Error Tracking Svelte
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides guidance and best practices for implementing PostHog error tracking within Svelte and SvelteKit projects. It covers essential setup steps, including SDK initialization, environment variable management, and source map configuration to ensure stack traces are readable. The skill emphasizes non-intrusive integration, recommending that developers maintain existing error handling logic while leveraging PostHog for automated exception capture and manual boundary monitoring.
What it does
- Guides the installation of PostHog error tracking in Svelte applications.
- Explains how to configure source maps for clear, unminified stack traces.
- Provides patterns for using captureException at error boundaries.
- Outlines best practices for managing PostHog keys using environment variables.
- Details how to set up alerts and automated issue assignment for team workflows.
- Offers configuration tips for SvelteKit SSR compatibility.
When to use it
- When you need to monitor runtime errors in a Svelte or SvelteKit application.
- When you want to centralize error reporting and issue triaging in PostHog.
- When you need to resolve minified stack traces to original source code.
- When you want to set up automated alerts for specific error spikes or types.
Advantages
- Maintains existing application error handling structures.
- Enables automated exception capture alongside manual error boundary tracking.
- Improves debugging efficiency through unminified stack traces.
- Facilitates team collaboration with automated issue assignment and alerting.
Usage examples
- “How do I set up PostHog error tracking in my SvelteKit project?”
- The agent provides the steps to initialize the PostHog SDK, configure environment variables, and ensure paths.relative is set to false in svelte.config.js.
- “How can I ensure my stack traces are readable in PostHog?”
- The agent explains the process of uploading source maps to PostHog so that minified bundles are mapped back to your original source code.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/error-tracking-svelte/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip error-tracking-svelte.zip -d .agents/skills
Documentation by PostHog
PostHog error tracking for Svelte
This skill helps you add PostHog error tracking to Svelte applications.
Reference files
references/svelte.md- Sveltekit error tracking installation - docsreferences/fingerprints.md- Fingerprints - docsreferences/alerts.md- Send error tracking alerts - docsreferences/monitoring.md- Monitor and search issues - docsreferences/assigning-issues.md- Assign issues to teammates - docsreferences/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
Set paths.relative to false in svelte.config.js — this is required for PostHog session replay to work correctly with SSR and is easy to miss
Use the Svelte MCP server tools to check Svelte documentation (list-sections, get-documentation) and validate components (svelte-autofixer) — always run svelte-autofixer on new or modified .svelte files before finishing
Files
- ATTRIBUTION.mdAdded by AutoGineer963 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.7 KiB
- references/alerts.md4.1 KiB
- references/assigning-issues.md5.5 KiB
- references/fingerprints.md3.4 KiB
- references/monitoring.md8.6 KiB
- references/svelte.md4.8 KiB
- references/upload-source-maps.md2.7 KiB
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.
Needs: Needs an MCP server
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/error-tracking/skills/svelte · 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 or PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download error-tracking-svelte.zip