solana-kit-migration

Migrate Solana applications from @solana/web3.js v1 to @solana/kit SDK.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kiran-nebula/agentshaus --skill solana-kit-migration-kiran-nebula
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solana-kit-migration
Source: https://github.com/kiran-nebula/agentshaus/tree/main/packages/agent-runtime/workspace/skills/sendaifun/solana-kit-migration
Command: npx skills add https://github.com/kiran-nebula/agentshaus --skill solana-kit-migration-kiran-nebula

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @solana/kit, @solana/web3.js, @solana/compat, @solana-program/system, @solana-program/token, @solana-program/compute-budget, and includes scripts (resource) and references (resource) and examples (resource) and docs (resource) components.

What problem does it solve?

This Skill assists developers in migrating their Solana projects from the legacy @solana/web3.js (v1) SDK to the newer, more performant @solana/kit SDK, providing guidance, API mappings, and analysis tools.

Core Features & Use Cases

  • Migration Guidance: Understand when to use @solana/kit vs. @solana/web3.js (v1).
  • API Mapping: Provides detailed comparisons and conversion examples for common Solana SDK functions.
  • Code Analysis: Includes scripts to scan codebases for patterns requiring migration.
  • Edge Case Handling: Details common pitfalls and solutions during the migration process.
  • Use Case: A developer needs to upgrade a large Solana application to use @solana/kit for performance gains but is unsure about the specific code changes required. This Skill provides the necessary documentation, examples, and analysis tools to guide the migration.

Quick Start

Use the solana-kit-migration skill to analyze the codebase at '/path/to/my/solana/project'.

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 my Solana app from @solana/web3.js v1 to @solana/kit?

To migrate your Solana app to @solana/kit, use code analysis scripts to scan your codebase for legacy patterns, then apply detailed API mapping documentation and examples to address the identified migration requirements.

When should I use @solana/kit instead of @solana/web3.js v1?

Use @solana/kit instead of @solana/web3.js v1 when your project requires performance optimization, reduced bundle size, or framework compatibility, while keeping the v1 SDK for specific legacy compatibility needs.

What is the best way to handle edge cases during Solana SDK migration?

The best way to handle edge cases during Solana SDK migration is to reference comprehensive documentation on common pitfalls and apply provided solutions for accurate conversion between the legacy and new SDK functions.

Can I analyze my codebase to find patterns requiring migration to @solana/kit?

Yes, you can analyze your codebase by running included scripts that scan your Solana project directory to automatically identify specific code patterns requiring migration to the new @solana/kit SDK.

Are there API mapping examples for converting @solana/web3.js functions?

Yes, detailed API mapping comparisons and conversion examples are provided for common Solana SDK functions, allowing you to accurately translate legacy @solana/web3.js v1 calls to the @solana/kit structure.

What dependencies are needed for a Solana SDK migration to @solana/kit?

Dependencies required for the migration include @solana/kit, @solana/web3.js, @solana/compat, @solana-program/system, @solana-program/token, and @solana-program/compute-budget to ensure full program coverage.