ux-laws
Installation
SKILL.md
UX Laws
Use UX laws as design heuristics, not as proof that a design works.
Method
- Identify the primary user, task, context, and constraints. State bounded assumptions when evidence is missing.
- Read references/laws.md and select only the laws that materially affect the task. Do not force all 21 into a design.
- Design or review the complete path, including loading, empty, error, success, keyboard, touch, and responsive states when relevant.
- Resolve conflicts in this order: user safety and accessibility, user intent and evidence, domain conventions, then UX-law heuristics.
- Recommend the smallest change that improves the task. Explain the expected benefit and what usability evidence would confirm it.
Guardrails
- Do not invent user research or present a law as validation.
- Do not use fake urgency, forced progress, concealed choices, or other dark patterns.
- Do not rely on color alone for meaning or emphasis. Preserve contrast, focus visibility, target size, reduced-motion preferences, and assistive-technology semantics.
- Familiar patterns can still be poor patterns. Simplicity must not remove necessary control, information, consent, or recovery.
- When laws conflict, name the tradeoff instead of pretending every heuristic can be satisfied.