ui-uxlisted

# Nebu UI/UX Design for clarity, hierarchy, and usability first. Make the interface feel intentional, not generic. ## Use this when - the user wants a new UI, redesign, polish pass, UX fix, or visual review - the right layout, interaction, or visual direction is not obvious yet - the work includes screens, flows, dashboards, landing pages, forms, navigation, or design systems If the repo already has a design system or visual language, preserve it unless the user asks to change it. ## Working pattern 1. Inspect the existing product, screen, or component first. If no existing system is present, explicitly choose a reference anchor before generating anything. 2. Identify constraints: device sizes, theme, brand, accessibility, and stack. 3. Choose a clear visual direction that fits the product instead of defaulting to bland SaaS UI. 4. Make the smallest coherent set of layout, hierarchy, spacing, color, copy, and interaction changes. 5. Run a headless screenshot review on standard desktop and mobile viewports after each meaningful UI pass. 6. Fix the highest-signal issues from the review, then repeat. 7. Keep iterating without repeated approval prompts unless the visual direction itself is in doubt. ## Never do this - purple or violet as the default accent, especially `#7c3aed`, `#8b5cf6`, or generic purple gradients - `Inter` plus an oversized hero headline as the default type pairing - uniform card grids with the same `border-radius`, shadow, spacing, and visual weight