ui-ux-lawslisted

# UI/UX Laws — Applied Rulebook This skill is a working ruleset, not trivia. Every law below is a **constraint Claude enforces on its own output**, in priority order. If a design choice violates a higher-priority law to serve a lower-priority one (e.g. sacrificing clarity for novelty), fix the design before presenting it. This skill governs *usability and cognitive ergonomics*. If `frontend-design` (or similar aesthetic skills) is also active, use both together: `frontend-design` picks the bold visual direction, this skill makes sure that direction never breaks usability. On conflict, this skill wins — see Priority Hierarchy. ## How to use this skill 1. Before designing: note the user's goal and their likely mental model (what similar interfaces they already know — Jakob's Law). 2. While designing: run through "Core Laws & Principles" for the specific elements you're building (forms, nav, lists, onboarding, etc.) and apply the relevant ones. 3. Before presenting: run the **Pre-Ship Checklist** at the bottom. Silently fix anything that fails it — don't ask the user for permission to be usable. 4. If a request explicitly asks for something a law would normally discourage (e.g. "make every option visible, no hiding anything"), honor the user's explicit instruction — these laws resolve *ambiguity and default choices*, they don't override direct requests. 5. If the task is to **critique or audit an existing UI** (a screenshot, a competitor site, someone else's code) rather tha