Focused Signals scout for PostHog projects using error tracking. Watches `$exception` bursts, stuck loops, multi-fingerprint clusters, status regressions, and stack-trace…
> General Signals scout for PostHog projects. Cross-product explorer that scans a team's project and emits findings into the Signals inbox.
Focused Signals scout for PostHog projects using logs. Watches for volume bursts, severity-distribution shifts, service silence, fresh message patterns, and trace-correlated…
Focused Signals scout for finding observability gaps in PostHog itself — significant event volumes the team isn't tracking, custom events with no insight or dashboard coverage,…
Focused Signals scout for PostHog projects using revenue analytics. Watches the derived revenue product for upstream failures (Stripe sync stalls, capture regressions), config…
Focused Signals scout for PostHog projects running surveys. Watches active surveys for score regressions (NPS / CSAT / rating drops), response-volume drops, abandonment spikes,…
Discover and use shared team skills stored in PostHog. Use when the user asks to list, browse, load, or manage \"shared skills\", \"team skills\", or references the \"skills…
Create PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks \"stop capturing this error\", \"drop browser extension…
Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks \"what's broken?\", \"what new errors do we have?\", \"show me top errors today\",…
Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions \"visual review\", \"VR\", \"snapshot diff\",…
Change the sync configuration of an existing data warehouse schema — switch sync_type, pick a different incremental_field, set primary_key_columns, choose cdc_table_mode, or…
Postman concepts and MCP tool guidance. Loaded when working with Postman MCP tools to make better decisions about tool selection and workarounds.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up.
Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\".
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types a — from…
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payload — from…
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irrevers — from…
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-repor — from…
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language.
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state…
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.
Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN- — from…
Full Sentry SDK setup for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS). Use when asked to \"add Sentry to iOS\", \"add Sentry to Swift\", \"install sentry-cocoa\ — from…
Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry.
Full Sentry SDK setup for Flutter and Dart. Use when asked to \"add Sentry to Flutter\", \"install sentry_flutter\", \"setup Sentry in Dart\", or configure error monitoring,…
Full Sentry SDK setup for Go. Use when asked to \"add Sentry to Go\", \"install sentry-go\", \"setup Sentry in Go\", or configure error monitoring, tracing, logging, metrics, or…
Configure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation.
Fix production issues and review code with Sentry context. Use when asked to fix Sentry errors, debug issues, triage exceptions, review PR comments from Sentry, or resolv — from…
Use when the user wants to find businesses, software, service providers, or partners for a specific industry, workflow, pain point, capability, or job to be done.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies — from KunanonJ/ai-skills-hub
Use when you have a written implementation plan to execute in a separate session with review checkpoints — from KunanonJ/ai-skills-hub
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory — from…
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions — from…
Use when you have a spec or requirements for a multi-step task, before touching code — from KunanonJ/ai-skills-hub
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services.
Find failing PR checks, inspect logs or external check links, and apply focused fixes
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks. — from KunanonJ/ai-skills-hub
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.
Generate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, a — from…
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR. — from KunanonJ/ai-skills-hub
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth.
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Summarize authored commits over a user-specified time period into a concise update — from KunanonJ/ai-skills-hub
Warp terminal integration for Claude Code — native notifications via OSC 777 escape sequences. Hooks into SessionStart, Stop, Notification, PermissionRequest, UserPromptSubmit,…
Deinstalliert einen Community-Skill, der über den Kanzlei-Builder-Hub installiert wurde. Bestätigt vor dem Löschen von Dateien, verweigert jede Aktion auf Erstanbieter-Pl — from…
Plugin-first doctrine and runtime engine for developer tools, plugin shells, agentic systems, memory and continuity, shell and terminal workflows, build and deploy posture,…
Use when working with docusaurus-plugin-glossary to configure, manage glossary terms, troubleshoot issues, and explain features
Build and bundle native Node.js addons for Electron with proper ABI compatibility, cross-compilation support, and rebuild automation
Extension API for domain bundle discovery, module detection, and canonical command generation
評估日文詞彙卡片的語用延伸需求。 分析六個面向：敬語、語氣、語域、褒貶義、暗喻、同義詞對比。 使用時機： - 當想了解某個詞彙需要哪些延伸卡片 - 當需要評估詞彙的語用複雜度 - 當探索詞彙的社會語言學特徵 - 當人工判斷是否需要建立延伸卡片 關鍵字：延伸需求、敬語延伸、同義詞對比、語域分析、延伸卡片、語用分析
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup