In brief
PostHog Error Tracking for Nuxt
What it does
- Reference files
- Basic principles
- Framework directives
Who it is for, and an example
People whose task corresponds: PostHog error tracking for Nuxt
Example request: « PostHog Error Tracking for Nuxt: PostHog Error Tracking for Nuxt »
PostHog Error Tracking for Nuxt Example written by iadujour.fr from the SKILL.md, not tested.
Install
Claude Code : /plugin marketplace add PostHog/skills, puis /plugin install posthog-all@posthog-skills (README).
/plugin marketplace add PostHog/skills/plugin install posthog-all@posthog-skillsWorks with
- Claude Code
Source: K0: marketplace K1: K2: Other agents are not appointed.
Level: Intermediate
Supposes a project already in place at the publisher and the tools described in the K0.
Good to know
SKILL.md excerpt
The original description, which the agent reads to decide whether to load the skill (in English):
PostHog error tracking for Nuxt
Quoted from SKILL.md at commit 445764b . The folder also contains 6 extra files (references/).
The SKILL.md has 35 lines and 3 main sections:
- Reference files
- Key principles
- Framework guidelines
Licence: MIT
Checked on 13 November 2026 : fichier de licence du dépôt.
The licence allows reuse: the full SKILL.md text is reproduced below, unmodified, with its licence notice.
Full SKILL.md text
Reproduced unmodified from PostHog/skills (commit 445764b) , © PostHog, under licence MIT (original licence file ).
Show the original SKILL.md (35 lines, in English)
---
name: error-tracking-nuxt
description: PostHog error tracking for Nuxt
metadata:
author: PostHog
version: 1.9.4
---
# PostHog error tracking for Nuxt
This skill helps you add PostHog error tracking to Nuxt applications.
## Reference files
- `references/nuxt.md` - Nuxt error tracking installation (v3.7 and above) - docs
- `references/fingerprints.md` - Fingerprints - docs
- `references/alerts.md` - Send error tracking alerts - docs
- `references/monitoring.md` - Monitor and search issues - docs
- `references/assigning-issues.md` - Assign issues to teammates - docs
- `references/upload-source-maps.md` - Upload source maps - docs
Consult the documentation for API details and framework-specific patterns.
## Key principles
- **Environment variables**: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
- **Minimal changes**: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
- **Autocapture first**: Enable exception autocapture in the SDK initialization before adding manual captures.
- **Source maps**: Upload source maps so stack traces resolve to original source code, not minified bundles.
- **Manual capture for boundaries**: Use `captureException()` at error boundaries and catch blocks for errors that don't propagate to the global handler.
## Framework guidelines
_No specific framework guidelines._
Comments.
A field note, a question, a precision on this skill? Comments are reviewed before publication.
Published comments
Loading comments…
Leave a comment
Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.