---
name: workflow-interface-design
description: Design new web UI or make a substantial visual refinement within the web-development workflow. Use when the visual direction needs design judgment and no explicit or established primary design specialist already owns it. Preserve the actual brief and approved DESIGN.md.
license: MIT for this adapter; Apache-2.0 for the bundled source
---

# Interface design adapter

Read the [preserved Frontend Design guidance](references/upstream.md) for the relevant design task. It is an Apache-2.0 source snapshot from Anthropic, reviewed 27 October 2026; its [license](LICENSE.txt) remains attached. This [MIT-licensed adapter](ADAPTER_LICENSE.txt) supplies the application rules below; it does not require an Anthropic account or runtime.

1. Inspect the actual screen, audience, primary decision, required content, project tokens and approved DESIGN.md. Infer settled choices and ask only for missing choices that change the result. Use one primary design workflow.
2. Apply the source's intentionality, hierarchy, typography and subject-specific composition to that brief. Its assumed client history is hypothetical. Do not claim prior rejected proposals, invent project facts or force aesthetic rules over approved decisions. Existing cream palettes, serif fonts, cards or wordmarks can be appropriate. Match density and restraint to the product.
3. For a consequential unresolved direction, render a bounded prototype or a few distinct options. Within an approved direction, implement directly. Use truthful copy and authorized assets; keep missing content explicit. Do not write memories or new product records without task authorization.
4. Build the complete affected interaction with semantic controls, visible focus, useful states, responsive reading order, contrast, zoom/reflow and reduced-motion support. Decoration and animation need a purpose. Keep the project's framework and dependencies.
5. Inspect the rendered result at relevant sizes with realistic content. Compare it with the approved direction and fix visible defects. A code-only review does not prove visual quality. Record the evidence and any unavailable check; use a separate interface review for a substantial release.

Return the concrete change, design rationale that matters, rendered checks and unresolved decisions. Do not substitute an aesthetic score for observed usability.