What problem does it solve? Choosing and configuring the right storage backend 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 authoritative guidance on which storage product to use, how to provision it, and how to migrate away from deprecated packages. ## Core Features & Use Cases - Storage Decision Matrix: Maps needs like file uploads, feature flags, relational data, caching, and vector search to the correct product (Vercel Blob, Global Config, Neon Postgres, Upstash Redis, Supabase, Prisma, MongoDB Atlas, Convex, Turso). - Deprecation & Migration Guidance: 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 import @vercel/kv in a Next.js project and need to migrate to Upstash Redis with Marketplace provisioning and unified billing without breaking your build. ## Quick Start Ask the agent to help you choose and set up the right Vercel storage option for your project, or to migrate an existing @vercel/postgres or @vercel/kv integration to its supported replacement.