What problem does it solve? Adding product analytics to a Next.js App Router project requires correct client and server SDK setup, event instrumentation, and user identification, which is easy to get wrong without a guided process. ## Core Features & Use Cases - Guided four-phase integration: Plans events in a .posthog-events.json file, implements capture calls, reviews and lints the changes, then builds a PostHog dashboard and setup report. - Client and server coverage: Initializes posthog-js via instrumentation-client.ts, sets up a posthog-node server client, and configures a reverse proxy through Next.js rewrites. - User identification and error tracking: Adds identify() calls on login and signup, correlates client and server sessions via distinct ID headers, and captures exceptions around critical flows. - Use Case: Point the skill at an existing Next.js App Router codebase and receive instrumented event tracking, a configured "Analytics basics" dashboard, and a posthog-setup-report.md summarizing every change. ## Quick Start Add PostHog analytics with event tracking, user identification, and error tracking to my Next.js App Router project.