flags▌

Use this skill when adding or changing framework feature flags in Next.js internals.

The Flags SDK (flags npm package) is a feature flags toolkit for Next.js and SvelteKit. It turns each feature flag into a callable function, works with any flag provider via adapters, and keeps pages static using the precompute pattern. Vercel Flags is the first-party provider, letting you manage flags from the Vercel dashboard or the vercel flags CLI.

Inspect and compare feature flag states across React release channels. \n \n View all flags across channels (www, www-modern, canary, next, experimental, rn variants) or compare specific channels with --diff \n Output formats include default table view, CSV export, and cleanup status grouping \n Flag states indicated by symbols: enabled (✅), disabled (❌), variant testing (🧪), profiling-only (📊) \n Common pitfall: __VARIANT__ flags are tested in both states on www; use --diff to spot meaningful

Manage React feature flags across channels, gate tests conditionally, and debug flag-specific test failures. \n \n Four flag files control defaults and channel-specific overrides (canary, www, React Native, test renderer) with __VARIANT__ flags simulating gatekeepers tested in both states \n Use @gate flagName pragma to skip tests entirely when a flag is unavailable, or inline gate() to branch assertions when behavior differs \n Adding a new flag requires entries in the main file plus all fork f