[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"org-posthog":3,"repo-skills-v-0-3-0":182},{"org":4,"repos":57},{"slug":5,"name":6,"logoUrl":7,"githubOrg":5,"website":8,"skillCount":9,"repoCount":10,"topRepos":11,"topTags":27,"lastUpdatedAt":56},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png","https:\u002F\u002Fposthog.com",231,6,[12,15,18,21,24],{"name":13,"skillCount":14},"PostHog\u002Fskills",110,{"name":16,"skillCount":17},"PostHog\u002Fposthog",61,{"name":19,"skillCount":20},"PostHog\u002Fai-plugin",56,{"name":22,"skillCount":23},"PostHog\u002Fcode",2,{"name":25,"skillCount":26},"PostHog\u002Fcodex-share-plugin",1,[28,29,32,35,38,41,44,47,50,53],{"slug":5,"name":6},{"slug":30,"name":31},"analytics","Analytics",{"slug":33,"name":34},"observability","Observability",{"slug":36,"name":37},"debugging","Debugging",{"slug":39,"name":40},"frontend","Frontend",{"slug":42,"name":43},"backend","Backend",{"slug":45,"name":46},"feature-flags","Feature Flags",{"slug":48,"name":49},"monitoring","Monitoring",{"slug":51,"name":52},"product-management","Product Management",{"slug":54,"name":55},"llm","LLM","2026-07-31T06:23:36.250839",[58,73,104,123,146,166],{"name":59,"fullName":13,"repoUrl":60,"skillCount":14,"stars":20,"forks":61,"description":62,"topics":63,"topTags":64,"topTagCount":71,"lastUpdatedAt":72},"skills","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills",4,"PostHog skills (under construction)",[],[65,66,67,68,69,70],{"slug":5,"name":6},{"slug":30,"name":31},{"slug":33,"name":34},{"slug":39,"name":40},{"slug":42,"name":43},{"slug":45,"name":46},86,"2026-06-21T08:19:05.85849",{"name":5,"fullName":16,"repoUrl":74,"skillCount":17,"stars":75,"forks":76,"description":77,"topics":78,"topTags":92,"topTagCount":103,"lastUpdatedAt":56},"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog",35568,2977,"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.",[79,80,30,81,82,83,45,84,85,86,87,88,89,90,91],"ab-testing","ai-analytics","cdp","data-warehouse","experiments","javascript","product-analytics","python","react","session-replay","surveys","typescript","web-analytics",[93,94,95,96,97,100],{"slug":5,"name":6},{"slug":33,"name":34},{"slug":30,"name":31},{"slug":36,"name":37},{"slug":98,"name":99},"mcp","MCP",{"slug":101,"name":102},"code-review","Code Review",66,{"name":105,"fullName":19,"repoUrl":106,"skillCount":20,"stars":107,"forks":108,"description":109,"topics":110,"topTags":115,"topTagCount":103,"lastUpdatedAt":122},"ai-plugin","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin",59,11,"Official PostHog plugin for Claude Code, Cursor, Gemini, Codex and other AI coding tools",[111,112,113,114],"claude-code-plugin","codex-plugin","cursor-plugin","gemini-cli-extension",[116,117,118,119,120,121],{"slug":5,"name":6},{"slug":33,"name":34},{"slug":30,"name":31},{"slug":48,"name":49},{"slug":36,"name":37},{"slug":51,"name":52},"2026-07-28T06:05:59.674369",{"name":124,"fullName":22,"repoUrl":125,"skillCount":23,"stars":126,"forks":127,"description":128,"topics":129,"topTags":130,"topTagCount":144,"lastUpdatedAt":145},"code","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fcode",162,58,"The era of self-driving development is here",[],[131,132,135,138,140,141],{"slug":5,"name":6},{"slug":133,"name":134},"agents","Agents",{"slug":136,"name":137},"api-development","API Development",{"slug":84,"name":139},"JavaScript",{"slug":98,"name":99},{"slug":142,"name":143},"multi-agent","Multi-Agent",7,"2026-07-15T05:29:57.224313",{"name":147,"fullName":25,"repoUrl":148,"skillCount":26,"stars":149,"forks":149,"description":150,"topics":151,"topTags":152,"topTagCount":61,"lastUpdatedAt":165},"codex-share-plugin","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fcodex-share-plugin",0,null,[],[153,156,159,162],{"slug":154,"name":155},"codex","Codex",{"slug":157,"name":158},"documentation","Documentation",{"slug":160,"name":161},"github","GitHub",{"slug":163,"name":164},"markdown","Markdown","2026-07-24T06:09:09.203347",{"name":167,"fullName":168,"repoUrl":169,"skillCount":26,"stars":170,"forks":171,"description":172,"topics":173,"topTags":174,"topTagCount":61,"lastUpdatedAt":181},"posthog-foss","PostHog\u002Fposthog-foss","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog-foss",682,112,"PostHog FOSS is a read-only mirror of PostHog, with all proprietary code removed. NOTE: This repo is synced automatically from the main PostHog repo. Please raise any issues and PRs there.",[],[175,178,179,180],{"slug":176,"name":177},"data-engineering","Data Engineering",{"slug":36,"name":37},{"slug":33,"name":34},{"slug":5,"name":6},"2026-07-31T05:54:21.06761",{"items":183,"total":20},[184,200,214,229,242,254,270,288,303,319,330,341,357,373,384,399,409,420,433,444,457,468,481,493],{"slug":185,"name":185,"fn":186,"description":187,"org":188,"tags":189,"stars":107,"repoUrl":106,"updatedAt":199},"analyzing-experiment-session-replays","analyze session replays for PostHog experiments","Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[190,192,195,196],{"name":31,"slug":30,"type":191},"tag",{"name":193,"slug":194,"type":191},"Design","design",{"name":6,"slug":5,"type":191},{"name":197,"slug":198,"type":191},"User Research","user-research","2026-04-06T18:44:38.291781",{"slug":201,"name":201,"fn":202,"description":203,"org":204,"tags":205,"stars":107,"repoUrl":106,"updatedAt":213},"assessing-heatmaps","analyze page heatmaps and suggest improvements","Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click \u002F rageclick \u002F scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap\u002Fclick data, or to 'analyze\u002Fassess\u002Freview the heatmap' for a URL.\nDO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[206,207,208,209,210],{"name":31,"slug":30,"type":191},{"name":40,"slug":39,"type":191},{"name":6,"slug":5,"type":191},{"name":52,"slug":51,"type":191},{"name":211,"slug":212,"type":191},"UX Design","ux-design","2026-06-05T07:40:43.37798",{"slug":215,"name":215,"fn":216,"description":217,"org":218,"tags":219,"stars":107,"repoUrl":106,"updatedAt":228},"auditing-experiments-flags","audit PostHog experiments and feature flags","Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[220,223,224,225],{"name":221,"slug":222,"type":191},"Audit","audit",{"name":46,"slug":45,"type":191},{"name":6,"slug":5,"type":191},{"name":226,"slug":227,"type":191},"QA","qa","2026-04-06T18:44:30.657553",{"slug":230,"name":230,"fn":231,"description":232,"org":233,"tags":234,"stars":107,"repoUrl":106,"updatedAt":241},"authoring-scouts","author and edit PostHog Signals scouts","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), or steer a scout without editing it at all by leaving it a note. Covers the scout SKILL.md anatomy, the report contract, the dedupe + scratchpad-memory conventions, the scout-notes steering channel, 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\u002Fedit\u002Fcustomize a signals scout\", \"new scout for X\", \"tune my scout schedule\", \"make a scout that watches \u003Cevent>\", \"leave a note for \u002F give feedback to a scout\", \"tell the scouts about X\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[235,236,239,240],{"name":134,"slug":133,"type":191},{"name":237,"slug":238,"type":191},"Automation","automation",{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-07-28T05:33:45.509154",{"slug":243,"name":243,"fn":244,"description":245,"org":246,"tags":247,"stars":107,"repoUrl":106,"updatedAt":253},"building-a-dashboard","build and update PostHog dashboards","Build a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics\u002Fcharts together on one page, assemble a dashboard for a topic (product analytics, retention, revenue, activation, etc.), or add\u002Fremove\u002Freplace insights on a dashboard they already have. Covers deciding create vs update, reusing existing insights vs creating new ones, and using PostHog's vetted dashboard templates as reference for what a strong dashboard on a topic looks like.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[248,249,252],{"name":31,"slug":30,"type":191},{"name":250,"slug":251,"type":191},"Dashboards","dashboards",{"name":99,"slug":98,"type":191},"2026-07-21T06:07:38.060598",{"slug":255,"name":255,"fn":256,"description":257,"org":258,"tags":259,"stars":107,"repoUrl":106,"updatedAt":269},"checking-deploy-timing","correlate PostHog deployments with GitHub commits","Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask \"when was X deployed\", \"is my change live in the US\u002FEU yet\", \"has my PR shipped\", \"did the fix roll out to prod-us\", or otherwise want to know whether\u002Fwhen a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event\u002Fdata volume alone — that only shows when data changed, not when code shipped.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[260,263,266,267,268],{"name":261,"slug":262,"type":191},"Deployment","deployment",{"name":264,"slug":265,"type":191},"Git","git",{"name":161,"slug":160,"type":191},{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-06-28T07:46:59.53536",{"slug":271,"name":271,"fn":272,"description":273,"org":274,"tags":275,"stars":107,"repoUrl":106,"updatedAt":287},"choosing-trend-or-slope-view","visualize trends and growth over time","Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — \"how much did X change from A to B\", \"before vs after\", \"start vs end\", \"week over week\", \"compare this month to last\", \"change over time\" — or mentions a \"slope chart\" \u002F \"slopegraph\". Two readings of \"change\" need different charts: the whole trend (a line, every interval) versus just the two endpoints (a slope, start vs end). Ask which they want, then render it. Not for choosing a saved insight ChartDisplayType in the insight editor.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[276,277,280,283,284],{"name":31,"slug":30,"type":191},{"name":278,"slug":279,"type":191},"Charts","charts",{"name":281,"slug":282,"type":191},"Data Visualization","data-visualization",{"name":6,"slug":5,"type":191},{"name":285,"slug":286,"type":191},"Reporting","reporting","2026-06-18T08:18:57.960157",{"slug":289,"name":289,"fn":290,"description":291,"org":292,"tags":293,"stars":107,"repoUrl":106,"updatedAt":302},"cleaning-up-stale-feature-flags","clean up stale PostHog feature flags","Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[294,295,298,299],{"name":46,"slug":45,"type":191},{"name":296,"slug":297,"type":191},"Operations","operations",{"name":6,"slug":5,"type":191},{"name":300,"slug":301,"type":191},"Tech Debt","tech-debt","2026-04-06T18:44:31.93061",{"slug":304,"name":304,"fn":305,"description":306,"org":307,"tags":308,"stars":107,"repoUrl":106,"updatedAt":318},"configuring-experiment-analytics","configure PostHog experiment analytics","Configures the analytics side of a PostHog experiment — exposure criteria (default `$feature_flag_called` vs custom exposure events), primary and secondary metrics, the supported metric types (count, sum, ratio with `math` and `math_property`, retention with `retention_window_start` and `start_handling`), multivariate user handling (\"Exclude\" vs \"First seen variant\"), and how to read results once the experiment is live. Use when the user adds or edits a primary or secondary metric (e.g. \"add a secondary metric tracking 'downloaded_file' per user\"), sets up a ratio metric (e.g. \"revenue from purchase_completed \u002F pageviews\"), sets up a retention metric (e.g. \"$pageview → uploaded_file, 7-day window\"), configures custom exposure (e.g. \"only count users who hit \u002Fcheckout\"), changes multivariate handling, or asks \"who is in the analysis?\", \"how do I measure impact?\", \"is this winning?\", \"what's the confidence level?\", or \"should I ship?\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[309,312,313,316,317],{"name":310,"slug":311,"type":191},"A\u002FB Testing","a-b-testing",{"name":31,"slug":30,"type":191},{"name":314,"slug":315,"type":191},"Data Analysis","data-analysis",{"name":6,"slug":5,"type":191},{"name":285,"slug":286,"type":191},"2026-04-24T05:16:52.666341",{"slug":320,"name":320,"fn":321,"description":322,"org":323,"tags":324,"stars":107,"repoUrl":106,"updatedAt":329},"configuring-experiment-rollout","configure PostHog experiment rollouts","Configures the rollout shape of a PostHog experiment — the variant split (50\u002F50, 80\u002F20, A\u002FB\u002FC ratios), the overall rollout percentage that gates how many users enter the experiment, and the disambiguation when a percentage like \"roll out to 25%\" could mean either. Use when the user mentions a rollout percentage, variant split, or traffic distribution; gives a ratio like 60\u002F40, 70\u002F30, or 80\u002F20; asks \"who sees the test variant?\"; wants to increase, decrease, or change the rollout or split on a draft or running experiment; weighs equal vs uneven splits; or proposes a mid-experiment split change (often an anti-pattern that needs reset or end-and-restart).",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[325,326,327,328],{"name":310,"slug":311,"type":191},{"name":261,"slug":262,"type":191},{"name":6,"slug":5,"type":191},{"name":52,"slug":51,"type":191},"2026-07-24T05:36:54.187234",{"slug":331,"name":331,"fn":332,"description":333,"org":334,"tags":335,"stars":107,"repoUrl":106,"updatedAt":340},"creating-experiments","create experiments in PostHog","Guides agents through the 3-step experiment creation flow: defining the hypothesis, configuring rollout, and setting up analytics. Delegates rollout decisions to configuring-experiment-rollout and metric setup to configuring-experiment-analytics.\nTRIGGER when: user asks to create a new experiment or A\u002FB test, OR when you are about to call experiment-create.\nDO NOT TRIGGER when: user is updating an existing experiment, managing lifecycle, or only browsing experiments.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[336,337,338,339],{"name":310,"slug":311,"type":191},{"name":31,"slug":30,"type":191},{"name":6,"slug":5,"type":191},{"name":52,"slug":51,"type":191},"2026-07-18T05:11:43.415403",{"slug":342,"name":342,"fn":343,"description":344,"org":345,"tags":346,"stars":107,"repoUrl":106,"updatedAt":356},"debugging-signals-pipeline","debug PostHog signals pipeline","Debug the signals pipeline locally end-to-end. Covers emitting test signals from fixtures, monitoring Temporal workflows via the REST API, reading sandbox agent logs from object storage, inspecting Docker sandbox containers, and diagnosing common failures (stale ClickHouse embeddings, agentsh network denials, inactivity timeouts). Use when a signal isn't reaching the inbox, a signal-report-summary workflow fails, or a sandbox task run times out.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[347,350,351,354,355],{"name":348,"slug":349,"type":191},"Data Pipeline","data-pipeline",{"name":37,"slug":36,"type":191},{"name":352,"slug":353,"type":191},"Engineering","engineering",{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-06-05T07:40:53.882356",{"slug":358,"name":358,"fn":359,"description":360,"org":361,"tags":362,"stars":107,"repoUrl":106,"updatedAt":372},"diagnosing-failed-warehouse-syncs","diagnose failed data warehouse syncs","Diagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks \"why isn't my Stripe\u002FPostgres\u002FHubspot sync working?\", \"this table has been stuck for hours\", \"the data in the warehouse looks wrong\", or wants to troubleshoot a specific source or schema. Covers source-level vs schema-level failures, stuck Running states, credential and schema-drift errors, incremental-field misconfig, CDC prerequisite failures, and the cancel \u002F reload \u002F resync \u002F delete-data recovery actions.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[363,364,366,367,370,371],{"name":177,"slug":176,"type":191},{"name":365,"slug":82,"type":191},"Data Warehouse",{"name":37,"slug":36,"type":191},{"name":368,"slug":369,"type":191},"ETL","etl",{"name":49,"slug":48,"type":191},{"name":6,"slug":5,"type":191},"2026-06-18T08:19:16.316755",{"slug":374,"name":374,"fn":375,"description":376,"org":377,"tags":378,"stars":107,"repoUrl":106,"updatedAt":383},"exploring-llm-clusters","analyze LLM usage patterns and clusters","Investigate AI observability clusters — understand usage patterns in AI\u002FLLM traffic, compare cluster behavior, compute cost\u002Flatency metrics, and drill into individual traces within clusters.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[379,380,381,382],{"name":31,"slug":30,"type":191},{"name":55,"slug":54,"type":191},{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-04-06T18:44:29.40583",{"slug":385,"name":385,"fn":386,"description":387,"org":388,"tags":389,"stars":107,"repoUrl":106,"updatedAt":398},"exploring-llm-traces","debug and inspect LLM agent traces","ABSOLUTE MUST to debug and inspect LLM\u002FAI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. \u002Fai-observability\u002Ftraces\u002F\u003Cid> or \u002Fai-observability\u002Fsessions\u002F\u003Cid>), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context\u002Ffiles were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL\u002FHogQL against `events.properties.$ai_input` \u002F `$ai_output_choices` returns empty — message content lives only on the dedicated `posthog.ai_events` table.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[390,391,392,393,394,395],{"name":134,"slug":133,"type":191},{"name":37,"slug":36,"type":191},{"name":55,"slug":54,"type":191},{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},{"name":396,"slug":397,"type":191},"Tracing","tracing","2026-04-06T18:44:40.791466",{"slug":400,"name":400,"fn":401,"description":402,"org":403,"tags":404,"stars":107,"repoUrl":106,"updatedAt":408},"exploring-scouts","explore PostHog Signals scout findings","How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, and assessing a scout's health and performance over time (cadence, success rate, report rate, signal-to-noise). Read-only and exploratory — to write or tune a scout, use `authoring-scouts` instead. Trigger on \"what are my scouts doing\", \"how is my \u003Cx> scout performing\", \"show me recent scout runs\", \"why did this scout find\u002Freport nothing\", \"what has the fleet learned\", \"explore scout run \u003Cid>\", \"is my scout working\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[405,406,407],{"name":31,"slug":30,"type":191},{"name":49,"slug":48,"type":191},{"name":6,"slug":5,"type":191},"2026-07-28T05:33:43.543894",{"slug":410,"name":410,"fn":411,"description":412,"org":413,"tags":414,"stars":107,"repoUrl":106,"updatedAt":419},"finding-experiments","resolve PostHog experiment references","Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment (\"split test demo\", \"the File engagement boost experiment\", \"onboarding retention test\", \"landing page hero experiment\", \"pricing experiment\"), describes it loosely (\"the signup experiment\", \"my pricing test\", \"the one with the new checkout\"), uses a relative reference (\"latest\", \"most recent\", \"the one I created yesterday\"), filters by status (running, draft, paused, exposure frozen, stopped, archived), or otherwise refers to an experiment by anything other than its concrete ID.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[415,416,417,418],{"name":310,"slug":311,"type":191},{"name":31,"slug":30,"type":191},{"name":6,"slug":5,"type":191},{"name":52,"slug":51,"type":191},"2026-07-24T05:36:58.200605",{"slug":421,"name":421,"fn":422,"description":423,"org":424,"tags":425,"stars":107,"repoUrl":106,"updatedAt":432},"instrument-error-tracking","instrument applications with PostHog error tracking","Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[426,427,430,431],{"name":37,"slug":36,"type":191},{"name":428,"slug":429,"type":191},"Integrations","integrations",{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-07-28T05:33:42.496857",{"slug":434,"name":434,"fn":435,"description":436,"org":437,"tags":438,"stars":107,"repoUrl":106,"updatedAt":443},"instrument-feature-flags","instrument applications with PostHog feature flags","Add PostHog feature flags to gate new functionality. Use after implementing features or reviewing PRs to ensure safe rollouts with feature flag controls. Also handles initial PostHog SDK setup if not yet installed.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[439,440,441,442],{"name":261,"slug":262,"type":191},{"name":46,"slug":45,"type":191},{"name":428,"slug":429,"type":191},{"name":6,"slug":5,"type":191},"2026-07-28T05:33:40.494239",{"slug":445,"name":445,"fn":446,"description":447,"org":448,"tags":449,"stars":107,"repoUrl":106,"updatedAt":456},"instrument-integration","integrate PostHog SDK into applications","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.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[450,451,452,453],{"name":31,"slug":30,"type":191},{"name":428,"slug":429,"type":191},{"name":6,"slug":5,"type":191},{"name":454,"slug":455,"type":191},"SDK","sdk","2026-07-28T05:33:38.516267",{"slug":458,"name":458,"fn":459,"description":460,"org":461,"tags":462,"stars":107,"repoUrl":106,"updatedAt":467},"instrument-llm-analytics","instrument applications with PostHog LLM analytics","Add PostHog LLM analytics to trace AI model usage. Use after implementing LLM features or reviewing PRs to ensure all generations are captured with token counts, latency, and costs. Also handles initial PostHog SDK setup if not yet installed.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[463,464,465,466],{"name":31,"slug":30,"type":191},{"name":55,"slug":54,"type":191},{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-07-28T05:33:41.519804",{"slug":469,"name":469,"fn":470,"description":471,"org":472,"tags":473,"stars":107,"repoUrl":106,"updatedAt":480},"instrument-logs","instrument applications with PostHog log capture","Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[474,475,478,479],{"name":428,"slug":429,"type":191},{"name":476,"slug":477,"type":191},"Logs","logs",{"name":34,"slug":33,"type":191},{"name":6,"slug":5,"type":191},"2026-07-28T05:33:39.517469",{"slug":482,"name":482,"fn":483,"description":484,"org":485,"tags":486,"stars":107,"repoUrl":106,"updatedAt":492},"instrument-product-analytics","instrument PostHog product analytics events","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.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[487,488,489,490,491],{"name":31,"slug":30,"type":191},{"name":40,"slug":39,"type":191},{"name":6,"slug":5,"type":191},{"name":52,"slug":51,"type":191},{"name":454,"slug":455,"type":191},"2026-07-28T05:33:44.509005",{"slug":494,"name":494,"fn":495,"description":496,"org":497,"tags":498,"stars":107,"repoUrl":106,"updatedAt":503},"managing-experiment-lifecycle","manage PostHog experiment lifecycles","Guides experiment state transitions: launching, pausing, resuming, freezing\u002Funfreezing exposure, ending, shipping variants, archiving, resetting, duplicating, and copying to another project. Covers preconditions, implications for variant assignment and analysis, and the decision framework for when to use each action.\nTRIGGER when: user asks to launch, pause, resume, end, ship, archive, reset, duplicate, or copy an experiment to another project, or to freeze\u002Funfreeze exposure (stop enrolling new users while metrics keep flowing, or reopen enrollment).\nDO NOT TRIGGER when: user is creating an experiment (use creating-experiments), configuring rollout (use configuring-experiment-rollout), or setting up metrics (use configuring-experiment-analytics).",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[499,500,501,502],{"name":310,"slug":311,"type":191},{"name":296,"slug":297,"type":191},{"name":6,"slug":5,"type":191},{"name":52,"slug":51,"type":191},"2026-07-24T05:36:55.200817"]