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 you catch yourself writing the same instruction a second time, or notice a recurring correction.
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 designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries.
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 layer — from…
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 when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on — 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…
Create Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow automations — 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.
Full Sentry SDK setup for TanStack Start React. Use when asked to \"add Sentry to TanStack Start\", \"install @sentry/tanstackstart-react\", or configure error monitoring,…
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 executing implementation plans with independent tasks in the current session — 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
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents.
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.
Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
Summarize authored commits over a user-specified time period into a concise update — from KunanonJ/ai-skills-hub
Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs.
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents.
Warp terminal integration for Claude Code — native notifications via OSC 777 escape sequences. Hooks into SessionStart, Stop, Notification, PermissionRequest, UserPromptSubmit,…
Cursor verimlilik ritüeli — Plan mode, Graphify, @ refs, browser MCP, vault handoff. "cursor verimlilik", "plan mode", "graphify", "devam cursor" taleplerinde kullan.
Upload markdown (including docmgr ticket docs) to a reMarkable device as PDF via a local uploader script, with a safe dry-run and optional mirroring of ticket structure.
Review code changes with the Bugbot subagent. Computes diffs, launches a bugbot subagent, and summarizes findings by severity.
Procédure complète pour créer ou modifier des Project Rules Cursor (.mdc) : modes d'activation, choix globs vs intelligent, contenu, anti-patterns, checklist.
Configure Cursor project rules using .cursor/rules/*.mdc files and legacy .cursorrules. Triggers on "cursorrules", ".cursorrules", "cursor rules", "cursor config", "cursor project…
Synchronizes Cursor Rules (.mdc files in .cursor/rules/) to CLAUDE.md by generating a Rules section with context-efficient descriptions and usage instructions.
Create Cursor IDE rules in .mdc format with proper frontmatter, glob patterns, and cross-references. Covers rule structure, file organization, triggering mechanisms, and quality…
Audits your Cursor Teams usage data and produces a right-sized Standard vs Premium seat assignment plan, saving typical teams 20–40% vs blanket Premium upgrades.
Cross-platform readiness setup for the `cursor` delegation skill. Detects the host OS (WSL / Linux / macOS; native Windows is unsupported → WSL), checks every runtime dependency…