integration-tanstack-start — Claude Code skill: PostHog
The integration-tanstack-start skill adds PostHog analytics to TanStack Start apps, covering client tracking, server events, user identity, feature flags, and errors.
MIT 268 installs ★ 80 updated 2026-10-24
npx skills add PostHog/skills --skill integration-tanstack-start -a claude-codeWhat integration-tanstack-start does
The skill guides a PostHog setup in a TanStack Start application through four stages: begin, edit, revise, and conclude. It includes a sample project plus reference material for TanStack Start, user identification, and each setup stage.
Its guidance separates browser and server work. Put PostHogProvider in the root route, use posthog-node for API-side capture, and rely on TanStack Router navigation events for pageviews. It also covers feature flags, login and signup identification, and error tracking. PostHog keys belong in environment variables, while the server client should be kept as a singleton.
When both sides of the app are present, the skill carries the distinct ID and session ID through X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers. It directs event capture into user-action handlers rather than useEffect, so existing event logic may need adjustment.
What it helps with
- add PostHog to a TanStack Start application
- set up client tracking in the root route
- capture API events with
posthog-node - connect browser and server user sessions
- track feature flags and application errors
Example prompts for the agent
- Add PostHog to this TanStack Start app using the skill’s workflow.
- Set up browser tracking with
PostHogProviderin__root.tsx, then useposthog-nodefor API event capture. - Review login and signup, identify users, and pass
X-POSTHOG-DISTINCT-IDwithX-POSTHOG-SESSION-ID.
How to install integration-tanstack-start
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-tanstack-start -a claude-code2Manually: put the files in place
~/.claude/skills/integration-tanstack-start/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/integration-tanstack-start/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-tanstack-start -a codex2Manually: put the files in place
.agents/skills/integration-tanstack-start/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-tanstack-start -a cursor2Manually: put the files in place
.cursor/skills/integration-tanstack-start/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/skills skills/posthog/all/skills/integration-tanstack-start2Manually: put the files in place
.github/skills/integration-tanstack-start/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-tanstack-start -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/skills --path skills/posthog/all/skills/integration-tanstack-startManually: put the files in place
.devin/skills/integration-tanstack-start/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-tanstack-start -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about integration-tanstack-start
How do I install integration-tanstack-start in Claude Code?
Run npx skills add PostHog/skills --skill integration-tanstack-start -a claude-code, then open ~/.claude/skills/integration-tanstack-start/SKILL.md.
What does integration-tanstack-start do?
It guides PostHog integration for TanStack Start apps. The workflow covers browser and server tracking, feature flags, identity events, and error tracking.
Which platforms support integration-tanstack-start?
The skill is available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
Source text
SKILL.md · MIT
--- name: integration-tanstack-start description: PostHog integration for TanStack Start full-stack applications metadata: author: PostHog version: 1.9.4 --- # PostHog integration for TanStack Start This skill helps you add PostHog analytics to TanStack Start 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` - TanStack Start example project code - `references/tanstack-start.md` - Tanstack start - 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 - For feature flags, use useFeatureFlagEnabled() or useFeatureFlagPayload() hooks - they handle loading states and external sync automatically - Add analytics capture in event handlers where user actions occur, NOT in useEffect reacting to state changes - Do NOT use useEffect for data transformation - calculate derived values during render instead - Do NOT use useEffect to respond to user events - put that logic in the event handler itself - Do NOT use useEffect to chain state updates - calculate all related updates together in the event handler - Do NOT use useEffect to notify parent components - call the parent callback alongside setState in the event handler - To reset component state when a prop changes, pass the prop as the component's key instead of using useEffect - useEffect is ONLY for synchronizing with external systems (non-React widgets, browser APIs, network subscriptions) - Use PostHogProvider in the root route (__root.tsx) for client-side tracking - Use posthog-node for server-side event capture in API routes (src/routes/api/) - do NOT use posthog-js on the server - Create a singleton PostHog server client to avoid re-initialization on every request - Use TanStack Router's built-in navigation events for pageview tracking instead of useEffect - Use PostHogProvider in the root component defined in either the file-based convention (__root.tsx) or code-based convention (wherever createRootRoute() is called) so all child routes have access to the PostHog client ## 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.
© PostHog · MIT · PostHog/skills