AutoGineer
Generated banner for Integration Nuxt 3 6
Generated logo for Integration Nuxt 3 6

Integration Nuxt 3 6

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

PostHog integration for Nuxt versions 3.0 to 3.6
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a step-by-step procedure for adding PostHog analytics to Nuxt 3.6 projects. Because Nuxt 3.0-3.6 does not support the standard @posthog/nuxt package, this workflow guides developers through manual implementation using posthog-js and posthog-node. It covers client-side initialization, server-side tracking, user identification, and error tracking to ensure a complete analytics setup.

What it does

  • Guides the manual installation of PostHog packages for Nuxt 3.6
  • Provides a structured 4-step integration workflow
  • Demonstrates client-side plugin configuration for Nuxt
  • Outlines patterns for server-side event tracking in API routes
  • Explains how to identify users and maintain session correlation
  • Includes instructions for implementing error tracking

When to use it

  • When you need to add PostHog analytics to a Nuxt 3.0 through 3.6 application
  • When you require both client-side and server-side event tracking
  • When you need to implement user identification and error tracking in a Nuxt 3 environment
  • When you want to follow established patterns for environment variable management and API integration

Advantages

  • Provides a clear, sequential path for integration
  • Ensures consistent implementation of server-side and client-side tracking
  • Promotes best practices like using environment variables for sensitive keys
  • Offers a reference project to verify implementation patterns

Usage examples

“How do I start integrating PostHog into my Nuxt 3.6 project?”
The agent will initiate the workflow, starting with the setup phase and guiding you through the required file analysis and dependency verification.
“How should I handle user identification in Nuxt 3.6 with PostHog?”
The agent will direct you to the identification patterns, explaining how to use client-side login events and pass session headers to the backend.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/integration-nuxt-3-6/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip integration-nuxt-3-6.zip -d .agents/skills

Documentation by PostHog

PostHog integration for Nuxt 3.6

This skill helps you add PostHog analytics to Nuxt 3.6 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 - Nuxt 3.6 example project code

  • references/nuxt-js-3-6.md - Nuxt.js (v3.0 to v3.6) - 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

No specific framework guidelines.

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.

Files

references/basic-integration-1.3-conclude.md

title: PostHog Setup - Conclusion description: Review and fix any errors in the PostHog integration implementation

Use the PostHog MCP to create a new dashboard named "Analytics basics" based on the events created here. Make sure to use the exact same event names as implemented in the code. Populate it with up to five insights, with special emphasis on things like conversion funnels, churn events, and other business critical insights.

Search for a file called .posthog-events.json and read it for available events. Do not spawn subagents.

Create the file posthog-setup-report.md. It should include a summary of the integration edits, a table with the event names, event descriptions, and files where events were added, along with a list of links for the dashboard and insights created. Follow this format:

<wizard-report> # PostHog post-wizard report

The wizard has completed a deep integration of your project. [Detailed summary of changes]

[table of events/descriptions/files]

Next steps

We've built some insights and a dashboard for you to keep an eye on user behavior, based on the events we just instrumented:

[links]

Agent skill

We've left an agent skill folder in your project. You can use this context for further agent development when using Claude Code. This will help ensure the model provides the most up-to-date approaches for integrating PostHog.

</wizard-report>

Upon completion, remove .posthog-events.json.

Status

Status to report in this phase:

  • Configured dashboard: [insert PostHog dashboard URL]

  • Created setup report: [insert full local file path]

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.

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/integration/skills/nuxt-3.6 · 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.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download integration-nuxt-3-6.zip