solana-dev
/solana-dev
Prowadzi przez tworzenie aplikacji Solana: połączenie portfela, programy Anchor lub Pinocchio, testy i wdrożenie na devnet.
- Autor
- elophanto ↗
- Repozytorium
- EloPhanto ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 01.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 15
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 01.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi przez tworzenie aplikacji Solana: połączenie portfela, programy Anchor lub Pinocchio, testy i wdrożenie na devnet.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", or "deploy to devnet". End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
Jak działa
- What this Skill is for
- Default stack decisions (opinionated)
- Operating procedure (how to execute tasks)
- Progressive disclosure (read when needed)
- Verify
Podgląd SKILL.md
--- name: solana-dev description: Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", or "deploy to devnet". End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries. user-invocable: true license: MIT compatibility: Requires Node.js 18+, Rust toolchain, Solana CLI, Anchor CLI metadata: author: Solana Foundation version: 1.1.0 --- # 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) - **Toolchain setup, version mismatches, GLIBC errors, dependency conflicts** - **Upgrading Anchor/Solana CLI versions, migration between versions** ## 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 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](references/frontend-framework-kit.md) - Kit ↔ web3.js boundary: [kit-web3-interop.md](references/kit-web3-interop.md) - Anchor programs: [programs-anchor.md](references/programs-anchor.md) - Pinocchio programs: [programs-pinocchio.md](references/programs-pinocchio.md) - Testing strategy: [testing.md](references/testing.md) - IDLs + codegen: [idl-codegen.md](references/idl-codegen.md) - Payments: [payments.md](references/payments.md) - Confidential transfers: [confidential-transfers.md](references/confidential-transfers.md) - Security checklist: [security.md](references/security.md) - Reference links: [resources.md](references/resources.md) - **Version compatibility:** [compatibility-matrix.md](references/compatibility-matrix.md) - **Common errors & fixes:** [common-errors.md](references/common-errors.md) - **Surfpool (local network):** [surfpool.md](references/surfpool.md) - **Surfpool cheatcodes:** [surfpool-cheatcodes.md](references/surfpool-cheatcodes.md) ## Verify - A real RPC/SDK call was issued (mainnet, devnet, or local validator) and the response payload is captured in the transcript, not just paraphrased - Every transaction was simulated (`simulateTransaction` or equivalent) before any signing/sending step; simulation logs are attached - For any signed/sent transaction, the resulting signature is recorded and confirmed on chain (status returned by `getSignatureStatuses` or an explorer URL) - Slippage, priority-fee, and compute-unit limits were set explicitly with concrete numeric values, not left to library defaults - Account addresses, mints, and program IDs used in the run match the documented solana-development addresses for the targeted cluster (no mainnet/devnet mix-up) - Failure path was exercised at least once (insufficient balance, stale oracle, expired blockhash, etc.) and the agent's error handling produced a human-readable message
Pliki w paczce (15)
- SKILL.md 6 KB
- references/common-errors.md 20 KB
- references/compatibility-matrix.md 9 KB
- references/confidential-transfers.md 25 KB
- references/frontend-framework-kit.md 3 KB
- references/idl-codegen.md 1 KB
- references/kit-web3-interop.md 2 KB
- references/payments.md 2 KB
- references/programs-anchor.md 8 KB
- references/programs-pinocchio.md 14 KB
- references/resources.md 3 KB
- references/security.md 8 KB
- references/surfpool-cheatcodes.md 14 KB
- references/surfpool.md 20 KB
- references/testing.md 8 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · elophanto/EloPhanto | 85 | MIT |
| solana-foundation/solana-dev-skill | 100 | MIT |
| internet-court/internet-court-skill | 100 | MIT |
| guibibeau/solana-dev-skill | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki eb3a389a3781 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100solana
Pomaga pisać programy on-chain w Rust z frameworkiem Anchor, łączyć się z siecią Solana z TypeScript przez @solana/kit, tworzyć tokeny SPL w CLI oraz testować i wdrażać na devnet. - 100solana
Pomaga pisać kod Solana w TypeScript i Rust oraz programy Anchor, Quasar i testy LiteSVM z minimalną duplikacją. - 100solana
Pomaga przy oprogramowaniu Solana w TypeScript i Rust, w tym programach Anchor i Quasar, tworząc mały, wielokrotnego użytku kod. - 100solana-development
Buduje, testuje, wdraża i audytuje programy Solana w Anchor lub natywnym Rust, z ZK Compression (Light Protocol), operacje na tokenach, optymalizację obliczeń i skompresowane tokeny oraz PDA. - 100solana-network
Pokazuje bieżącą sieć Solana i przełącza między devnet, testnet, localnet i mainnet-beta. - 100auditing-solana-programs
Audytuje programy Solana w Rust pod kątem wad architektury, opierając się na wzorcach projektowych i klasycznych błędach.