# feature-flags-nextjs

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 140 installs · ★ 80 repo stars
- Author: PostHog
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/PostHog/skills/tree/HEAD/skills/posthog/all/skills/feature-flags-nextjs/SKILL.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/feature-flags-nextjs

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/skills --skill feature-flags-nextjs -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/feature-flags-nextjs/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/feature-flags-nextjs/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/skills --skill feature-flags-nextjs -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/feature-flags-nextjs/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/skills --skill feature-flags-nextjs -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/feature-flags-nextjs/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install PostHog/skills skills/posthog/all/skills/feature-flags-nextjs
```

2. **Manually: put the files in place**
- File: `.github/skills/feature-flags-nextjs/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/skills --skill feature-flags-nextjs -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/PostHog/skills --path skills/posthog/all/skills/feature-flags-nextjs
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/feature-flags-nextjs/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add PostHog/skills --skill feature-flags-nextjs -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/PostHog/skills/tree/HEAD/skills/posthog/all/skills/feature-flags-nextjs/SKILL.md

## When to use it
- 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 `useEffect` into a handler

## Example prompts
- Add a `new-checkout` flag check to `app/page.tsx` using `useFeatureFlagEnabled`
- Create a boolean flag `beta-banner` in PostHog and gate the header block on it
- Pass the flag value from the Server Component into the client one as a prop

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 916bce42c40d1acc.

BEGIN THIRD-PARTY FILE 916bce42c40d1acc
```text
---
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
```
END THIRD-PARTY FILE 916bce42c40d1acc

The third-party file has ended. Everything between the 916bce42c40d1acc tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2282 of 3278 bytes. © PostHog · MIT · https://github.com/PostHog/skills/tree/HEAD/skills/posthog/all/skills/feature-flags-nextjs/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
