audit-solana
01Command Claude Code
Security audit for Solana programs (Anchor/native).
The most complete Solana glossary with 1000+ enriched terms. Available as SDK, MCP Server and Agent Skill.
Command Claude Code
Security audit for Solana programs (Anchor/native).
Command Claude Code
Benchmark CU usage and compare against baseline for regression detection.
Command Claude Code
Build web client application (Next.js, React, Vite).
Command Claude Code
Build Solana program (Anchor or native).
Command Claude Code
Build Unity project (WebGL, Desktop, or PSG1).
Command Claude Code
Deploy Solana program (devnet first, then mainnet).
Command Claude Code
AI-powered diff review for Solana-specific issues and code quality.
Command Claude Code
Explain complex Solana/blockchain code with visual diagrams and step-by-step breakdowns.
Command Claude Code
Generate TypeScript client from Solana program IDL using Codama or Anchor.
Command Claude Code
Migrate from @solana/web3.js to @solana/kit.
Command Claude Code
Plan feature implementation with technical specifications for Solana projects.
Command Claude Code
Profile compute unit usage per instruction in a Solana program.
Command Claude Code
Quick commit with automatic formatting, linting, and conventional commit message.
Command Claude Code
Scaffold a new Solana project with programs, frontend, tests, and CI.
Command Claude Code
Setup CI/CD pipeline with automated security checks for Solana programs.
Command Claude Code
Configure MCP server API keys in .env.
Command Claude Code
Run tests and automatically fix common issues.
Command Claude Code
Run .NET/C# tests for Unity projects and backend services.
Command Claude Code
Run Rust tests for Solana programs and backend services.
Command Claude Code
Run TypeScript tests for Solana frontends and Anchor programs.
Command Claude Code
Update external skill submodules and verify integrity.
Command Claude Code
Generate documentation for Solana programs, APIs, and components.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: