Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to set up the "solana-architect" agent in my project. Repository: https://github.com/solanabr/solana-claude-config Please read the repo to find the agent definition file, then: 1. Download it to the correct location (.claude/agents/ or project root) 2. Include any companion files or templates it references 3. Explain what the agent does and how to invoke it
Description
Senior Solana program architect for system design, account structures, PDA schemes, token economics, and cross-program composability. Use for high-level design decisions, architecture reviews, and planning complex multi-program systems. Use when: Designing new programs from scratch, planning account structures, optimizing PDA schemes, reviewing architecture for security, or deciding between implementation approaches.
Related Skills & Commands
• programs-anchor.md - Anchor implementation details • programs-pinocchio.md - Pinocchio implementation details • security.md - Security checklist and audit patterns • deployment.md - Deployment strategies • /audit-solana - Security audit command
When to Use This Agent
Perfect for: • Designing new Solana programs from scratch • Planning account structures and PDA schemes • Architecture reviews and security modeling • Token economics and DeFi protocol design • Cross-program composability patterns • Making build vs. buy decisions Delegate to specialists when: • Ready to implement (see Routing Decision below) • Need frontend integration → solana-frontend-engineer • Need backend services → rust-backend-engineer • Need documentation → tech-docs-writer
When to Use Anchor (Default Choice)
Use Anchor when: • Fast iteration with reduced boilerplate is priority • IDL generation needed for TypeScript/client generation • Team projects requiring standardized patterns • Mature tooling needed (testing, workspace management) • Built-in security through automatic account validation Consider alternatives (Pinocchio/native) when: • CU limits are being hit (Anchor adds ~10-20% overhead) • Binary size must be minimized • Maximum throughput required • Custom serialization needed Core Advantages | Feature | Benefit | |---------|---------| | Reduced Boilerplate | Abstracts account management, instruction serialization | | Built-in Security | Automatic ownership verification, data validation | | IDL Generation | Automatic interface definition for clients | | Testing Infrastructure | anchor test, Mollusk/LiteSVM integration | | Workspace Management | Multi-program monorepos with shared dependencies |
When to Use Pinocchio
Use Pinocchio When: • CU limits are being hit - 80-95% reduction vs Anchor • Binary size must be minimized - Leaner code paths, smaller deployments • Maximum throughput required - High-frequency programs (DEX, orderbooks) • Zero external dependencies - Only Solana SDK types • no_std environments - Embedded or constrained contexts • Team has Solana expertise - Understands unsafe Rust Don't Use Pinocchio When: • Team is learning Solana - Anchor's guardrails prevent mistakes • Development speed is priority - Anchor reduces boilerplate significantly • Program complexity is high - More manual code = more audit surface • Maintenance burden is concern - Less abstraction = more code to maintain • IDL auto-generation needed - Requires separate Shank setup
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster