What problem does it solve? Choosing and configuring the right data storage for a Vercel application is confusing, especially since @vercel/postgres and @vercel/kv are sunset and Edge Config was renamed to Global Config. This Skill provides expert guidance on which storage product to use, how to provision it, and how to migrate away from deprecated packages. ## Core Features & Use Cases - Storage Selection Guidance: Decision matrix mapping needs (file uploads, feature flags, relational data, caching) to the correct product: Vercel Blob, Global Config, Neon Postgres, Upstash Redis, Supabase, Prisma, MongoDB Atlas, Convex, or Turso. - Deprecation Detection & Migration: Detects usage of sunset packages (@vercel/postgres, @vercel/kv, @vercel/edge-config) and provides drop-in migration paths to @neondatabase/serverless, @upstash/redis, and @vercel/global-config. - Provisioning Workflows: Covers Vercel Marketplace installation via vercel integration add, automatic environment variable provisioning, and fallback manual setup with vercel env pull. - Use Case: You are building a Next.js app that needs file uploads and a Postgres database. The Skill directs you to install @vercel/blob for media and provision Neon Postgres through the Marketplace with lazy initialization to avoid build-time crashes. ## Quick Start Ask the assistant to help you choose and set up the right Vercel storage option for your project, such as adding Neon Postgres or migrating off @vercel/kv.