Use when you need a comprehensive code review combining architecture, security, and test perspectives - especially before merging, releasing, or after major changes.

Use when optimizing landing pages, signup flows, checkout processes, or any user-facing page for higher conversion rates - before A/B testing.

Use when adding a new UI component to an existing module - handles templates, inputs, and test scaffolding.

Use when adding server state management or shared logic - creates an auto-imported composable with useFetch/useAsyncData.

Use when adding server state management to a module - creates React Query hook with caching and error handling.

Use when adding a signal-based store or utility service - creates injectable with inject() and Angular Signals.

Use when adding an interactive UI component that requires client-side JavaScript - creates a framework island with hydration strategy.

Use when creating a new feature module with all layers - service, adapter, types, state, components, and tests.

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when adding state management to a module - creates Svelte store with server state integration.

Use when a module needs test coverage - creates tests for adapters, services, and components.

Use when integrating with an API endpoint and need TypeScript types, contracts, and adapters generated automatically.

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Use when feature implementation is complete and the branch is ready for final validation, PR creation, or merge.

Use when you want to stress-test code by having an adversarial reviewer try to break it - finding edge cases, security holes, race conditions, and logical flaws that normal reviews miss.

Use when the codebase has architectural issues like high coupling, circular dependencies, or unclear boundaries - but a full migration is not needed.

Use when transforming a project's architecture pattern - e.g., Flat to Modular, MVC to Clean Architecture, Monolith to Modular Monolith.

Use when a component needs migration to the target architecture or framework version.

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.