How to think about reliable systems in domain models. Use when designing state management, type systems, domain boundaries, error handling, or service contracts. Triggers on discussions of React state, backend data flow, database design, making illegal states unrepresentable, deriving values instead of storing them, or preventing bugs through types.
Final self-review of your own completed work before wrapping up or committing. Use ONLY after you have finished implementing and are about to stop — never at the start of a task, never mid-implementation, and never to plan upcoming work. Triggers: "self-review", "review your work", "before we commit", "wrap up", or when you are done coding and ready to hand off.
Write copy following brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Cache Voice tones.
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.