Solana Claude Configuration

Production-ready Claude Code configuration for full-stack Solana development. Combines best practices from multiple sources into an agent-optimized, token-efficient config you can install and adapt to your specific project.

The idea here is to provide a generic CLAUDE.md that relies on subagents to plan and execute actions, dynamically loading markdown files, saving tokens and context in the end of the day. This config fully leverages the official Claude Code config recommendations:

• Rules are only loaded whenever specific file types are involved;
• SKILL.md is a mega hub to dynamically-disclosed skill files that are directly fetched from the best skill repos distributed across the ecosystem (Solana Foundation, Colosseum, Solana Mobile, SendAI, etc);
• Plus, its CLAUDE-solana.md is than half the size of the usual CLAUDE.md, leaving space for its self improvements programmed into the agents, noting and learning from anti-patterns, errors, recurrency and more. For less important notes, CLAUDE.local.md is constantly maintained by agents as well and, on monorepos, per-folder CLAUDE.md is also maintained.

Current multi-agent workflow favors monorepos, so we use a single CLAUDE.md/config for the whole project while leveraging agents and context-specific skills to solve each step of builder flow.

If you installed manually, remember to rename ./CLAUDE-solana.md back to ./CLAUDE.md, as the current top-level CLAUDE.md file is focused on maintaining the repo itself.

What This Is

A complete .claude/ configuration that turns Claude into a Solana development expert with:

• 15 specialized agents for different tasks (architecture, Anchor, Pinocchio, DeFi, tokens, frontend, mobile, backend, DevOps, QA, docs, games, Unity, learning, research)
• 24 workflow commands for building, testing, deploying, profiling, migrating, and committing
• 6 MCP server integrations for on-chain data (Helius), Solana docs (solana-dev), library docs (Context7), browser automation (Playwright), context optimization (context-mode), and persistent memory (memsearch)
• Agent teams for multi-step workflows (architect → engineer → QA)
• Progressive skill loading that only loads context when needed (saves tokens)
• Auto-loading rules that enforce best practices based on file patterns

Quick Start

# Option 0: Fork Template (Github UI)
claude -m "/cleanup"  # then start claude code running /cleanup so top-level directory of your project isn't polluted


# Option 1: One-liner installer (Claude Code)
curl -fsSL https://raw.githubusercontent.com/solanabr/solana-claude-config/main/install.sh | bash

# Option 2: One-liner installer (Codex, Opencode, everything else)
curl -fsSL https://raw.githubusercontent.com/solanabr/solana-claude-config/main/install.sh | bash -s -- --agents

# Option 3: Manual setup
git clone --recurse-submodules https://github.com/solanabr/solana-claude-config.git
cp -r solana-claude-config/.claude /path/to/your-project/
cp solana-claude-config/CLAUDE-solana.md /path/to/your-project/CLAUDE.md
cd /path/to/your-project && git submodule update --init --recursive

# Start Claude Code
claude

--agents Flag

Pass --agents to install everything into .agents/ instead of .claude/. Same content, different directory name. Useful when .claude/ is already taken or for non-Claude AI tools (Cursor, Windsurf, Copilot, etc.).

bash install.sh --agents /path/to/your-project

To update an --agents install:

# Run from your project root:
bash .agents/bin/update.sh

MCP Setup (Optional)

After installation, configure MCP servers for enhanced capabilities:

# In your project with Claude Code running:
/setup-mcp

This guides you through API key configuration for Helius, Context7, and other MCP servers.

Key Features

External Skill Submodules

Agent Teams

Each agent loads its own specialized context on invocation:

"Use solana-architect to design the vault program"
"Use anchor-engineer to implement the deposit instruction"
"Use defi-engineer to integrate Jupiter swaps"
"Use solana-qa-engineer to write comprehensive tests"

Claude will spawn each specialized agent by itself based on context and, with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled, orchestrate multi-agent workflows:

"Create an agent team: solana-architect for design, anchor-engineer for implementation, solana-qa-engineer for testing"

Recommended team patterns:

MCP Server Integrations

Pre-configured MCP servers in .mcp.json (API keys go in .env):

Token-Efficient Design

• CLAUDE.md is delivered as a user message (not system prompt) — shorter = better adherence
• Skills load progressively (not all at once)
• Agents reference skills instead of duplicating content
• Path-scoped rules lazy-load on file read (zero startup cost)
• CLAUDE.local.md for private scratch notes (gitignored, never shared)
• Subdirectory CLAUDE.md files lazy-load in monorepos
• Decision frameworks live in agents, not global context

Modern Stack (2026)

Repository Structure

