mcpbeat

Integration React Tanstack Router File Based

posthog/integration-react-tanstack-router-file-based

>- PostHog integration for React applications using TanStack Router with file-based routing

11k tokens
context cost
the whole folder, loaded on every use
8
files
instructions only
0
copies elsewhere
how many repositories repackaged it
57
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/PostHog/skills --skill integration-react-tanstack-router-file-based

What comes with it

39 249 bytes besides the instruction
references/EXAMPLE.md
references/basic-integration-1.0-begin.md
references/basic-integration-1.1-edit.md
references/basic-integration-1.2-revise.md
references/basic-integration-1.3-conclude.md
references/identify-users.md
references/tanstack-start.md

The instruction itself

7 sections, as written by the author

PostHog integration for React with TanStack Router (file-based)

This skill helps you add PostHog analytics to React with TanStack Router (file-based) applications.

Workflow

Follow these steps in order to complete the integration:

  • basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here
  • basic-integration-1.1-edit.md - PostHog Setup - Edit
  • basic-integration-1.2-revise.md - PostHog Setup - Revise
  • basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

  • references/EXAMPLE.md - React with TanStack Router (file-based) 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 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.

How to use it

Copy the folder

Take posthog/integration-react-tanstack-router-file-based from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.