AutoGineer
Generated banner for Integration Sveltekit
Generated logo for Integration Sveltekit

Integration Sveltekit

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog integration for SvelteKit applications
— the description by PostHog

AutoGineer summary

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

This skill provides a comprehensive, step-by-step procedure for adding PostHog analytics to SvelteKit projects. It covers client-side initialization, server-side tracking, user identification, and error tracking. The workflow emphasizes best practices such as using environment variables, implementing reverse proxies to bypass ad blockers, and maintaining consistency with provided example patterns.

What it does

  • Guides users through a multi-step integration process for PostHog in SvelteKit.
  • Provides patterns for both client-side and server-side event tracking.
  • Includes instructions for user identification and error tracking implementation.
  • Details the configuration of reverse proxies to improve data reliability.
  • Requires the use of environment variables for secure credential management.
  • Mandates validation of Svelte components using provided tooling.

When to use it

  • When you need to add analytics to a new or existing SvelteKit application.
  • When you want to track user behavior across both client and server environments.
  • When you need to implement robust error tracking within a SvelteKit project.
  • When you are setting up session replay and require specific SvelteKit configuration adjustments.

Advantages

  • Ensures a consistent and reliable integration pattern.
  • Promotes secure handling of API keys via environment variables.
  • Addresses common SvelteKit-specific pitfalls like SSR compatibility.
  • Facilitates accurate user correlation between frontend and backend.

Usage examples

“How do I start integrating PostHog into my SvelteKit app?”
The agent initiates the workflow, starting with the 'PostHog Setup - Begin' phase to analyze your project structure and create an event tracking plan.
“How should I handle server-side tracking in SvelteKit?”
The agent directs you to use the singleton pattern in 'src/lib/server/posthog.ts' as shown in the reference example.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/integration-sveltekit/download

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

    mkdir -p .agents/skills && unzip integration-sveltekit.zip -d .agents/skills

Documentation by PostHog

PostHog integration for SvelteKit

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

  • references/svelte.md - Svelte - 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

  • 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

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.

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/integration/skills/sveltekit · 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 integration-sveltekit.zip