Design production modules, interfaces, seams, types, signatures, and dependency structure before implementation. Use ONLY when the requested result is a production code shape or integration contract, such as /architect, 'architect this', 'design this module', 'improve this interface', or 'deepen this module'; do not use for throwaway HTML experiments that test state, transition, policy, scheduling, or algorithm behavior.
Review local changes, branch diffs, commits, or pull requests for correctness, security, regressions, maintainability, repository standards, specification compliance, and blast radius. Use for "review", "code review", "review my changes", "review PR", "review since X", "thermo", "thermonuclear", "deep review", "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", "tear this apart", "blast radius", "what could this break", "review canvas", "visual PR review", "PR walkthrough", or "review and ship". Accepts an optional fixed point, PR number, or PR URL.
Use only when the user explicitly asks to model a domain, establish ubiquitous language, create or update a glossary or CONTEXT.md, map contexts, or create or revise an ADR. Do not use for TDD, test-first implementation, red-green-refactor, or integration tests alone. If the user explicitly asks for both domain modeling and test-first work, load both skills.