Feature Flags React
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides guidance and best practices for implementing PostHog feature flags within React applications. It covers installation, flag evaluation patterns, and strategies for managing feature states effectively. The skill emphasizes performance, consistency, and clean code practices, such as using hooks for flag management and avoiding common pitfalls with React's useEffect hook.
What it does
- Provides patterns for implementing boolean and multivariate feature flags in React.
- Offers guidance on handling loading states and ensuring flags are available for use.
- Outlines best practices for flag naming, targeting, and lifecycle management.
- Explains how to use PostHog hooks for efficient flag evaluation.
- Provides strategies to prevent UI flicker and improve performance through local evaluation.
- Integrates with PostHog MCP tools for direct flag management.
When to use it
- When you need to perform controlled feature rollouts or A/B testing in a React app.
- When you want to manage feature availability without redeploying code.
- When you need to ensure consistent user experiences across sessions and devices.
- When you want to optimize feature flag performance and reduce network latency.
Advantages
- Enables safe, incremental feature releases.
- Reduces the risk of breaking changes by allowing instant toggling.
- Supports data-driven decision-making through experiments.
- Promotes clean code by encouraging centralized flag logic.
Usage examples
- “How do I check a boolean feature flag in my React component?”
- The agent will recommend using the useFeatureFlagEnabled() hook to check the flag status and handle loading states appropriately.
- “How can I avoid UI flicker when using feature flags?”
- The agent will suggest server-side flag evaluation or bootstrapping flags during initialization to ensure they are available immediately upon render.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/feature-flags-react/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip feature-flags-react.zip -d .agents/skills
Documentation by PostHog
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 - docsreferences/adding-feature-flag-code.md- Adding feature flag code - docsreferences/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)
Files
- ATTRIBUTION.mdAdded by AutoGineer957 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.2 KiB
- references/adding-feature-flag-code.md108.7 KiB
- references/best-practices.md7.9 KiB
- references/react.md8.1 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- PostHog
- Publisher
- PostHog (Official)
- Source
- PostHog/skills · skills/posthog/feature-flags/skills/react · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- PostHog/skills
AutoGineer is not affiliated with or endorsed by PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download feature-flags-react.zip