open-claude-design-qualitylisted

# UI Design Quality Apply these stable constraints to user-visible interface work. Preserve the rendered interface during logic-only changes; do not broaden them into redesigns. When a selected design workflow requires independent assessors or finish reviewers, that workflow requirement plus an exposed agent tool is sufficient authorization to delegate the bounded review. Use the minimum required agents and do not ask a routine permission question. ## Start from the product **Preserve the current visual language unless the user asks to change it.** Read the relevant components, tokens, theme, screenshots, brand guidance, and neighboring screens before making visual decisions. Exact project values outrank generic design advice. - Keep the project's component library, CSS methodology, icon set, typefaces, spacing scale, radii, shadows, and motion language. - Reuse real product content and assets. Do not invent testimonials, statistics, features, destinations, or decorative copy to fill space. - Treat an absent design system as a decision point, not permission to fall back to a generic template. Establish a small coherent direction tied to audience, purpose, and tone. ## Make the hierarchy legible - A first-time user can identify the page purpose, primary information, and next action without hunting. - Use size, weight, color, position, and density deliberately. Do not make every element equally loud or equally muted. - Give each screen a clear primary action when the pro