Patterns for building reusable, accessible, production-grade React/TypeScript UI components. Use this whenever you create or review a UI component, build a form, design a component API, or work on the frontend — even if accessibility isn't explicitly mentioned. Covers state handling, a11y, responsiveness, and prop…
Principles and checks for structuring code with clear boundaries, low coupling, and high cohesion. Use this whenever you are designing a new module, refactoring existing code, reviewing structure, deciding where logic should live, or untangling a messy codebase — even if the user doesn't say the words "clean…
A go/no-go checklist for shipping code to production. Use this whenever you're about to deploy, finishing a feature, opening a PR for real traffic, or someone asks "is this production-ready". Covers correctness, errors, security, observability, and scale. Applies to Go, React/TypeScript, and C#/.NET.
Use PROACTIVELY when starting a new feature, service, or MVP, or when a design decision needs to be made before code is written. Designs system architecture, data flow, API contracts, database schema, and a minimal-but-scalable implementation plan. Invoke for "design", "architecture", "how should we structure", "new…
Use when something is broken, failing, flaky, or behaving unexpectedly, and the cause isn't obvious. Reproduces the issue, traces the real root cause, explains why it fails, surfaces hidden edge cases, and proposes the most robust fix. Invoke for "bug", "error", "crash", "failing test", "works locally but not in…
Use to prepare an app for production deployment or improve its operational setup. Designs deployment architecture, CI/CD pipelines, containerization, monitoring and logging, and reliability/scaling. Invoke for "deploy", "CI/CD", "Docker", "Kubernetes", "pipeline", "monitoring", "logging", "infrastructure", "uptime"…
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
Use when code needs to be cleaned up, restructured, or made more maintainable WITHOUT changing what it does. Handles reverse-engineering an unfamiliar codebase, separating concerns, reducing coupling, removing duplication, and applying clean architecture. Invoke for "refactor", "clean up", "restructure", "reduce…
Use to audit code for security problems before shipping, after a sensitive change, or on request. Inspects for vulnerabilities, auth flaws, API weaknesses, injection risks, sensitive-data exposure, and infrastructure risk, then reports findings by severity with attack scenarios and fixes. Invoke for "security review"…