feature-flags-react — Claude Code skill: PostHog flags in React
feature-flags-react adds PostHog feature flag checks to a React app and keeps them clear of the code that already works.
MIT 112 installs ★ 80 updated 2026-10-24
npx skills add PostHog/skills --skill feature-flags-react -a claude-codeWhat feature-flags-react does
This skill adds PostHog feature flags to a React app. It carries three reference docs: installation, flag code samples, and practices. Plus a short list of rules for hooks and useEffect that the agent follows while editing.
Keys stay in environment variables; the skill never hardcodes them. Flag code lands next to what already exists instead of replacing it, and boolean checks are the default unless you ask for multivariate. With a PostHog MCP server connected, it looks for flag-management tools and creates or edits flags from the editor rather than sending you to the dashboard.
Flags read through useFeatureFlagEnabled() and useFeatureFlagPayload(), which handle loading state and external sync. Analytics calls belong in event handlers — the skill rules out useEffect for reacting to state, chaining updates, or notifying parents. Server-side evaluation is its preference, because client checks can flicker the UI. This is a React skill; other frameworks fall outside what the reference files describe.
What it helps with
- Gate a new component behind a PostHog flag without touching the surrounding code
- Create and list flags from the editor through the PostHog MCP server
- Cut UI flicker by evaluating flags on the server
- Move analytics calls out of
useEffectand into event handlers - Keep PostHog keys in environment variables
Example prompts for the agent
- Add a PostHog flag called
new-checkoutaround the checkout form - Create a boolean flag
beta-bannerin PostHog and wrap the homepage banner with it - Review the flag hooks and
useEffectusage insrc/App.tsx
How to install feature-flags-react
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-react -a claude-code2Manually: put the files in place
~/.claude/skills/feature-flags-react/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/feature-flags-react/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-react -a codex2Manually: put the files in place
.agents/skills/feature-flags-react/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-react -a cursor2Manually: put the files in place
.cursor/skills/feature-flags-react/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/skills skills/posthog/all/skills/feature-flags-react2Manually: put the files in place
.github/skills/feature-flags-react/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-react -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/skills --path skills/posthog/all/skills/feature-flags-reactManually: put the files in place
.devin/skills/feature-flags-react/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-react -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about feature-flags-react
How do I install feature-flags-react in Claude Code?
Run npx skills add PostHog/skills --skill feature-flags-react -a claude-code. The skill lands at ~/.claude/skills/feature-flags-react/SKILL.md.
What does feature-flags-react do?
It walks the agent through adding PostHog feature flags to a React app: flag checks in components, hook usage, and reference docs on setup and practices.
Do I need the PostHog MCP server?
No. When it is connected, the skill manages flags with its tools; otherwise you create them in the PostHog dashboard yourself.
Source text
SKILL.md · MIT
--- name: feature-flags-react description: PostHog feature flags for React applications metadata: author: PostHog version: 1.9.4 --- # PostHog feature flags for React This skill helps you add PostHog feature flags to React applications. ## Reference files - `references/react.md` - React feature flags installation - docs - `references/adding-feature-flag-code.md` - Adding feature flag code - docs - `references/best-practices.md` - Feature flag best practices - docs Consult the documentation for API details and framework-specific patterns. ## Key principles - **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them. - **Minimal changes**: Add feature flag code alongside existing logic. Don't replace or restructure existing code. - **Boolean flags first**: Default to boolean flag checks unless the user specifically asks for multivariate flags. - **Server-side when possible**: Prefer server-side flag evaluation to avoid UI flicker. ## PostHog MCP tools Check if a PostHog MCP server is connected. If available, look for tools related to feature flag management (creating, listing, updating, deleting flags). Use these tools to manage flags directly in PostHog rather than requiring the user to do it manually in the dashboard. ## Framework guidelines - For feature flags, use useFeatureFlagEnabled() or useFeatureFlagPayload() hooks - they handle loading states and external sync automatically - Add analytics capture in event handlers where user actions occur, NOT in useEffect reacting to state changes - Do NOT use useEffect for data transformation - calculate derived values during render instead - Do NOT use useEffect to respond to user events - put that logic in the event handler itself - Do NOT use useEffect to chain state updates - calculate all related updates together in the event handler - Do NOT use useEffect to notify parent components - call the parent callback alongside setState in the event handler - To reset component state when a prop changes, pass the prop as the component's key instead of using useEffect - useEffect is ONLY for synchronizing with external systems (non-React widgets, browser APIs, network subscriptions)
© PostHog · MIT · PostHog/skills