Use when designing, reviewing, or modifying backend API endpoints, schemas, validation, and API documentation.
Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules.
Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation.
Use when React components are too large or complex and need extraction, simplification, or separation of concerns.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code.
Use when implementing or reviewing football data logic, pitch coordinates, event modeling, or sports vision pipelines.
Use when reviewing frontend code changes for correctness, quality, performance, and maintainability risks.