solana-kit-migration

Identify and map v1 web3.js usage to plan Solana Kit-based replacements.

116|9|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/elophanto/EloPhanto --skill solana-kit-migration-elophanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solana-kit-migration
Source: https://github.com/elophanto/EloPhanto/tree/main/skills/solana-kit-migration
Command: npx skills add https://github.com/elophanto/EloPhanto --skill solana-kit-migration-elophanto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Solana developers face fragmented guidance when migrating from @solana/web3.js (v1) to @solana/kit. This Skill consolidates migration guidance, API mappings, and edge-case handling to streamline a safe upgrade.

Core Features & Use Cases

  • Migration guidance: decision criteria on when to use kit vs web3.js, with a flowchart and edge-case coverage.
  • API mappings reference: links and details to convert v1 constructs to Kit equivalents.
  • Codebase analysis: lightweight scripts to estimate migration complexity and identify hotspots.

Quick Start

Run the analysis to surface v1 patterns in your codebase and follow the references to implement Kit-compatible migrations.

Frequently Asked Questions about solana-kit-migration

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

FAQPage Schema
How do I migrate from @solana/web3.js v1 to @solana/kit?

Migrate from @solana/web3.js v1 to @solana/kit by running codebase analysis scripts to identify v1 usage patterns, then use API mapping references to incrementally replace RPC creation, key management, and transaction building logic.

What is the difference between @solana/web3.js and Solana Kit?

Solana Kit provides modular replacements for @solana/web3.js v1 primitives, targeting RPC creation, key management, transaction building, and subscription patterns to enable a safer, incremental TypeScript migration path.

How do I analyze my codebase for Solana web3.js v1 usage before upgrading to Kit?

Analyze codebase Solana web3.js v1 usage by running lightweight scripts that estimate migration complexity, identify v1 hotspots, and map remaining RPC and transaction patterns to plan Kit-based replacements.

Can I incrementally migrate Solana web3.js RPC and subscription patterns to Kit?

Yes, you can incrementally migrate Solana web3.js RPC and subscription patterns to Kit by following decision criteria and API mappings to safely upgrade specific constructs without rewriting the entire TypeScript project simultaneously.

When should I use Solana Kit instead of keeping @solana/web3.js v1?

You should use Solana Kit instead of @solana/web3.js v1 when you need modular RPC creation and transaction building, using the provided migration flowchart and edge-case guidance to decide when an upgrade is appropriate.