solana-kit-migration

Guide Solana SDK migrations between @solana/kit and @solana/web3.js.

11|13|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/MetalLegBob/drfraudsworth --skill solana-kit-migration-metallegbob
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solana-kit-migration
Source: https://github.com/MetalLegBob/drfraudsworth/tree/main/.claude/skills/solana-kit-migration-skill
Command: npx skills add https://github.com/MetalLegBob/drfraudsworth --skill solana-kit-migration-metallegbob

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Guides developers on when to use @solana/kit versus @solana/web3.js during Solana SDK migrations, and provides migration guidance, API mappings, and edge-case handling to streamline transitions.

Core Features & Use Cases

  • Decision guidance on library choice for new vs existing projects, including Anchor considerations.
  • API migration mappings and concrete scenarios to illustrate typical transitions.
  • Use Case: Migrating from web3.js to Kit while maintaining compatibility with Anchor-based modules, including hybrid path recommendations.

Quick Start

Assess your project and decide whether to adopt @solana/kit or @solana/web3.js, then apply the recommended migration steps accordingly.

Frequently Asked Questions about solana-kit-migration

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

FAQPage Schema
Should I use @solana/kit or @solana/web3.js for my new Solana project?▼

Choosing between @solana/kit and @solana/web3.js depends on your project type and Anchor compatibility. The skill provides decision criteria evaluating new projects, hybrid dependencies, and framework integration to guide your SDK selection.

How do I migrate from @solana/web3.js to @solana/kit?▼

Migrate from @solana/web3.js to @solana/kit by following a step-by-step framework that includes API migration mappings, edge-case coverage, and risk factor assessment to streamline the transition.

Does @solana/kit work with Anchor-based modules?▼

Yes, @solana/kit works with Anchor-based modules through a hybrid dependency path. The skill outlines specific scenarios and recommendations for maintaining compatibility during your migration.

What are the risk factors when migrating Solana SDKs?▼

Risk factors when migrating Solana SDKs include API mapping mismatches and edge-case handling. The skill identifies these constraints and offers a structured framework to mitigate potential transition issues.

What prerequisites are needed for a Solana SDK migration?▼

Prerequisites for a Solana SDK migration include API mappings, edge-case coverage, and a step-by-step framework. These align with the skill's references, examples, and tooling to ensure a confident transition.

Why choose @solana/kit over @solana/web3.js?▼

Choose @solana/kit over @solana/web3.js based on decision criteria covering new versus existing projects and Anchor considerations. The skill contrasts these scenarios to highlight the benefits and trade-offs of each library.