About integration-sveltekit
A skill for adding PostHog analytics to SvelteKit applications. It guides implementation through a staged workflow, with framework-specific setup, user identification, and error tracking guidance.
Key features
- 01Four-step integration workflow
- 02SvelteKit setup guidance
- 03Environment-variable key handling
- 04User identification guidance
- 05Error tracking guidance
- 06Svelte component validation
Use cases
- 01Adding PostHog to a SvelteKit app
- 02Instrumenting login and signup
- 03Adding error tracking to critical flows
MCP support
The skill instructs users to use Svelte MCP server tools to consult documentation and validate components.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ posthog/ skills --skill integration-sveltekitAfter installing, type/integration-sveltekitin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/basic-integration-1.0-begin.mdbasic-integration-1.1-edit.mdbasic-integration-1.2-revise.mdbasic-integration-1.3-conclude.mdEXAMPLE.mdidentify-users.mdsvelte.mdDetails
From the project READMEPostHog integration for SvelteKit
This skill helps you add PostHog analytics to SvelteKit applications.
Workflow
Follow these steps in order to complete the integration:
basic-integration-1.0-begin.md- PostHog Setup - Begin ← Start herebasic-integration-1.1-edit.md- PostHog Setup - Editbasic-integration-1.2-revise.md- PostHog Setup - Revisebasic-integration-1.3-conclude.md- PostHog Setup - Conclusion
Reference files
references/EXAMPLE.md- SvelteKit example project codereferences/svelte.md- Svelte - docsreferences/identify-users.md- Identify users - docsreferences/basic-integration-1.0-begin.md- PostHog setup - beginreferences/basic-integration-1.1-edit.md- PostHog setup - editreferences/basic-integration-1.2-revise.md- PostHog setup - revisereferences/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.