What problem does it solve? Starting UI implementation with vague direction words like "clean" or "modern" leads to inconsistent design decisions and rework. This Skill resolves undefined visual direction by reading existing project evidence, detecting contradictions, and producing a shared DESIGN-BRIEF.md before any layout, color, typography, or motion work begins. ## Core Features & Use Cases - Evidence-first analysis: Reads README, existing design docs, tokens, components, and screens before asking the user anything, avoiding redundant questions. - Contradiction detection: Finds conflicts such as dense UI plus generous whitespace, or minimal motion plus expressive transitions, and resolves them per product surface. - Specific reference handling: Converts vague references like "Linear-like" into concrete statements about which surface, behavior, and properties to adopt or avoid. - Use Case: Before building a new dashboard UI, run this Skill to produce a DESIGN-BRIEF.md covering color direction, typography, component character, and motion level that downstream design skills consume as project evidence. ## Quick Start Analyze this project's existing context and create a DESIGN-BRIEF.md that defines the visual direction for the new settings page.
