mcpField
S
solana-v1

solana-v1

github.com/blockmaticDevelopment1221 installsUpdated 5w ago
Repository

About solana-v1

solana-v1 is a skill for developing Solana dApp interfaces with React or Next.js. It focuses on wallet connection, address validation, and transaction flows using Solana-specific libraries and patterns.

Key features

  1. 01Solana dApp UI patterns for React and Next.js
  2. 02Wallet discovery and connection with Wallet Standard
  3. 03Address validation with PublicKey
  4. 04Transaction building, sending, and confirmation
  5. 05Guidance on Solana client and RPC libraries

Use cases

  1. 01Building a Solana dApp interface
  2. 02Implementing wallet connection and signing flows
  3. 03Validating addresses before use
  4. 04Creating transaction submission and confirmation flows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blockmatic/basilic-skills --skill solana-v1

After installing, type/solana-v1in Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

frontend-framework-kit.md
kit-web3-interop.md
payments.md
resources.md
security.md

Details

From the project README

Skill: solana

Scope

  • Solana dApp UI development (React/Next.js) with framework-kit
  • Wallet connection and signing flows
  • Transaction building, sending, and confirmation UX
  • Address validation and transaction patterns

Does NOT cover:

  • EVM frontend development (see wagmi-v3)
  • Address-only backend validation without dApp UI (may use @solana/web3.js PublicKey only)
  • General blockchain concepts

Assumptions

  • @solana/client and @solana/react-hooks for UI development
  • @solana/kit for client/RPC/transaction code
  • @solana/web3.js v1.x for address validation
  • React 18+ or Next.js 14+ for UI
  • TypeScript v5+ with strict mode
  • Node.js 18+

Principles

  • Use Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI
  • Use @solana/kit for client/RPC/transaction code
  • Validate addresses with PublicKey from @solana/web3.js (including backend-only routes that do not ship wallet UI)
  • Use Wallet Standard for wallet discovery and connection
  • Isolate @solana/web3.js to adapter boundaries when legacy dependencies require it

Constraints

MUST
  • Validate addresses with PublicKey.isOnCurve() before use
  • Use @solana/web3-compat for legacy adapter boundaries
SHOULD
  • Use @solana/kit types (Address, Signer) over web3.js types
  • Prefer @solana-program/* instruction builders over hand-rolled instruction data
  • Use Wallet Standard for wallet discovery/connect
  • Contain @solana/web3.js types to adapter modules (don't leak across app)
AVOID
  • Letting @solana/web3.js types leak across entire app
  • Skipping address validation before use

Patterns

Address Validation Pattern

Always validate Solana addresses before use:

import { PublicKey } from '@solana/web3.js'

function validateSolanaAddress(address: string): boolean {
  try {
    const publicKey = new PublicKey(address)
    return PublicKey.isOnCurve(publicKey)
  } catch {
    return false
  }
}

Interactions

  • Complements wagmi skill for EVM frontend work
  • Focuses on Solana-specific dApp development patterns

Comments

Markdown supported