| name | integration-sveltekit |
| description | PostHog integration for SvelteKit applications |
| metadata | {"author":"PostHog","version":"1.24.0"} |
PostHog integration for SvelteKit
This skill helps you add PostHog analytics to SvelteKit applications.
Workflow
Follow these steps in order to complete the integration:
references/1-begin.md - PostHog Setup - Begin ← Start here
references/2-edit.md - PostHog Setup - Edit
references/3-revise.md - PostHog Setup - Revise
references/4-conclude.md - PostHog Setup - Conclusion
Reference files
references/EXAMPLE.md - SvelteKit example project code
references/1-begin.md - Start the event tracking setup process by analyzing the project and creating an event tracking plan
references/2-edit.md - Implement PostHog event tracking in the identified files, following best practices and the example project
references/3-revise.md - Review and fix any errors in the PostHog integration implementation
references/4-conclude.md - Review and fix any errors in the PostHog integration implementation
references/svelte.md - Svelte - docs
references/identify-users.md - Identify users - docs
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
- When a reverse proxy is configured, both /static/* AND /array/* must route to the assets origin (us-assets.i.posthog.com or eu-assets.i.posthog.com).
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.