solana-dev
Skill0 starsChanged 10 months agoMITView on GitHub
End-to-end Solana development playbook. 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. Covers wallet-standard-first connection, Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.
9 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- gabrielkoerich/skillsedited, first seen Nov 1, 2026
- MShehrozJamshaid/cypher-claude-skillsedited, first seen Oct 20, 2026
- GuiBibeau/solana-dev-skilltheir own version, first seen Oct 9, 2026
- solana-foundation/solana-dev-skilltheir own version, first seen Oct 8, 2026
- Enricrypto/cypher-claude-skillsedited, first seen Jul 12, 2026
- Starchild-ai-agent/official-skillsedited, first seen May 21, 2026
Used with
Projects with it also use frontend-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Starchild-ai-agent/official-skills★ 3232% same
- gabrielkoerich/skills★ 882% same
- Shiven0504/claude-skills-collection★ 634% same
- MShehrozJamshaid/cypher-claude-skills★ 386% same
- Enricrypto/cypher-claude-skills★ 286% same
Wrote their own version · 4
- GuiBibeau/solana-dev-skill★ 589same name
- solana-foundation/solana-dev-skill★ 589same name
- solanabr/solana-glossary★ 19same name
- Helg-git/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- contextual-placeholdersSkill
- solana-mobile-devSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 8 are common, 1 is distinctive, and 4 are very specific to this project.
8
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 10
Use this Skill when the user asks for:
- Common: line 22
Prefer Wallet Standard discovery/connect via the framework-kit client.
- Very specific: line 25
Prefer Kit types (Address, Signer, transaction message APIs, codecs).
- Very specific: line 26
Prefer @solana-program/* instruction builders over hand-rolled instruction data.
- Very specific: line 29
If you must integrate a library that expects web3.js objects (PublicKey, Transaction, Connection), use @solana/web3-compat as the boundary …
- Very specific: line 31
Do not let web3.js types leak across the entire app.
- Common: line 34
Default: Anchor (fast iteration, IDL generation, mature tooling).
- Common: line 39
Default: LiteSVM or Mollusk for unit tests (fast feedback, runs in-process).
- Common: line 40
Use Surfpool for integration tests against realistic cluster state (mainnet/devnet) locally.
- Distinctive: line 41
Use solana-test-validator only when you need specific RPC behaviors not emulated by LiteSVM.
- Common: line 44
When solving a Solana task:
- Common: line 60
Always be explicit about:
- Common: line 73
When you implement changes, provide:
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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-compatas 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

