281 件 ・ 関連度順
概要と使いどころ
Diagnose why a PostHog endpoint is slow or expensive and propose a concrete fix — bump the cache TTL, enable materialisation, restructure variables, or rewrite the query. Use when the user says "this endpoint is slow", "my endpoint times out", "we're hitting the cost cap on this one", or asks "should I materialise this?". Focuses on a single named endpoint, not a project-wide audit.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, "SDK health", "SDK doctor" (the former name), or when events or features seem off and it might be due to an old SDK.
日本語の概要は準備中です。原文の説明を表示しています。
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP. Use when the user asks about service traces, slow HTTP/database spans, error spans, trace IDs, or span attributes — not AI observability traces or product logs. Uses posthog:query-apm-spans, posthog:apm-trace-get, posthog:apm-services-list, posthog:apm-attributes-list, and posthog:apm-attribute-values-list.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters.
日本語の概要は準備中です。原文の説明を表示しています。
Export code, terminal output, diagrams, or UI components to PNG images using headless browser rendering or CLI tools.
日本語の概要は準備中です。原文の説明を表示しています。
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
日本語の概要は準備中です。原文の説明を表示しています。
Scan running terminals for dev server URLs (localhost ports), report them, and optionally open the app in Cursor's built-in browser.
日本語の概要は準備中です。原文の説明を表示しています。
Crawl all links in a file or project, test each for a valid HTTP response, report broken ones, and fix or remove them.
日本語の概要は準備中です。原文の説明を表示しています。
Use Cursor's browser to fill and submit every form in the app with valid and invalid data, verifying validation, error states, and success flows.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Guides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating observation volume and checking the org's monthly quota before creating, so a broad scanner doesn't exhaust the budget on its first scheduled sweep. TRIGGER when: user asks to create, set up, or configure a Replay Vision scanner, OR when you are about to call vision-scanners-create, OR when widening an existing scanner's query or sampling_rate via vision-scanners-update. DO NOT TRIGGER when: only reading scanners or observations, deleting a scanner, or running an existing scanner against a single session on demand (vision-scanners-scan-session).
日本語の概要は準備中です。原文の説明を表示しています。
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. TRIGGER when: user asks to create a new experiment or A/B test, OR when you are about to call experiment-create. DO NOT TRIGGER when: user is updating an existing experiment, managing lifecycle, or only browsing experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and optimize application performance, including bundle size, rendering, database queries, and Core Web Vitals.
日本語の概要は準備中です。原文の説明を表示しています。
Document technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Add Sentry error tracking, performance monitoring, and source maps to a web application.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.
日本語の概要は準備中です。原文の説明を表示しています。
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate Stripe payments into a web application, including checkout sessions, webhooks, and customer portal.
日本語の概要は準備中です。原文の説明を表示しています。
Add feature flags to an application for gradual rollouts, A/B testing, and kill switches using PostHog, LaunchDarkly, or a simple local implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Solve a hard problem by trying multiple approaches in parallel using isolated git worktrees. Each attempt runs in its own branch, and the best solution is selected. Use for complex refactors, tricky bugs, or architectural decisions where multiple strategies could work.
日本語の概要は準備中です。原文の説明を表示しています。
Audit the health of a PostHog project's data warehouse — find every broken or degraded pipeline item across sources, sync schemas, materialized views, batch exports, and transformations. Use when the user asks "what's broken in my warehouse?", "give me a health check", "audit my data pipeline", "why are some dashboards stale?", or wants a one-shot triage summary before deciding where to spend time. Produces a prioritized report of issues grouped by severity and type, with recommended next steps.
日本語の概要は準備中です。原文の説明を表示しています。