How do I install the Solana Dev skill?

Run npx skillmds@latest add kbarbel640-del/solana-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Solana Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solana Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Solana Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Solana Dev?

kbarbel640-del (@kbarbel640-del) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Solana Dev by kbarbel640-del — Agent Skill

Name: Solana Dev
Rating: 4.2 (5 reviews)
Author: kbarbel640-del

Solana Dev

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.

kbarbel640-del Updated Sep 8, 2026 1 repo stars

File contents

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

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
Security checklist: security.md
Reference links: resources.md

---name: solana-devdescription: 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.---# Solana Development Skill (framework-kit-first)## What this Skill is forUse 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## 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**- Prefer Kit types (`Address`, `Signer`, transaction message APIs, codecs).- Prefer `@solana-program/*` instruction builders over hand-rolled instruction data.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.5) **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 correctnessAlways 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 expectationsWhen 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](frontend-framework-kit.md)- Kit ↔ web3.js boundary: [kit-web3-interop.md](kit-web3-interop.md)- Anchor programs: [programs-anchor.md](programs-anchor.md)- Pinocchio programs: [programs-pinocchio.md](programs-pinocchio.md)- Testing strategy: [testing.md](testing.md)- IDLs + codegen: [idl-codegen.md](idl-codegen.md)- Payments: [payments.md](payments.md)- Security checklist: [security.md](security.md)- Reference links: [resources.md](resources.md)

Frequently asked questions