Agent skill · software engineering · aiskillstore
solana-dev
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.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
Why this skill is useful
Adds a comprehensive end-to-end Solana development playbook with specific toolchain setups, executable code snippets, and security guidelines that are not widely available.
What it needs
Requires anchor-cli, node, rust, solana-cli installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Solana Development Skill (framework-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 (LiteSVM, Mollusk, Surfpool) 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 Default stack decisions (opinionated) 1) UI: framework-kit first Use @solana/client + @solana/react-hooks. Prefer Wallet Standard discovery/connect via the framework-kit client. 2) SDK: @solana/kit first Build clients with createClient() from @solana/kit, then .use(...) plugins: Default to signer() / signerFromFile() / generatedSigner() from @solana/kit-plugin-signer — they set both payer and identity to the same keypair (the common case). For fresh local/devnet signers, install the RPC/LiteSVM plugin after generatedSigner(), then fund with airdropSigner(...). 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). 3) Legacy compatibility: web3.js only at boundaries If you must integrate a library that expects web3.js objects (PublicKey, Transaction, Connection), use @solana/web3-compat as the boundary adapter. Do not let web3.js types leak across the entire app; contain them to adapter modules. 4) Programs Default: Anchor (fast iteration, IDL generation, mature tooling). Performance/footprint: Pinocchio when you need CU optimization, minimal binary size, zero dependencies, or fine-grained control over parsing/allocations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/solana-dev