solana-ai-kit
The solana-ai-kit Claude Code skill acts as a central hub routing Solana development capabilities, bundling go-to-market skills for idea validation, pitch decks, and hackathon submissions alongside an opt-in catalog of specialized add-ons. Use it when starting a Solana project, preparing investor or grant pitches, or accessing curated protocol, security, and ecosystem resources through linked upstream marketplaces and the full install script.
git clone --depth 1 https://github.com/solanabr/solana-ai-kit /tmp/solana-ai-kit && cp -r /tmp/solana-ai-kit/plugin/skills ~/.claude/skills/solana-ai-kitSKILL.md
# Solana AI Kit — Plugin Skill Hub
This is the **plugin variant** of the kit's skill hub. It ships only the skills that travel cleanly in a plugin (go-to-market wrappers + the opt-in add-on catalog). For the full depth — protocol/security/ecosystem skills, `.claude/rules/*`, and the curated permissions/sandbox policy — use the **full install** (see "Getting more depth" below).
**Source precedence (when multiple skills cover one topic):**
1. `.claude/rules/*` are law for code style — but rules ship **only** with the full install (`install.sh`), not this plugin. If you installed via the plugin, the house code-style rules are not loaded; prefer them when present.
2. Protocol-OFFICIAL skill is primary for that protocol's API/SDK usage (jup-ag→Jupiter, metaplex-foundation→Metaplex, helius-labs→Helius). In plugin form, add the relevant upstream marketplace (below).
3. Foundation/platform skills (Solana Foundation `solana-dev`) are primary for general concepts (Anchor, Pinocchio, testing, clients) — add its marketplace.
4. Community versions (sendai et al.) are secondary references.
## Bundled skills (shipped with this plugin)
These load automatically when the plugin is enabled. Commands and skills are namespaced under `solana-ai-kit:` (e.g. `/solana-ai-kit:deploy`).
### Idea, Pitch & Go-To-Market
Local wrappers, adapted from sendaifun/solana-new (MIT, telemetry removed):
- [idea-sprint/SKILL.md](idea-sprint/SKILL.md) — What to build: blunt interview, crypto-necessity gate, 3 scored candidates (/15), go/no-go with pivot suggestions
- [pitch-deck/SKILL.md](pitch-deck/SKILL.md) — Audience-aware decks (hackathon/VC/grant/accelerator): narrative frameworks, slides + speaking notes, objection prep
- [hackathon/SKILL.md](hackathon/SKILL.md) — Scannable submissions, <3-min demo scripts, least-crowded-track selection, Superteam Earn grants
### Extended add-ons (opt-in catalog)
- [skill-registry.json](skill-registry.json) — structured, machine-readable catalog of opt-in add-on skills/plugins/MCPs (frontend/design, UX/writing, testing, data, dev-workflow, extra protocols/MCPs) NOT bundled by default. Install on the user's request, at their own expense. Search it by domain/tags, then run the entry's install command only on explicit confirmation.
## Getting more depth (protocol / security / ecosystem skills)
Plugins cannot carry git submodules, so the 18 external skill packs (the `ext` submodules) are **not** bundled here. Two ways to get them:
### Option A — Add the upstream marketplaces (routing, not copying)
Several of the upstream skill packs publish their own Claude Code marketplaces. Add the ones you need, then `/plugin install` the specific skill plugins:
| Domain | Add the marketplace | Then install |
|--------|---------------------|--------------|
| DeFi protocols, infra, data (Jupiter, Raydium, Kamino, perps, oracles, cross-chain…) | `/plugin marketplace add sendaifun/skills` | the protocol plugins you need (one per skill) |
| AppSec scanning (SAST, SCA, secrets) | `/plugin marketplace add ghostsecurity/skills` | `ghost` |
| Security auditing, vulnerability scanning | `/plugin marketplace add trailofbits/skills` | the audit plugins you need |
| Infrastructure (Workers, Agents SDK, MCP servers) | `/plugin marketplace add cloudflare/skills` | `cloudflare` |
For Jupiter, Metaplex, and Helius the official skill repos are the primary sources — check the add-on catalog (`skill-registry.json`) for their current upstream locations and `/plugin marketplace add` targets. Route to a **marketplace** and install the plugin; do not point at an upstream repo's `SKILL.md` directly.
### Option B — Full install (recommended for project teams)
Run the installer in your project to get everything the plugin can't carry — the 18 external skill submodules, the lazy-loaded `.claude/rules` files (Rust, Anchor, Pinocchio, TypeScript, .NET code-style law), and the curated permissions + sandbox policy:
```bash
curl -fsSL https://raw.githubusercontent.com/solanabr/solana-ai-kit/main/install.sh | bash
```
See the project README ("External Skill Submodules" and "Install as a Claude Code plugin") for when to pick the plugin vs. the full install — they are complementary, not competing. If you run **both** in the same project, `/solana-ai-kit:doctor` warns about duplicate commands/hooks/MCP and advises picking one.
## Task Routing (bundled skills)
| User asks about... | Skill |
|--------------------|-------|
| Idea validation, "what should I build" | idea-sprint/SKILL.md |
| Pitch deck, demo day, investor or grant slides | pitch-deck/SKILL.md |
| Hackathon submission, demo script, track choice | hackathon/SKILL.md |
| Opt-in add-on skills/plugins/MCPs, "should I add X", extra capability not bundled | skill-registry.json |
| Protocol SDK depth (Jupiter, Metaplex, Helius, Raydium…), security audits, infra | add the upstream marketplace (Option A) or do the full install (Option B) |Anchor framework specialist for rapid Solana program development. Use for building programs with Anchor macros, IDL generation, account validation, and standardized patterns. Prioritizes developer experience while maintaining security.\\n\\nUse when: Building new programs quickly, team projects needing standardization, projects requiring IDL for client generation, or when developer experience is prioritized over maximum CU optimization.
DeFi integration specialist for composing with Solana protocols including Jupiter, Drift, Kamino, Raydium, Orca, Meteora, Marginfi, and Sanctum. Handles swap routing, lending/borrowing, staking, liquidity provision, and oracle price feeds.\n\nUse when: Integrating DeFi protocols, building swap interfaces, implementing lending/borrowing, setting up yield strategies, working with Pyth/Switchboard oracles, or composing multi-protocol transactions.
CI/CD, infrastructure, and deployment specialist for Solana projects. Handles GitHub Actions, Docker, monitoring, RPC management, and Cloudflare Workers edge deployment.\n\nUse when: Setting up CI/CD pipelines, containerizing Solana validators or programs, configuring monitoring and alerting, managing RPC infrastructure, deploying edge workers, or automating build and deploy workflows.
Senior Solana game architect for game system design, Unity/C# architecture, on-chain game state, player progression, NFT integration, and PlaySolana ecosystem. Use for high-level game design decisions, architecture reviews, and planning complex game systems.\n\nUse when: Designing new Solana games from scratch, planning game state on-chain, Unity project architecture, integrating with PlaySolana/PSG1, or deciding between implementation approaches.
React Native and Expo specialist for building Solana mobile dApps. Handles mobile wallet adapter integration, transaction signing UX, deep linking, and mobile-specific performance optimization.\n\nUse when: Building React Native or Expo mobile apps with Solana integration, implementing mobile wallet adapter flows, setting up deep links for transaction signing, or optimizing mobile dApp performance.
CU optimization specialist using Pinocchio framework. Use for performance-critical programs requiring 80-95% CU reduction vs Anchor. Specializes in zero-copy access, manual validation, and minimal binary size.\\n\\nUse when: CU limits are being hit, transaction costs are significant at scale, binary size must be minimized, or maximum throughput is required.
Rust backend specialist for building async services that interact with Solana blockchain. Builds APIs, indexing services, and off-chain processing using Axum, Tokio, and modern async patterns.\n\nUse when: Building REST/WebSocket APIs for Solana dApps, implementing transaction indexers, creating webhook services, or any Rust backend that interacts with Solana.
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.\n\nUse when: Designing new programs from scratch, planning account structures, optimizing PDA schemes, reviewing architecture for security, or deciding between implementation approaches.