.
├── CLAUDE.md                    # Main hub - Claude reads this first
├── README.md                    # This file
├── .mcp.json                    # MCP server configurations (project root)
├── install.sh                   # One-liner installer
├── update.sh                    # Deprecation wrapper → .claude/bin/update.sh
├── validate.sh                  # Config integrity checker
├── LICENSE                      # MIT
├── tests/                       # Config integrity test suite
├── .github/workflows/
│   ├── ci.yml                       # PR validation
│   └── claude-code.yml              # Claude Code action template
└── .claude/
    ├── VERSION                  # Semver version (e.g. 1.4.0)
    ├── agents/                  # 15 specialized agents
    ├── bin/
    │   ├── update.sh                # In-place update from upstream
    │   └── resync.sh                # Submodule resync script
    ├── commands/                # 25 workflow commands
    ├── skills/                  # Progressive-loading knowledge
    │   ├── SKILL.md                 # Unified hub routing to all skills
    │   ├── ext/                     # External skill submodules
    │   │   ├── solana-dev/              # Solana Foundation dev skill (core)
    │   │   ├── sendai/                  # SendAI protocol skills (DeFi)
    │   │   ├── solana-game/             # Solana game skill (Unity, PSG1)
    │   │   ├── cloudflare/              # Cloudflare Workers, Agents SDK
    │   │   ├── trailofbits/             # Trail of Bits security skills
    │   │   ├── qedgen/                # QEDGen formal verification (Lean 4)
    │   │   ├── solana-mobile/           # Mobile Wallet Adapter, Genesis Token
    │   │   ├── colosseum/              # Colosseum Copilot (startup research)
    │   │   ├── safe-solana-builder/   # Security-first code generation
    │   │   └── vercel/                # Vercel deployment, Next.js, AI SDK
    │   ├── token-2022.md            # Token Extensions guide (local)
    │   ├── backend-async.md         # Axum/Tokio patterns (local)
    │   └── deployment.md            # Deployment workflows (local)
    ├── rules/                   # Auto-loading constraints
    └── settings.json            # Permissions, hooks, agent teams

Agents

Commands

Building

Testing & Quality

Deployment & Migration

Workflow & Setup

DX Scripts

GitHub Action for Team Collaboration

This config includes a pre-built GitHub Action (.github/workflows/claude-code.yml) for PR-based iteration:

1. Add ANTHROPIC_API_KEY to your repository secrets
2. Copy .github/workflows/claude-code.yml to your project
3. Team members can @claude in PR comments
4. Claude responds with code suggestions using this configuration

Branch Workflow

All new work starts on a feature branch:

# Format: <type>/<scope>-<description>-<DD-MM-YYYY>
git checkout -b feat/program-vault-15-01-2026
git checkout -b fix/frontend-auth-15-01-2026

Use /quick-commit to automate branch creation and commits.

Code Quality

Before merging, run /diff-review or check diff against main:

git diff main...HEAD

Remove: excessive comments, abnormal try/catch blocks, verbose errors, redundant validation.

Keep: legitimate security checks, non-obvious explanations, matching error patterns.

Using as a GitHub Template

1. Click "Use this template" on GitHub (or fork the repo)
2. Clone your new repo
3. Run Claude Code and use /cleanup — this copies CLAUDE-solana.md → CLAUDE.md and removes config repo scaffolding (tests, install scripts, docs)
4. Start building!

For monorepos, add a CLAUDE.md to each package/module with architecture decisions scoped to that directory. Claude Code automatically loads these when working in that subdirectory.

Updating

# Preferred: use /update in Claude Code, or run directly:
bash .claude/bin/update.sh

# Preview changes without applying:
bash .claude/bin/update.sh --dry-run

# Resync skill submodules only:
bash .claude/bin/resync.sh

# Or manually update submodules
git submodule update --remote --merge

Credits

This project builds on excellent work from the community:

• solana-foundation/solana-dev-skill - The Solana Foundation's comprehensive skill set for Solana development, included as the primary submodule.

• sendaifun/skills - SendAI's protocol-specific skills for DeFi integrations.

• solanabr/solana-game-skill - Game development skills for Unity and PlaySolana.

• trailofbits/skills - Trail of Bits security auditing skills.

• cloudflare/skills - Cloudflare infrastructure skills.

• QEDGen/solana-skills - Formal verification for Solana programs using Lean 4 theorem proving.

• ColosseumOrg/colosseum-copilot - Solana startup research, idea validation, and hackathon project discovery from Colosseum. Proprietary license (Copyright Colosseum).

• 0xquinto/bcherny-claude - Compiled Boris Cherny's (creator of Claude Code at Anthropic) best practices including verification loops, parallel Claude sessions, and CLAUDE.md patterns.

License

MIT - See LICENSE