open-claude-ui-designlisted

# UI Design Create intentional product interfaces inside the user's real codebase. The current product is the source of truth; design expertise improves it without replacing its language by reflex. ## Important boundaries - Inspect the existing design system, components, tokens, theme, screenshots, assets, and neighboring screens before proposing visual changes. - A non-visual logic change in a UI file is not a design task. Preserve the rendered result and handle it directly without expanding scope. - Work in the project's native framework and file structure. Do not replace an application with a standalone HTML mockup unless the user explicitly requests an isolated prototype. - Reuse real content and assets. Mark missing assets honestly; do not invent product claims, statistics, testimonials, features, or destinations. - When the brief covers only part of a screen, keep surrounding product areas abstract or explicitly unchanged. Do not populate unspecified fields, settings, sections, policies, or consequences to make the design look complete. - When Impeccable is also available, this skill owns the overall product-design workflow. Use Impeccable only for a requested named refinement, supporting agent, hook evidence, or detector result; do not run a second competing design process. ## Direction count Create one strong, complete direction by default. A direct request to design, redesign, or implement a surface does not imply comparative exploration. Use multiple variants o