In brief
PostHog Options for React Applications
What it does
- Reference files
- Basic principles
- PostHog Tools
Who it is for, and an example
People whose task corresponds: PostHog feature flags for React applications
Example request: « PostHog Options for React: PostHog Options for React Applications »
PostHog Options for React Applications Example written by iadujour.fr from the SKILL.md, not tested.
Install
Claude Code : /plugin marketplace add PostHog/skills, puis /plugin install posthog-all@posthog-skills (README).
/plugin marketplace add PostHog/skills/plugin install posthog-all@posthog-skillsWorks with
- Claude Code
Source: K0: marketplace K1: K2: Other agents are not appointed.
Level: Intermediate
Supposes a project already in place at the publisher and the tools described in the K0.
Good to know
SKILL.md excerpt
The original description, which the agent reads to decide whether to load the skill (in English):
PostHog feature flags for React applications
Quoted from SKILL.md at commit 445764b . The folder also contains 3 extra files (references/).
The SKILL.md has 42 lines and 4 main sections:
- Reference files
- Key principles
- PostHog MCP tools
- Framework guidelines
Licence: MIT
Checked on 13 November 2026 : fichier de licence du dépôt.
The licence allows reuse: the full SKILL.md text is reproduced below, unmodified, with its licence notice.
Full SKILL.md text
Reproduced unmodified from PostHog/skills (commit 445764b) , © PostHog, under licence MIT (original licence file ).
Show the original SKILL.md (42 lines, in English)
---
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)
In the directory
Use cases and guides that share a theme, industry or tool with this skill.
Comments.
A field note, a question, a precision on this skill? Comments are reviewed before publication.
Published comments
Loading comments…
Leave a comment
Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.