Skip to main content
skill CX Codex

integration-nextjs-app-router — Claude Code skill: setup guide

integration-nextjs-app-router adds PostHog analytics to Next.js App Router projects following official four-stage workflow guidelines and clean state patterns.

MIT 328 installs ★ 80 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/skills --skill integration-nextjs-app-router -a claude-code
Open on GitHub

What integration-nextjs-app-router does

The skill guides an AI agent through a four-phase workflow to embed PostHog into Next.js App Router applications. It emphasizes minimal edits alongside current codebase logic, refusing to restructure components unnecessarily.

It enforces strict React practices. Analytics captures belong in event handlers rather than useEffect hooks. For Next.js 15.3 and newer, PostHog initializes inside instrumentation-client.ts. To correlate events across client and server boundaries, the agent forwards X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers. Feature flags use useFeatureFlagEnabled() or useFeatureFlagPayload() to handle async states cleanly.

API keys must live strictly in environment variables; hardcoding them will violate the skill's safety rules.

What it helps with

  • Integrate PostHog analytics into a Next.js App Router codebase
  • Implement feature flags using useFeatureFlagEnabled hooks
  • Correlate frontend and backend events via session and distinct ID headers
  • Add error tracking across critical user flows and API endpoints

Example prompts for the agent

  • Integrate PostHog into our Next.js App Router app using the official step-by-step skill.
  • Set up a PostHog feature flag check in this component following the skill rules.
  • Add user identification on signup and forward the session headers to backend routes.

How to install integration-nextjs-app-router

1Skills CLI (Vercel)

npx skills add PostHog/skills --skill integration-nextjs-app-router -a claude-code

2Manually: put the files in place

~/.claude/skills/integration-nextjs-app-router/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/integration-nextjs-app-router/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about integration-nextjs-app-router

How to install integration-nextjs-app-router in Claude Code?

Run npx skills add PostHog/skills --skill integration-nextjs-app-router -a claude-code. The skill file will be created at ~/.claude/skills/integration-nextjs-app-router/SKILL.md.

What does the integration-nextjs-app-router skill do?

It provides prescriptive instructions and reference patterns for adding PostHog tracking, feature flags, and user identification to Next.js App Router apps.

How should PostHog be initialized in Next.js 15.3+?

The skill specifies putting the client initialization inside instrumentation-client.ts for the simplest implementation.

Source text

SKILL.md · MIT
---
name: integration-nextjs-app-router
description: PostHog integration for Next.js App Router applications
metadata:
  author: PostHog
  version: 1.9.4
---

# PostHog integration for Next.js App Router

This skill helps you add PostHog analytics to Next.js App Router applications.

## Workflow

Follow these steps in order to complete the integration:

1. `basic-integration-1.0-begin.md` - PostHog Setup - Begin ← **Start here**
2. `basic-integration-1.1-edit.md` - PostHog Setup - Edit
3. `basic-integration-1.2-revise.md` - PostHog Setup - Revise
4. `basic-integration-1.3-conclude.md` - PostHog Setup - Conclusion

## Reference files

- `references/EXAMPLE.md` - Next.js App Router example project code
- `references/next-js.md` - Next.js - docs
- `references/identify-users.md` - Identify users - docs
- `references/basic-integration-1.0-begin.md` - PostHog setup - begin
- `references/basic-integration-1.1-edit.md` - PostHog setup - edit
- `references/basic-integration-1.2-revise.md` - PostHog setup - revise
- `references/basic-integration-1.3-conclude.md` - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

## Key principles

- **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them.
- **Minimal changes**: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
- **Match the example**: Your implementation should follow the example project's patterns as closely as possible.

## Framework guidelines

- For Next.js 15.3+, initialize PostHog in instrumentation-client.ts for the simplest setup
- 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)

## Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` headers to maintain correlation.

## Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

© PostHog · MIT · PostHog/skills

Similar skills

All skills for Frontend and UI →

From the same set112

The whole set →
downloading-batch-export-files downloading-batch-export-files starts on-demand PostHog exports for events or HogQL queries and downloads resulting Parquet or JSONLines files directly via REST. CX Codex +1 348installs suppressing-noisy-errors suppressing-noisy-errors configures PostHog error tracking suppression rules to drop unactionable client-side noise and crawler traffic at ingestion. CX Codex +1 345installs signals-scout-general signals-scout-general — a PostHog skill that hunts cross-product correlations and covers surfaces the per-product scouts skip. Files findings as inbox reports. CX Codex +1 343installs designing-email-templates designing-email-templates is a Claude Code skill that drafts and edits email templates in PostHog via MCP. Runs whenever you build or update workflow campaigns. CX Codex +1 332installs finding-sessions-to-watch finding-sessions-to-watch turns a vague session replay goal into a short list of recordings worth opening, from signup and pricing flows to errors and rageclicks. CX Codex +1 327installs creating-replay-vision-scanners creating-replay-vision-scanners configures PostHog Replay Vision scanners and verifies credit budgets before background session sweeps begin. CX Codex +1 326installs consuming-endpoints-from-client-code consuming-endpoints-from-client-code guides integrating PostHog endpoints into apps and services. Covers OpenAPI generation, variable formatting, and request handling. CX Codex +1 322installs creating-ai-subscription The creating-ai-subscription Claude Code skill creates recurring PostHog reports from free-text prompts. The generated Markdown report is delivered by email, Slack, or Microsoft Teams on a schedule. CX Codex +1 321installs

Project sponsors

Companies that keep this analytics open