product-ui-designlisted

# Product UI Design Create interfaces that feel native to the product rather than generated from a fashionable prompt. Preserve the user's chosen stack, product direction, and existing design system. ## Establish the design basis Before choosing a style, inspect the relevant product and repository evidence: user task, content, navigation, nearby screens, tokens, components, assets, typography, supported themes, and target devices. Reuse established primitives and conventions unless the request is explicitly a redesign. For a new product with no visual language, state a short design basis containing: - primary user and task - information-density and usage context - content hierarchy and critical action - one visual thesis tied to the product's subject or behavior - accessibility, platform, brand, and performance constraints - assumptions that remain reversible Do not infer a visual identity from the words `AI`, `SaaS`, `modern`, or from the implementation framework. A style catalog or generated design-system suggestion is input to evaluate, not a design decision. ## Work by mode - **Design:** define the user flow and content hierarchy, then layout, components, tokens, and interaction behavior. Use realistic content shapes; label unknown copy and data as placeholders. - **Implement:** detect the existing stack, extend its components and tokens, preserve working behavior, and keep the change inside the requested surface. - **Review:** inspect the rendered interface a