Vercel Flags

Vercel Flags is Vercel's feature flags platform. Flags are created and managed in the Vercel dashboard or with the vercel flags CLI, evaluated server-side in your app, and switched per environment (Development, Preview, Production) without a redeploy.

• Docs: https://vercel.com/docs/flags
• CLI reference: https://vercel.com/docs/cli/flags

Use this skill to decide how a feature should be flagged, to create and change flags, and to run rollouts and experiments. Write app code with the skill that matches the stack (see Choose an approach). Do not leave CLI steps as "next steps" for the user; execute them yourself.

Route the request

• Planning ("put this behind a flag", "roll this out to 10%", "A/B test the pricing page", "add a kill switch"): follow Plan a flag, then Choose an approach.
• Create or manage a flag with no code change (create, inspect, enable, set, split, rollout, rules, archive): follow Manage flags with the CLI. This needs an authenticated CLI, not SDK packages, Toolbar, Flags Explorer, or .env.local (except vercel flags override, which reads FLAGS_SECRET).
• Share flags between projects: follow Project Connections to connect projects in the same team, then configure the consumer application.
• Clean up or remove a flag ("remove this flag", "clean up stale flags", "inline this flag"): follow references/cleanup.md, then Lifecycle and safety before archiving.
• Add a flag to an app that already uses the Flags SDK (flags in package.json): load the flags-sdk skill right away; it creates the flag on Vercel and declares it in code.
• Implement in code otherwise: follow Choose an approach and load the matching skill or reference. Inside an app repository, treat an ambiguous request as plan, create, and implement.

Choose an approach