solana-dev

Name: solana-dev - Agent Skill
Rating: 3.4 (189 reviews)
Author: GuiBibeau

189

End-to-end Solana development playbook (Jan 2026). Prefer Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI. Prefer @solana/kit for all new client/RPC/transaction code. When legacy dependencies require web3.js, isolate it behind @solana/web3-compat (or @solana/web3.js as a true legacy fallback). Covers wallet-standard-first connection (incl. ConnectorKit), Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.

Download Folder View on GitHub

CLI Install

Recommended

Use the skills CLI to install this skill with one command. Auto-detects all installed AI assistants.

Method 1 - skills CLI

npx skills i GuiBibeau/solana-dev-skill/skill

Method 2 - openskills (supports sync & update)

npx openskills install GuiBibeau/solana-dev-skill

Auto-detects Claude Code, Cursor, Codex CLI, Gemini CLI, and more. One install, works everywhere.

Installation Path

Download and extract to one of the following locations:

~/.claude/skills/solana-dev/

SKILL.md

confidential-transfers.md

frontend-framework-kit.md

idl-codegen.md

kit-web3-interop.md

payments.md

programs-anchor.md

programs-pinocchio.md

resources.md

security.md

testing.md

Skill Instructions

Back

Run with Cloud Agent

No setup needed. Let our cloud agents run this skill for you.

Select Provider

Select Model

Claude Sonnet 4.5

$0.20/task

Best for coding tasks

Environment setup included

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)

Default stack decisions (opinionated)

UI: framework-kit first

Use @solana/client + @solana/react-hooks.
Prefer Wallet Standard discovery/connect via the framework-kit client.

SDK: @solana/kit first

Prefer Kit types (Address, Signer, transaction message APIs, codecs).
Prefer @solana-program/* instruction builders over hand-rolled instruction data.

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.

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.

Testing

Default: LiteSVM or Mollusk for unit tests (fast feedback, runs in-process).
Use Surfpool for integration tests against realistic cluster state (mainnet/devnet) locally.
Use solana-test-validator only when you need specific RPC behaviors not emulated by LiteSVM.

Operating procedure (how to execute tasks)

When solving a Solana task:

1. Classify the task layer

UI/wallet/hook layer
Client SDK/scripts layer
Program layer (+ IDL)
Testing/CI layer
Infra (RPC/indexing/monitoring)

2. Pick the right building blocks

UI: framework-kit patterns.
Scripts/backends: @solana/kit directly.
Legacy library present: introduce a web3-compat adapter boundary.
High-performance programs: Pinocchio over Anchor.

3. Implement with Solana-specific correctness

Always be explicit about:

cluster + RPC endpoints + websocket endpoints
fee payer + recent blockhash
compute budget + prioritization (where relevant)
expected account owners + signers + writability
token program variant (SPL Token vs Token-2022) and any extensions

4. Add tests

Unit test: LiteSVM or Mollusk.
Integration test: Surfpool.
For "wallet UX", add mocked hook/provider tests where appropriate.

5. Deliverables expectations

When you implement changes, provide:

exact files changed + diffs (or patch-style output)
commands to install/build/test
a short "risk notes" section for anything touching signing/fees/CPIs/token transfers

Progressive disclosure (read when needed)

UI + wallet + hooks: frontend-framework-kit.md
Kit ↔ web3.js boundary: kit-web3-interop.md
Anchor programs: programs-anchor.md
Pinocchio programs: programs-pinocchio.md
Testing strategy: testing.md
IDLs + codegen: idl-codegen.md
Payments: payments.md
Confidential transfers: confidential-transfers.md
Security checklist: security.md
Reference links: resources.md