Guide for feature flags and A/B tests with the Flags SDK (flags npm package) and Vercel Flags. Use when: declaring flags with flag(), using vercelAdapter or vercel flags CLI (add, list, enable, disable, inspect, archive, rm, sdk-keys), setting up providers/adapters (Vercel, Statsig, LaunchDarkly, PostHog, GrowthBook, Hypertune, Edge Config, OpenFeature, Split, Flagsmith, Reflag, Optimizely, or custom adapters), implementing precompute patterns for static pages, setting up identify/dedupe, integrating Flags Explorer/Toolbar, working with flags in Next.js (App Router, Pages Router, Middleware) or SvelteKit, writing custom adapters, or encrypting/decrypting flag values. Triggers: feature flags, A/B testing, experimentation, flags SDK, flag adapters, precompute, Flags Explorer, feature gates, flag overrides, Vercel Flags, vercel flags CLI, vercel flags add, vercel flags list, vercel flags enable, vercel flags disable, flags/next, flags/sveltekit, flags/react, @flags-sdk/*.
$npx -y skills add vercel/flags --skill flags-sdkInstalls into the current project.
Run `npx skills use "https://github.com/vercel/flags" --skill "vercel/flags/flags-sdk"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/vercel/flags" that are relevant to the current task. Run `npx skills add "https://github.com/vercel/flags"` and select the relevant skills, then follow their instructions.