What problem does it solve? Code review workflows often miss visual and design issues because there is no consistent rule for deciding when a task actually involves UI work. This Skill defines a deterministic four-signal gate that automatically decides whether a design review layer should be added during ce:work or ce:review, preventing both missed UI reviews and unnecessary over-review of backend tasks. ## Core Features & Use Cases - Four-Signal Gate Detection: Evaluates Plan Signal (UI keywords in plan files), File Signal (frontend file changes like .tsx, .css, .vue), Artifact Signal (Figma URLs, screenshots, design specs), and Exclusion Signal (API design, schema, pure backend tasks) to decide if design review applies. - Combination-Based Triggering: Triggers design review only when signal pairs match (Plan+File, File+Artifact, or Plan+Artifact), with Exclusion Signal overriding when no frontend files changed. - Design Reviewer Dispatch: Automatically adds design-implementation-reviewer, figma-design-sync, and design-iterator agents to the Advisory Tier of ce:review, producing a UI review checklist covering spacing, design tokens, responsiveness, accessibility, and loading states. - Use Case: When a developer fixes a Button style (button.css changed, plan mentions "style fix"), the gate triggers Plan+File and automatically adds visual review to the review pipeline, while a SQL injection fix is correctly excluded. ## Quick Start Run ce:work or ce:review on a task and the four-signal gate will automatically determine whether design review agents should be included.
