How do I install the Nextjs App Router skill?

Run npx skillmds add majiayu000/nextjs-app-router-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Nextjs App Router skill do?

PostHog integration for Next.js App Router applications It is listed under Web & Frontend on SkillMD.

Is Nextjs App Router safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nextjs App Router?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nextjs App Router free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nextjs App Router?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nextjs App Router by majiayu000 — Agent Skill

Name: Nextjs App Router
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

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:

basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here
basic-integration-1.1-edit.md - PostHog Setup - Edit
basic-integration-1.2-revise.md - PostHog Setup - Revise
basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

EXAMPLE.md - Next.js App Router example project code
next-js.md - Next.js - docs
identify-users.md - Identify users - docs
basic-integration-1.0-begin.md - PostHog setup - begin
basic-integration-1.1-edit.md - PostHog setup - edit
basic-integration-1.2-revise.md - PostHog setup - revise
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

Never use useEffect() for analytics capture - it's brittle and causes errors
Prefer event handlers or routing mechanisms to trigger analytics calls
Add handlers where user actions occur rather than reacting to state changes
Remember that source code is available in the node_modules directory
Check package.json for type checking or build scripts to validate changes
posthog-js is the JavaScript SDK package name

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.

---name: nextjs-app-router-3description: PostHog integration for Next.js App Router applications--- # 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 - `EXAMPLE.md` - Next.js App Router example project code - `next-js.md` - Next.js - docs - `identify-users.md` - Identify users - docs - `basic-integration-1.0-begin.md` - PostHog setup - begin - `basic-integration-1.1-edit.md` - PostHog setup - edit - `basic-integration-1.2-revise.md` - PostHog setup - revise - `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 - Never use useEffect() for analytics capture - it's brittle and causes errors - Prefer event handlers or routing mechanisms to trigger analytics calls - Add handlers where user actions occur rather than reacting to state changes - Remember that source code is available in the node_modules directory - Check package.json for type checking or build scripts to validate changes - posthog-js is the JavaScript SDK package name ## 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.

Frequently asked questions