Question-led planning gate for implementation work. Use when the user wants a project plan, roadmap, feature plan, technical design, implementation plan, migration plan, product workflow, architecture change, or any substantial build before code changes begin. Forces the agent to repeatedly question assumptions…
Turn vague client briefs, discovery notes, pasted requirements, screenshots, transcripts, or early project ideas into a saved client-facing requirements and implementation plan. Use when the user wants client input formalized into numbered testable requirements, phased delivery, open client questions, technical…
Review an existing codebase for redundant, legacy, dead, superseded, or attack-surface-increasing code paths and guide progressive removal with behavior mapping, test coverage, security review, and validation. Use when asked to remove old providers or integrations, clean redundant code paths, reduce tech debt, reduce…
Conservative Docker-native disk cleanup for developer machines and local PR-gate hosts. Use when asked to clean Docker disk usage, reclaim Docker image/build-cache/volume space, run daily Docker cleanup, diagnose Docker disk pressure, or safely prune containers, networks, images, BuildKit cache, and unused volumes…
Vercel-first, provider-aware review and remediation workflow for web app error logging. Use when a user asks to audit, add, fix, harden, or verify logging, error capture, runtime observability, error boundaries, structured logs, correlation IDs, alerting evidence, or production debuggability in an existing web app.
Tool-agnostic feature design preflight that traces a requirement through production constraints, dependencies, user and system flows, edge cases, security, operations, and tests before implementation, and emits a READY, CONDITIONAL, or BLOCKED implementation readiness note. Use before implementing nontrivial features…
Ensure frontend design work follows established repo patterns, minimizes clicks, fills real viewports, stays responsive, avoids text overflow, reduces portal UI clutter, covers content-rich surfaces such as blogs/resources, and is verified with Playwright or equivalent visual screenshots. Use when building, changing…
Orchestrate a full non-mutating app or repo review across architecture, live flows, frontend quality, testing and coverage, security, observability and error instrumentation, analytics, dependencies, deployment, validation readiness, and redundant code paths. The default outcome is an evidence-backed, severity-ordered…
Keep this macOS developer laptop current without unsafe repo mutation. Use when asked to update Homebrew, PowerShell, Vercel CLI, Node, gh, dotnet, global developer tooling, package currency, stale CLIs, or to keep the laptop up to date while safely auditing local repo dependencies.
Add privacy-safe Vercel Web Analytics to Next.js apps, including pageview setup, typed client and server custom events, strict no-PII payload rules, App Router or Pages Router placement, and local verification. Use when a user asks to add, implement, instrument, review, or fix Vercel analytics, Vercel Web Analytics…
Fully automatic GitHub PR review and production deployment gate for trusted repos. Use when configuring or operating a scheduled PR gate that checks open PRs, downloads them locally, runs complete containerized validation with mocked external services, comments or rejects failing PRs, promotes passing PRs through…
Exhaustively document an existing repository's technical architecture and implementation details. Use when asked to work through a whole repo and create, update, reconcile, or refresh technical docs covering API endpoints, UI routes and choices, frameworks, libraries and rationale, data models, integrations, jobs…
Evidence-grounded threat modeling for a repository, subsystem, or automation. Builds a system model from the actual code, derives trust boundaries and assets, enumerates realistic abuse paths with likelihood/impact priorities, and writes a reviewable Markdown threat model. Use when asked to threat model a codebase or…
Pre-test readiness workflow that finds and fixes predictable validation blockers before running expensive local or container test gates, then declares a READY, CONDITIONAL, or BLOCKED verdict. Use before full verification, before push readiness checks, after substantial implementation, or when work is likely to hit…
Impact-scoped review that maps user actions, critical paths, roles, states, and mutations to Playwright/E2E plus unit/integration evidence. Use after an accepted plan and before implementation for substantial feature, frontend, workflow, route, mutation, auth/role, upload, save/delete, navigation, admin/user portal…