Solana Dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a...
Install
npx skills add internet-court/internet-court-skill --skill solana-dev -g -a claude-code -y- Repository
- internet-court/internet-court-skill7k
- Category
- Testing
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 2,744 tokens
- Runs scripts
- No, instructions only
What it does
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). Also use for quick on-chain lookups via public RPC + curl, "what's the balance of <wallet>", "look up transaction <sig>", "token balance for <account>", "check this address on mainnet/devnet". End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, Surfpool/LiteSVM/Mollusk testing, security checklists, and JSON-RPC curl lookups against public clusters. Prefers @solana/kit v7 plugin clients (createClient + .use()), wallet connection via @solana/kit-plugin-wallet + @solana/react, web3.js v3 (Kit internals, RC) as the migration target for legacy codebases, and Surfpool for local networks and integration testing.
Solana Development Skill (Kit-first)
What this Skill is for
Use this Skill when the user asks for:
- Solana dApp UI work (React / Next.js)
- Wallet connection + signing flows
- Transaction building / sending / confirmation UX
- On-chain program development (Anchor or Pinocchio)
- Client SDK generation (typed program clients)
- Local testing (Surfpool, LiteSVM, Mollusk)
- Security hardening and audit-style reviews
- Confidential transfers (Token-2022 ZK extension)
- Toolchain setup, version mismatches, GLIBC errors, dependency conflicts
- Upgrading Anchor/Solana CLI versions, migration between versions
- Migrating web3.js v1 code to web3.js v3 or Kit
Default stack decisions (opinionated)
- SDK: @solana/kit (v7+) first
- Build clients with
createClient()from@solana/kit, then.use(...)plugins:createClient() .use(signer(mySigner)) .use(solanaRpc({ rpcUrl })); // or solanaLocalRpc / solanaDevnetRpc / solanaMainnetRpc from @solana/kit-plugin-rpc - Default to
signer()/signerFromFile()/generatedSigner()from@solana/kit-plugin-signer, they set bothpayerandidentityto the same keypair (the common case). For fresh local/devnet signers, install the RPC/LiteSVM plugin aftergeneratedSigner(), then fund withairdropSigner(...). Reach for the role-specific variants (payer()+identity()) only when fees and authority must come from different keypairs. - Use
@solana-program/*program plugins (e.g.,tokenProgram()) for fluent instruction APIs. - Prefer Kit types (
Address,Signer, transaction message APIs, codecs).
