AgentSkillsCN

solana-dev

端到端 Solana 开发实战手册（2026年1月）。对于 React/Next.js 用户界面，优先选用 Solana 基金会提供的框架套件（@solana/client + @solana/react-hooks）；对于所有新开发的客户端、RPC 及交易相关代码，则优先使用 @solana/kit。若旧有依赖仍需 web3.js，应将其封装于 @solana/web3-compat 之后（或以 @solana/web3.js 作为真正的遗留回退方案）。本手册涵盖钱包标准优先的连接方式（包括 ConnectorKit）、Anchor/Pinocchio 程序、基于 Codama 的客户端生成、LiteSVM/Mollusk/Surfpool 测试，以及各类安全检查清单。

SKILL.md
--- frontmatter
name: solana-dev
description: 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.
user-invocable: true

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)

  1. •UI: framework-kit first
  • •Use @solana/client + @solana/react-hooks.
  • •Prefer Wallet Standard discovery/connect via the framework-kit client.
  1. •SDK: @solana/kit first
  • •Prefer Kit types (Address, Signer, transaction message APIs, codecs).
  • •Prefer @solana-program/* instruction builders over hand-rolled instruction data.
  1. •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.
  1. •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.
  1. •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)