exploring-ai-failures
>
exploring-llm-costs
>
exploring-llm-evaluations
>
exploring-llm-traces
>
feature-usage-feed
>
downloading-batch-export-files
>
understanding-billing-usage
>
building-canvases
>
building-html-canvases
>
building-react-quill-canvases
>
composing-grid-canvases
>
querying-canvas-data
>
validating-and-publishing-canvases
>
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the @posthog/quill pnpm override.
adding-warehouse-person-properties
>
setting-up-warehouse-properties
>
building-a-dashboard
>
setting-up-data-catalog
>
modeling-activation-metrics
>
modeling-conversion-metrics
>
modeling-dimension-tables
>
modeling-product-usage-metrics
>
modeling-revenue-metrics
>
modeling-warehouse-foundations
>
authoring-data-quality-checks
>
auditing-warehouse-view-health
>
upgrade-claude-adapter
>-
dynamic-workflows
>-
mcp-servers
Install, configure, authenticate, and troubleshoot MCP (Model Context Protocol) servers for this agent. Use when the user asks to add/install/remove an MCP server, connect a tool like Linear/Sentry/Supabase/GitHub via MCP, set up mcp.json, or when MCP tools are failing or need OAuth login.
auditing-endpoints
>
consuming-endpoints-from-client-code
>
copying-endpoints-across-projects
>
creating-an-endpoint
>
diagnosing-endpoint-performance
>
exploring-endpoint-execution-logs
>
managing-endpoint-versions
>
diagnosing-ci-and-merge-bottlenecks
>
investigating-ci-failures
>
turning-engineering-analytics-into-insights
>
authoring-error-tracking-alerts
>
diagnosing-stacktrace-symbolication
>
grouping-noisy-errors
>
investigating-error-issue
>
suppressing-noisy-errors
>
triaging-error-issues
>
finding-experiments
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.
debugging-experiments
>-
diagnosing-experiment-results
Diagnoses bias, anomalies, and strange results on a PostHog experiment. Covers 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, surprises after mid-run edits, and qualitative follow-up via a variant-split survey.\nTRIGGER 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 or A/A significance, finds PostHog numbers disagreeing with their SQL, reports surprises after mid-run edits, or wants qualitative feedback or a survey for an experiment.\nDO NOT TRIGGER when: creating an 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).
finding-deleted-feature-flags
Find feature flags that were soft-deleted in the active project within a recent time window. Use when the user asks "what flags were deleted in the last N days", "show me recently deleted feature flags", "who deleted flag X", "audit recent flag deletions", or anything similar. Handles the non-obvious gotcha that system.feature_flags exposes the deleted boolean but does not expose a deletion timestamp — the actual deleted-at time lives in the per-flag activity log and must be cross-referenced.
diagnosing-sdk-health
>
Page 629 of 1646 · 82296 results