synapse-sap

Design Anchor instruction, account model, PDA seeds, and program structure. Use when: creating new instructions, refactoring Anchor programs, designing state machines, planning PDA schemas, building account contexts. Produces minimal, production-oriented architecture before writing code.

Decide and implement zero-copy account structures in Anchor. Use when: dealing with large accounts, compute-sensitive hot paths, fixed-layout state, high-frequency structured data access. Evaluates whether zero-copy is actually justified before implementing.

Meta-skill: simplification pass before any final output. Use when: completing any code generation, architecture design, or refactor. Removes unnecessary accounts, abstractions, instructions, and features. Applied automatically as the last step of any skill pipeline.

Reduce compute units and runtime overhead in Solana programs. Use when: optimizing hot-path instructions, reducing CU for high-frequency programs, working with large accounts, pre-mainnet performance tuning. Maintains clarity and correctness while cutting waste.

Design clean, secure cross-program invocations (CPI) for Solana. Use when: calling other programs, designing authority propagation, building composable instructions, integrating SPL Token or System Program, verifying CPI trust boundaries.

Design PDA seed schemas for Solana programs. Use when: planning new PDAs, auditing seed collisions, designing authority relationships via seeds, reviewing PDA derivation consistency across program and client. Produces stable, semantic, collision-free seed designs.

Solana infrastructure awareness beyond smart contracts. Use when: designing account models for RPC queryability, planning indexing strategies, considering Geyser/DAS integration, optimizing client fetch patterns, designing for validator/RPC/archival constraints. Ensures on-chain design works well with real-world consumption.

Security audit for Solana/Anchor code. Use when: reviewing instructions pre-deploy, performing internal audits, refactoring existing code, verifying trust assumptions, checking CPI safety, validating signer/owner/PDA models. Finds logic bugs, attack surfaces, and fragile designs.

Generate meaningful Solana/Anchor tests. Use when: writing tests for new instructions, verifying access control, testing edge cases, validating state transitions, checking zero-copy layouts. Produces test matrices with happy paths, failure paths, and invariant checks — not smoke tests.