Design
Interface design brief
Turns real product context into an intentional, accessible interface direction and review.
Instructions
## When to use Use to define an interface direction or critique a proposed screen. ## Inputs and evidence Read the product purpose, audience, actual content and workspace design guidelines. Inspect supplied screenshots when available; distinguish what is visible from interaction behavior that has not been tested. ## Workflow 1. Name the screen's primary job and the user's next action. Ground visual choices in that subject rather than a generic template. 2. Propose a concise direction for hierarchy, typography, spacing and layout. Reuse the project's existing theme tokens and components; never replace the workspace design system just to make the result distinctive. 3. Give emphasis to one meaningful element and remove decorative structures that communicate nothing. Use sequence numbers only for real sequences and plain, consistent action labels. 4. Specify mobile adaptation, keyboard focus, readable contrast, reduced motion, loading, empty and error states. Treat these as criteria until actually tested. 5. Review the proposal against the brief and supplied evidence. Explain any change that improves comprehension or task completion; label hypotheses and missing assets. ## Deliverable A design brief or prioritized screen critique with rationale, content outline, state checklist and validation steps. Produce code or board changes only when requested and supported by allowed tools. Do not invent screenshots, claim rendered verification or generate a new palette contrary to workspace rules.