メニュー
Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | instrument-integration |
| description | Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework. |
| metadata | {"author":"PostHog"} |
Use this skill to add the PostHog SDK to an application. Use it when setting up PostHog for the first time, or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration. Supports any framework or language.
Supported frameworks and languages: Next.js, React, React Router, Vue, Nuxt, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, PHP, Ruby on Rails, Go, Elixir, Android, iOS, Swift, Flutter, React Native, Expo, Node.js, and vanilla JavaScript.
Follow these steps IN ORDER:
Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb, go.sum, pubspec.lock, Podfile.lock, Package.resolved, mix.lock) to determine the package manager.
STEP 2: Research integration. 2.1. Find the reference file below that matches the detected framework — it is the source of truth for SDK initialization, provider setup, and configuration patterns. Read it now. 2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com/docs as the primary search source.
STEP 3: Install the PostHog SDK.
STEP 4: Initialize PostHog.
STEP 5: Identify users.
identify() calls on the client side during login and signup events.X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to the server-side code.STEP 6: Set up environment variables.
.env, .env.local, or framework-specific env files). If valid values already exist, skip this step.projects-get tool to retrieve the project's api_token. If multiple projects are returned, ask the user which project to use. If the MCP server is not connected or not authenticated, ask the user for their PostHog project API key instead.https://us.i.posthog.com for US Cloud or https://eu.i.posthog.com for EU Cloud..env.local for Next.js, .env for others) using the framework's naming convention.STEP 7: Verify and clean up.
references/EXAMPLE-next-app-router.md - next-app-router example project codereferences/EXAMPLE-next-pages-router.md - next-pages-router example project codereferences/EXAMPLE-react-react-router-6.md - react-react-router-6 example project codereferences/EXAMPLE-react-react-router-7-framework.md - react-react-router-7-framework example project codereferences/EXAMPLE-react-react-router-7-data.md - react-react-router-7-data example project codereferences/EXAMPLE-react-react-router-7-declarative.md - react-react-router-7-declarative example project codereferences/EXAMPLE-react-vite.md - react-vite example project codereferences/EXAMPLE-nuxt-3-6.md - nuxt-3-6 example project codereferences/EXAMPLE-nuxt-4.md - nuxt-4 example project codereferences/EXAMPLE-vue-3.md - vue-3 example project codereferences/EXAMPLE-react-tanstack-router-file-based.md - react-tanstack-router-file-based example project codereferences/EXAMPLE-react-tanstack-router-code-based.md - react-tanstack-router-code-based example project codereferences/EXAMPLE-tanstack-start.md - tanstack-start example project codereferences/EXAMPLE-sveltekit.md - sveltekit example project codereferences/EXAMPLE-astro-static.md - astro-static example project codereferences/EXAMPLE-astro-view-transitions.md - astro-view-transitions example project codereferences/EXAMPLE-astro-ssr.md - astro-ssr example project codereferences/EXAMPLE-astro-hybrid.md - astro-hybrid example project codereferences/EXAMPLE-angular.md - angular example project codereferences/EXAMPLE-javascript-node.md - javascript-node example project codereferences/EXAMPLE-javascript-web.md - javascript-web example project codereferences/EXAMPLE-django.md - django example project codereferences/EXAMPLE-flask.md - flask example project codereferences/EXAMPLE-fastapi.md - fastapi example project codereferences/EXAMPLE-python.md - python example project codereferences/EXAMPLE-laravel.md - laravel example project codereferences/EXAMPLE-php.md - php example project codereferences/EXAMPLE-ruby-on-rails.md - ruby-on-rails example project codereferences/EXAMPLE-ruby.md - ruby example project codereferences/EXAMPLE-android.md - android example project codereferences/EXAMPLE-swift.md - swift example project codereferences/EXAMPLE-react-native.md - react-native example project codereferences/EXAMPLE-expo.md - expo example project codereferences/next-js.md - Next.js - docsreferences/react.md - React - docsreferences/react-router-v6.md - React router v6 - docsreferences/react-router-v7-framework-mode.md - React router v7 framework mode (remix v3) - docsreferences/react-router-v7-data-mode.md - React router v7 data mode - docsreferences/react-router-v7-declarative-mode.md - React router v7 declarative mode - docsreferences/nuxt-js-3-6.md - Nuxt.js (v3.0 to v3.6) - docsreferences/nuxt-js.md - Nuxt.js - docsreferences/vue-js.md - Vue.js - docsreferences/tanstack-start.md - Tanstack start - docsreferences/svelte.md - Svelte - docsreferences/astro.md - Astro - docsreferences/angular.md - Angular - docsreferences/js.md - JavaScript web - docsreferences/posthog-js.md - PostHog JavaScript web SDKreferences/node.md - Node.js - docsreferences/posthog-node.md - PostHog Node.js SDKreferences/django.md - Django - docsreferences/flask.md - Flask - docsreferences/python.md - Python - docsreferences/posthog-python.md - PostHog python SDKreferences/dotnet.md - .net - docsreferences/elixir.md - Elixir - docsreferences/go.md - Go - docsreferences/laravel.md - Laravel - docsreferences/php.md - Php - docsreferences/ruby-on-rails.md - Ruby on rails - docsreferences/ruby.md - Ruby - docsreferences/android.md - Android - docsreferences/ios.md - Ios - docsreferences/usage.md - Ios SDK usage - docsreferences/configuration.md - Ios SDK configuration - docsreferences/flutter.md - Flutter - docsreferences/react-native.md - React native - docsreferences/identify-users.md - Identify users - docsEach framework reference contains SDK-specific installation, initialization, and usage patterns. Find the one matching the user's stack.
How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers). Covers the scout SKILL.md anatomy, the report contract, the dedupe + scratchpad-memory conventions, the per-team skills-store path vs the canonical in-repo path, and the write-and-inspect test loop (with dry-run as an optional safety net). Trigger on "write/edit/customize a signals scout", "new scout for X", "tune my scout schedule", "make a scout that watches <event>".
Diagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty / 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A/A, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, and surprises after mid-run edits. Symptom-driven dispatch to the right diagnostic. TRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange / wrong / off, sees significance flipping, notices PostHog numbers disagreeing with their SQL, sees an A/A test showing significance, or reports surprises after mid-run edits. DO NOT TRIGGER when: creating a new experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).
Add PostHog product analytics events to track user behavior. Use after implementing new features or reviewing PRs to ensure meaningful user actions are captured. Also handles initial PostHog SDK setup if not yet installed.
Required reading before writing any HogQL/SQL or calling execute-sql against PostHog. Use whenever the user wants to search, find, or do complex aggregations PostHog entities (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse, persons, etc.) and query analytics data (trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, LLM traces). Covers HogQL syntax differences from ClickHouse SQL, system table schemas (system.*), available functions, query examples, and the schema-discovery workflow.
Signals scout for PostHog AI observability. Watches LLM traces for cost, latency, error, volume, and eval-performance regressions, sliced by the dimensions it discovers over time, and files each validated regression as a report in the inbox.
Focused Signals scout for PostHog projects capturing Core Web Vitals (`$web_vitals`). Watches each page's p75 LCP / INP / CLS / FCP against the absolute Google thresholds (good / needs-improvement / poor) and against its own history: pages standing in the poor band, pages crossing a band boundary after a deploy, and sharp in-band regressions. Reads the historical trajectory — not just the moment a value changes — so a page that is steadily slow surfaces even when nothing moved today. Every finding carries a metric-specific cause hypothesis and a concrete remediation. Emits only above the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet.