feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/react/react /tmp/react && ln -s /tmp/react/.claude/skills/feature-flags ~/.claude/skills/feature-flagsFrom README
React Feature Flags Flag Files | File | Purpose | |------|---------| | packages/shared/ReactFeatureFlags.js | Default flags (canary), EXPERIMENTAL overrides | | packages/shared/forks/ReactFeatureFlags.www.js | www channel, VARIANT overrides | | packages/shared/forks/ReactFeatureFlags.native-fb.js | React Native, VARIANT overrides | | packages/shared/forks/ReactFeatureFlags.test-renderer.js | Test renderer | Gating Tests @gate pragma (test-level) Use when the feature is completely unavailable without the flag: gate() inline (assertion-level) Use when the feature exists but behavior differs based on flag: Adding a New Flag Add to ReactFeatureFlags.js with default value Add to each fork file (.www.js, .native-fb.js, etc.) If it should vary in www/RN, set to VARIANT in the fork file Gate tests with @gate flagName or inline gate() Checking Flag States Use /flags to view states across channels. See the flags skill for full command options.
More from this repo
extract-errors
Used when adding new error messages to React, or seeing "unknown error code" warnings.
flags
Used when you need to check feature flag states, compare channels, or debug why a feature behaves differently across...
flow
Used when you need to run Flow type checking, or when seeing Flow type errors in React code.