solana-dev

Guide building, testing, and securing Solana dApps with Anchor and React.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/tarotmansa/moltguild --skill solana-dev-tarotmansa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solana-dev
Source: https://github.com/tarotmansa/moltguild/tree/main/skill-audit/solana-dev-skill
Command: npx skills add https://github.com/tarotmansa/moltguild --skill solana-dev-tarotmansa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consolidated, opinionated playbook to design, build, test, and secure Solana applications so teams avoid fragmented stacks, leaking web3.js types, and ad-hoc testing that causes production regressions.

Core Features & Use Cases

  • Frontend & Wallet UX: patterns for React/Next.js using framework-kit, Wallet Standard discovery, ConnectorKit options, and transaction UX best practices.
  • Program & Client Development: guidance for Anchor and Pinocchio programs, IDL-driven codegen (Codama), and Kit-first client APIs with web3-compat boundaries for legacy libraries.
  • Testing & Security: fast unit testing with LiteSVM/Mollusk, integration with Surfpool, and an extensive program+client security checklist for CPI safety, account validation, and revocation handling.
  • Use Case: Build a Next.js dApp that discovers Wallet Standard wallets, sends Kit-native transactions to an Anchor program, runs unit tests in LiteSVM, and verifies security checks before deployment.

Quick Start

Create a Next.js app, add framework-kit and @solana/kit, provide a single SolanaProvider client with auto-discovered wallet connectors, and run a unit test against LiteSVM.

Frequently Asked Questions about solana-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to structure a Solana dApp frontend with Wallet Standard and framework-kit?

The best way to structure a Solana dApp frontend is using framework-kit with a single SolanaProvider client that auto-discovers Wallet Standard wallets, establishing Kit↔web3.js interop boundaries to prevent leaking legacy types.

How do I generate client code for an Anchor program using IDL-driven codegen?

Generate client code for Anchor programs using Codama IDL-driven codegen to produce Kit-first client APIs, ensuring type-safe interactions and clear boundaries between Kit-native code and legacy web3.js compatibility layers.

Can I use LiteSVM or Mollusk for fast unit testing of Solana programs?

Yes, you can use LiteSVM and Mollusk for fast local unit testing of Solana programs, and integrate with Surfpool for broader integration testing before verifying security checks and deploying.

Does this Solana development playbook support Pinocchio as well as Anchor?

Yes, this Solana development playbook supports both Anchor and Pinocchio for program development, providing end-to-end guidance for building, testing, and securing programs alongside client codegen and frontend integration.

What security checks should I run for Solana program CPI safety and account validation?

Run an extensive security checklist covering CPI safety, account validation, revocation handling, and RPC endpoint security to prevent production regressions caused by ad-hoc testing and fragmented stacks.

Why does my Solana dApp leak web3.js types into the client stack?

Solana dApps leak web3.js types when ad-hoc integration lacks clear boundaries, which this playbook solves by enforcing framework-kit-first client patterns and defining strict Kit↔web3.js interop boundaries for legacy libraries.