
This helps you decide whether to migrate from Solana's web3.js v1 to the newer @solana/kit and actually do it without breaking things. It walks through dependency analysis (especially Anchor, which blocks migration), provides API mappings for the trickiest conversions like Connection to RPC and Transaction building, and catches the gotchas that will bite you like forgetting BigInt conversions or the async keypair generation. The decision tree is genuinely useful: new non-Anchor projects should use Kit for the 26% smaller bundles and better performance, but if you're using Anchor or have a large codebase that works fine, stay put. The hybrid approach with @solana/compat is probably the smartest path for real production apps.
$ npx -y skills add sendaifun/skills --skill solana-kit-migration --agent claude-codeInstalls into .claude/skills of the current project.
This skill helps you navigate the transition between @solana/web3.js (v1.x) and @solana/kit (formerly web3.js 2.0), providing guidance on when to use each library and how to migrate between them.
The Solana JavaScript ecosystem has two major SDK options:
| Library | Status | Use Case |
|---|---|---|
@solana/web3.js (1.x) | Maintenance mode | Legacy projects, Anchor-dependent apps |
@solana/kit | Active development | New projects, performance-critical apps |
Key Decision: @solana/kit is the future, but migration isn't always straightforward.
Sponsors