What problem does it solve? Solana developers face uncertainty when choosing between @solana/web3.js (v1) and @solana/kit, and migrating existing codebases involves many breaking changes: async keypair generation, BigInt amounts, functional transaction building with pipe(), and different RPC patterns that cause subtle runtime errors. ## Core Features & Use Cases - Decision Guidance: Clear criteria and a flowchart for choosing between @solana/web3.js v1, @solana/kit, or a hybrid approach using @solana/compat, including Anchor compatibility checks. - Automated Codebase Analysis: Shell and Node.js scripts scan a project for v1 patterns (Connection, Keypair, PublicKey, Transaction usage), count migration points, detect blocking dependencies, and recommend a migration strategy. - Complete API Reference: Detailed mappings for RPC calls, keypairs, transactions, subscriptions, and PDAs, plus edge-case documentation covering BigInt serialization, .send() requirements, and encoding errors. - Use Case: A developer with an existing Solana dApp runs the analysis script, discovers 120 migration points with no Anchor dependency, and follows the checklist to incrementally migrate using @solana/compat. ## Quick Start Analyze my Solana project and tell me whether I should migrate from @solana/web3.js to @solana/kit and how to do it.