Feature Flags Nextjs
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 a Next.js environment. It covers initialization, client-side and server-side evaluation, and strategies to prevent common issues like UI flickering or hydration mismatches. The skill emphasizes efficient flag management, proper use of environment variables, and architectural patterns for clean code integration.
What it does
- Provides patterns for initializing PostHog in Next.js applications.
- Explains how to perform server-side flag evaluation to prevent UI flicker.
- Offers guidance on using React hooks for client-side flag management.
- Details how to use the posthog-node SDK for server-side components and route handlers.
- Outlines best practices for flag naming, targeting, and local evaluation.
- Includes instructions for bootstrapping flags to ensure immediate availability.
When to use it
- When you need to implement feature toggles or experiments in a Next.js project.
- When you want to perform server-side feature flag evaluation to improve performance.
- When you need to manage feature flags across both client and server components.
- When you want to follow established best practices for flag naming and maintenance.
Advantages
- Reduces UI flicker by enabling server-side flag evaluation.
- Ensures consistent user experiences through proper identification and targeting.
- Promotes clean code by recommending centralized flag logic.
- Provides clear separation between client-side hooks and server-side SDK usage.
Usage examples
- “How do I check a boolean feature flag in a Next.js client component?”
- The agent will explain using the useFeatureFlagEnabled hook from the posthog-js library, noting that it works automatically if PostHog is initialized globally.
- “How can I evaluate a feature flag in a Next.js Server Component?”
- The agent will guide you to use the posthog-node SDK to fetch the flag value on the server and pass it as a prop to your component.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/feature-flags-nextjs/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip feature-flags-nextjs.zip -d .agents/skills
Documentation by PostHog
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 - docsreferences/next-js.md- Next.js - 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 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)
Files
- ATTRIBUTION.mdAdded by AutoGineer960 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md3.2 KiB
- references/adding-feature-flag-code.md108.7 KiB
- references/best-practices.md7.9 KiB
- references/next-js.md12.5 KiB
- references/react.md8.1 KiB
references/react.md
React feature flags installation - Docs
1
Install the package
Required
Install
posthog-jsand@posthog/reactusing your package manager:PostHog AI
npm
npm install posthog-js @posthog/reactyarn
yarn add posthog-js @posthog/reactpnpm
pnpm add posthog-js @posthog/react2
Add environment variables
Required
Add your PostHog project token and host to your environment variables. For Vite-based React apps, use the
VITE_PUBLIC_prefix:.env
PostHog AI
VITE_PUBLIC_POSTHOG_PROJECT_TOKEN=<ph_project_token> VITE_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com3
Initialize PostHog
Required
Wrap your app with the
PostHogProvidercomponent at the root of your application (such asmain.tsxif you're using Vite):main.tsx
PostHog AI
import { StrictMode } from 'react' import { createRoot } from 'react-dom/client' import './index.css' import App from './App.jsx' import { PostHogProvider } from '@posthog/react' const options = { api_host: import.meta.env.VITE_PUBLIC_POSTHOG_HOST, defaults: '2026-01-30', } as const createRoot(document.getElementById('root')).render( <StrictMode> <PostHogProvider apiKey={import.meta.env.VITE_PUBLIC_POSTHOG_PROJECT_TOKEN} options={options}> <App /> </PostHogProvider> </StrictMode> )defaults option
The
defaultsoption automatically configures PostHog with recommended settings for new projects. See SDK defaults for details.4
Accessing PostHog in your code
Recommended
Use the
usePostHoghook to access the PostHog instance in any component wrapped byPostHogProvider:MyComponent.tsx
PostHog AI
import { usePostHog } from '@posthog/react' function MyComponent() { const posthog = usePostHog() function handleClick() { posthog.capture('button_clicked', { button_name: 'signup' }) } return <button onClick={handleClick}>Sign up</button> }You can also import
posthogdirectly for non-React code or utility functions:utils/analytics.ts
PostHog AI
import posthog from 'posthog-js' export function trackPurchase(amount: number) { posthog.capture('purchase_completed', { amount }) }5
Send events
Recommended
Click around and view a couple pages to generate some events. PostHog automatically captures pageviews, clicks, and other interactions for you.
If you'd like, you can also manually capture custom events:
JavaScript
PostHog AI
posthog.capture('my_custom_event', { property: 'value' })6
Use feature flags
Required
Using hooks
PostHog provides several hooks to make it easy to use feature flags in your React app. Use
useFeatureFlagEnabledfor boolean flags:import { useFeatureFlagEnabled } from '@posthog/react' function App() { const showWelcomeMessage = useFeatureFlagEnabled('flag-key') const payload = useFeatureFlagPayload('flag-key') return ( <div className="App"> {showWelcomeMessage ? ( <div> <h1>Welcome!</h1> <p>Thanks for trying out our feature flags.</p> </div> ) : ( <div> <h2>No welcome message</h2> <p>Because the feature flag evaluated to false.</p> </div> )} </div> ) }Multivariate flags
For multivariate flags, use
useFeatureFlagVariantKey:import { useFeatureFlagVariantKey } from '@posthog/react' function App() { const variantKey = useFeatureFlagVariantKey('show-welcome-message') let welcomeMessage = '' if (variantKey === 'variant-a') { welcomeMessage = 'Welcome to the Alpha!' } else if (variantKey === 'variant-b') { welcomeMessage = 'Welcome to the Beta!' } return ( <div className="App"> {welcomeMessage ? ( <div> <h1>{welcomeMessage}</h1> <p>Thanks for trying out our feature flags.</p> </div> ) : ( <div> <h2>No welcome message</h2> <p>Because the feature flag evaluated to false.</p> </div> )} </div> ) }Flag payloads
The
useFeatureFlagPayloadhook does not send a$feature_flag_calledevent, which is required for experiments. Always use it withuseFeatureFlagEnabledoruseFeatureFlagVariantKey:import { useFeatureFlagPayload, useFeatureFlagEnabled } from '@posthog/react' function App() { const variant = useFeatureFlagEnabled('show-welcome-message') const payload = useFeatureFlagPayload('show-welcome-message') return ( <> {variant ? ( <div className="welcome-message"> <h2>{payload?.welcomeTitle}</h2> <p>{payload?.welcomeMessage}</p> </div> ) : ( <div> <h2>No custom welcome message</h2> <p>Because the feature flag evaluated to false.</p> </div> )} </> ) }Using PostHogFeature component
The
PostHogFeaturecomponent simplifies code by handling feature flag related logic:App.tsx
PostHog AI
import { PostHogFeature } from '@posthog/react' function App() { return ( <PostHogFeature flag='show-welcome-message' match={true}> <div> <h1>Hello</h1> <p>Thanks for trying out our feature flags.</p> </div> </PostHogFeature> ) }The
matchprop can be eithertrue, or the variant key, to match on a specific variant. If you also want to show a default message, you can pass these in thefallbackprop.If your flag has a payload, you can pass a function to children whose first argument is the payload:
App.tsx
PostHog AI
<PostHogFeature flag='show-welcome-message' match={true}> {(payload) => { return ( <div> <h1>{payload.welcomeMessage}</h1> <p>Thanks for trying out our feature flags.</p> </div> ) }} </PostHogFeature>7
Running experiments
Optional
Experiments run on top of our feature flags. Once you've implemented the flag in your code, you run an experiment by creating a new experiment in the PostHog dashboard.
8
Next steps
Recommended
Now that you're evaluating flags, continue with the resources below to learn what else Feature Flags enables within the PostHog platform.
Resource Description Creating a feature flag How to create a feature flag in PostHog Adding feature flag code How to check flags in your code for all platforms Framework-specific guides Setup guides for React Native, Next.js, Flutter, and other frameworks How to do a phased rollout Gradually roll out features to minimize risk More tutorials Other real-world examples and use cases
Community questions
Ask a question
Was this page useful?
HelpfulCould be better
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, Needs Node.js
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/nextjs · 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 or PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download feature-flags-nextjs.zip