posthog/ai-plugin

instrument-integration

Add PostHog SDK integration to your application.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/posthog/ai-plugin --skill instrument-integration

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Add PostHog SDK integration

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.

Instructions

Follow these steps IN ORDER:

STEP 1: Analyze the codebase and detect the platform. - Look for dependency files (package.json, pubspec.yaml, Podfile, Package.swift, requirements.txt, Gemfile, composer.json, go.mod, mix.exs, etc.) to determine the framework and language. - 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.

  • Check for existing PostHog setup. If PostHog is already installed and initialized, do not modify its code. Inform the user and skip to verification.

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.

  • Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.

STEP 4: Initialize PostHog.

  • Follow the framework reference for where and how to initialize. This varies significantly by framework (e.g., instrumentation-client.ts for Next.js 15.3+, AppConfig.ready() for Django, create_app() for Flask).
  • Set up the PostHog provider/wrapper component if the framework requires one.

STEP 5: Identify users.

  • Add PostHog identify() calls on the client side during login and signup events.
  • If both frontend and backend exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to the server-side code.

STEP 6: Set up environment variables.

  • Check if the project already has PostHog environment variables configured (e.g. in .env, .env.local, or framework-specific env files). If valid values already exist, skip this step.
  • If the PostHog project token is missing, use the PostHog MCP server's 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 token instead.
  • For the PostHog host URL: check the projects-get MCP response for a region field — US maps to https://us.i.posthog.com, EU maps to https://eu.i.posthog.com. If the region is not available from the MCP response or from existing project configuration, ask the user: "Are you on PostHog US Cloud or EU Cloud?" Do not assume US Cloud.
  • Write these values to the appropriate env file (e.g. .env.local for Next.js, .env for others) using the framework's naming convention.
  • Reference these environment variables in code instead of hardcoding them.

STEP 7: Verify and clean up.

  • Check the project for errors. Look for type checking or build scripts in package.json.
  • Ensure any components created were actually used.
  • Run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase.

Reference files

  • references/EXAMPLE-next-app-router.md - next-app-router example project code
  • references/EXAMPLE-next-pages-router.md - next-pages-router example project code
  • references/EXAMPLE-react-react-router-6.md - react-react-router-6 example project code
  • references/EXAMPLE-react-react-router-7-framework.md - react-react-router-7-framework example project code
  • references/EXAMPLE-react-react-router-7-data.md - react-react-router-7-data example project code
  • references/EXAMPLE-react-react-router-7-declarative.md - react-react-router-7-declarative example project code
  • references/EXAMPLE-react-vite.md - react-vite example project code
  • references/EXAMPLE-nuxt-3-6.md - nuxt-3-6 example project code
  • references/EXAMPLE-nuxt-4.md - nuxt-4 example project code
  • references/EXAMPLE-vue-3.md - vue-3 example project code
  • references/EXAMPLE-react-tanstack-router-file-based.md - react-tanstack-router-file-based example project code
  • references/EXAMPLE-react-tanstack-router-code-based.md - react-tanstack-router-code-based example project code
  • references/EXAMPLE-tanstack-start.md - tanstack-start example project code
  • references/EXAMPLE-sveltekit.md - sveltekit example project code
  • references/EXAMPLE-astro-static.md - astro-static example project code
  • references/EXAMPLE-astro-view-transitions.md - astro-view-transitions example project code
  • references/EXAMPLE-astro-ssr.md - astro-ssr example project code
  • references/EXAMPLE-astro-hybrid.md - astro-hybrid example project code
  • references/EXAMPLE-angular.md - angular example project code
  • references/EXAMPLE-javascript-node.md - javascript-node example project code
  • references/EXAMPLE-javascript-web.md - javascript-web example project code
  • references/EXAMPLE-django.md - django example project code
  • references/EXAMPLE-flask.md - flask example project code
  • references/EXAMPLE-fastapi.md - fastapi example project code
  • references/EXAMPLE-python.md - python example project code
  • references/EXAMPLE-laravel.md - laravel example project code
  • references/EXAMPLE-php.md - php example project code
  • references/EXAMPLE-ruby-on-rails.md - ruby-on-rails example project code
  • references/EXAMPLE-ruby.md - ruby example project code
  • references/EXAMPLE-android.md - android example project code
  • references/EXAMPLE-swift.md - swift example project code
  • references/EXAMPLE-react-native.md - react-native example project code
  • references/EXAMPLE-expo.md - expo example project code
  • references/next-js.md - Next.js
  • references/react.md - React
  • references/react-router-v6.md - React router v6
  • references/react-router-v7-framework-mode.md - React router v7 framework mode (remix v3)
  • references/react-router-v7-data-mode.md - React router v7 data mode
  • references/react-router-v7-declarative-mode.md - React router v7 declarative mode
  • references/nuxt-js-3-6.md - Nuxt.js (v3.0 to v3.6)
  • references/nuxt-js.md - Nuxt.js
  • references/vue-js.md - Vue.js
  • references/tanstack-start.md - Tanstack start
  • references/svelte.md - Svelte
  • references/astro.md - Astro
  • references/angular.md - Angular
  • references/js.md - JavaScript web
  • references/posthog-js.md - PostHog JavaScript web SDK
  • references/node.md - Node.js
  • references/posthog-node.md - PostHog Node.js SDK
  • references/django.md - Django
  • references/flask.md - Flask
  • references/python.md - Python
  • references/posthog-python.md - PostHog python SDK
  • references/dotnet.md - .net
  • references/elixir.md - Elixir
  • references/go.md - Go
  • references/laravel.md - Laravel
  • references/php.md - Php
  • references/ruby-on-rails.md - Ruby on rails
  • references/ruby.md - Ruby
  • references/android.md - Android
  • references/ios.md - Ios
  • references/usage.md - Ios SDK usage
  • references/configuration.md - Ios SDK configuration
  • references/flutter.md - Flutter
  • references/react-native.md - React native
  • references/identify-users.md - Identify users
  • references/COMMANDMENTS.md - Framework-specific rules the integration must follow

Each framework reference contains SDK-specific installation, initialization, and usage patterns. Find the one matching the user's stack.

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.
  • Analytics contract: Treat event names, property names, and feature flag keys as part of an analytics contract. Reuse existing names and patterns found in the project. When introducing new ones, make them clear, descriptive, and consistent with existing conventions.
do mesmo repositório

Mais Skills

Todos os Skills
posthog
Oficial

exploring-llm-costs

Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.

Instalações / 1h
2
GitHub Stars
98
Atualizado
6 de nov.
posthog
Oficial

exploring-llm-traces

Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/ or /ai-observability/sessions/ ), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against events.properties.$aiinput / $aioutputchoices returns empty — message

Instalações / 1h
2
GitHub Stars
98
Atualizado
6 de nov.
posthog
Oficial

investigating-error-issue

Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (/error-tracking/ ) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.

Instalações / 1h
2
GitHub Stars
98
Atualizado
6 de nov.
posthog
Oficial

investigating-replay

Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors occurred, and whether there are related error tracking issues. Replaces the manual chain of session-recording-get, persons-retrieve, execute-sql, and query-error-tracking-issues-list.

Instalações / 1h
2
GitHub Stars
98
Atualizado
6 de nov.