Reviews staged changes, commits, or pull-request diffs for correctness, security, regressions, scope, and test gaps. Use for code review, pre-commit, pre-push, merge-safety, diff-review, refactor-verification, or test-quality requests. Do not use to diagnose an active failure or implement new work.
Use only when a multi-part implementation plan contains independent work that would materially benefit from separate context windows, specialized focus, or parallel execution. Delegation is optional per task, not a required review pipeline.
Diagnoses code defects with evidence and falsifiable hypotheses, then applies and verifies root-cause fixes when requested. Use for bugs, crashes, stack traces, failing or flaky tests, regressions, wrong output, hangs, leaks, races, or unexplained performance loss. Do not use for feature work, code review, or infrastructure-only incidents.
Designs, implements, and critiques web, mobile, and desktop interfaces with intentional UX, visual hierarchy, responsive or adaptive behavior, and accessibility. Use for new pages and components, redesigns, dashboards, landing and pricing pages, forms, navigation, design systems, visual polish, dark mode, responsive UI, accessibility design or remediation, or requests to make an interface look better or less generic. Also use when modifying UI code where visual or interaction quality is part of the task. Do not use for a motion-only change when layout is settled, product strategy, or root-cause debugging of an isolated implementation defect; combine it with systematic-debugging when a UI defect also requires design judgment.
Designs, implements, and audits the experience of interface motion for web, mobile, and desktop products. Use for transitions, micro-interactions, hover or press feedback, loading states, animated icons, route and view transitions, scroll-linked effects, gesture physics, choreography, ambient or brand motion, and reduced-motion behavior. Also use when asked to make an interface feel more responsive, tactile, alive, less static, or polished through motion and interaction feedback. Do not use for static layout and visual-system work, video or timeline production, implementation or PR code review without a redesign request, or root-cause debugging of an animation defect.
Develops evidence-grounded product and business strategy without generic startup advice. Use whenever the user is shaping or evaluating a product, startup, market, customer segment, value proposition, positioning, product-market fit, pricing, subscription, retention or growth loop, revenue model, go-to-market plan, unit economics, funding choice, or historical company tactic. Also use for product or business problems where the real question is what to build, for whom, why it will matter, how it spreads, or how it makes money. Do not use for pure UI implementation, marketing copy, investment advice, legal compliance, or software debugging.