feature-flags-nextjs — Claude Code skill: what it does, how to install
feature-flags-nextjs puts PostHog feature flags into a Next.js app: checks inside components, evaluation on the server, and flag management from chat when the PostHog MCP server is connected.
MIT 140 installs ★ 80 updated 2026-10-24
npx skills add PostHog/skills --skill feature-flags-nextjs -a claude-codeWhat feature-flags-nextjs does
The skill guides an agent through adding PostHog flags to a Next.js project, from the first check in a component to server-side evaluation. Four reference files ship with it: references/react.md, references/next-js.md, references/adding-feature-flag-code.md and references/best-practices.md.
With a PostHog MCP server connected, the agent looks for its flag tools and creates, updates or deletes flags itself instead of sending you to the dashboard. Code goes in beside what already exists. Keys belong in environment variables, and the skill will not accept them pasted into source.
Server Components and Route Handlers cannot use React hooks, so the skill reaches for posthog-node there: call getAllFlags() or getFeatureFlag(), then await posthog.shutdown(). Flags that shape the initial render should be evaluated on the server and passed down as props, or the UI flickers and hydration complains. On Next.js 15.3 and newer the simplest setup initialises PostHog in instrumentation-client.ts; PostHogProvider is not needed just for flags.
What it helps with
- add a flag check to an existing Next.js component
- evaluate a flag on the server and pass it down as a prop
- create and toggle a flag from chat with the PostHog MCP tools
- stop the layout from flickering while flags load
- move event logic out of
useEffectinto a handler
Example prompts for the agent
- Add a
new-checkoutflag check toapp/page.tsxusinguseFeatureFlagEnabled - Create a boolean flag
beta-bannerin PostHog and gate the header block on it - Pass the flag value from the Server Component into the client one as a prop
How to install feature-flags-nextjs
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-nextjs -a claude-code2Manually: put the files in place
~/.claude/skills/feature-flags-nextjs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/feature-flags-nextjs/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-nextjs -a codex2Manually: put the files in place
.agents/skills/feature-flags-nextjs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-nextjs -a cursor2Manually: put the files in place
.cursor/skills/feature-flags-nextjs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/skills skills/posthog/all/skills/feature-flags-nextjs2Manually: put the files in place
.github/skills/feature-flags-nextjs/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-nextjs -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/skills --path skills/posthog/all/skills/feature-flags-nextjsManually: put the files in place
.devin/skills/feature-flags-nextjs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/skills --skill feature-flags-nextjs -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-nextjs
How do I install feature-flags-nextjs in Claude Code?
Run npx skills add PostHog/skills --skill feature-flags-nextjs -a claude-code. The skill then lives at ~/.claude/skills/feature-flags-nextjs/SKILL.md.
What does feature-flags-nextjs do?
It helps an agent wire PostHog flags into a Next.js app: checks in client components, evaluation on the server, and flag work through an MCP server.
Do I need a PostHog MCP server for it?
No. When one is connected the agent can create and change flags on its own; otherwise you make the flags in the dashboard and the skill handles the code side.
Source text
SKILL.md · MIT
--- name: feature-flags-nextjs description: PostHog feature flags for Next.js applications metadata: author: PostHog version: 1.9.4 --- # PostHog feature flags for Next.js This skill helps you add PostHog feature flags to Next.js applications. ## Reference files - `references/react.md` - React feature flags installation - docs - `references/next-js.md` - Next.js - 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 Next.js 15.3+, initialize PostHog in instrumentation-client.ts for the simplest setup - The PostHog React hooks (useFeatureFlagEnabled, useFeatureFlagPayload) work WITHOUT PostHogProvider if posthog-js is already initialized (e.g., via instrumentation-client.ts) - In client components, import and use hooks directly - the React context defaults to the posthog-js singleton - Do NOT wrap components in PostHogProvider just for feature flags - it's unnecessary if posthog-js is initialized globally - Server Components and Route Handlers cannot use React hooks - use posthog-node SDK instead - Create a server-side PostHog client with posthog-node, call getAllFlags() or getFeatureFlag(), then await posthog.shutdown() - Pass flag values from server to client components as props to avoid hydration mismatches - For flags that affect initial render, evaluate server-side and pass as props to prevent UI flicker - Client-side hooks may return undefined initially while flags load - handle this loading state - 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