What problem does it solve? Adding third-party capabilities like commerce, payments, email, or monitoring to a Vercel app often leads to hand-built scaffolding that gets thrown away once a real integration is provisioned. This Skill enforces the correct categorize → discover → install → build sequence so integrations are provisioned first and the app is built around real environment variables. ## Core Features & Use Cases - Guided provider selection: Recommends preferred providers (Shopify for commerce, Stripe for payments) and falls back to top discover results for other categories. - CLI-driven provisioning: Uses vercel integration categories, discover, add, and env pull to install integrations with automatic env vars and unified billing. - Category mapping: Maps needs like messaging, observability, search, CMS, feature flags, and video to the correct Marketplace category, while routing storage, auth, and AI needs to dedicated skills. - Use Case: When building a storefront, run discovery in the commerce category, install Shopify via the CLI, pull the real env vars, and only then build the catalog, cart, and checkout against them. ## Quick Start Ask the assistant to discover and install the right Vercel Marketplace integration for your app's payment or commerce need before writing any code.
