uxilisted

UX research and UI design guidance for any product in any domain. Use this whenever the work touches interface design, usability, design critique, accessibility, design systems, user research, information architecture, onboarding, forms, dashboards, landing pages, empty and error states, or interface copy. Trigger it even when the request sounds like plain frontend work ("build a settings page", "make this look better", "our signup is leaking users", "review this screen"), because in those requests the design decisions are the hard part and the code is the easy part. Covers heuristic evaluation, WCAG 2.2 conformance, visual craft, research method selection, success metrics, and deceptive-pattern screening, with runnable Python tools for contrast checking, HTML accessibility linting, CSS craft linting, research statistics, and audit validation.
ahammadnafiz/uxi · ★ 2 · Web & Frontend · score 76

Install: claude install-skill ahammadnafiz/uxi

# UX This is a working procedure for designing interfaces and for checking whether they actually work. It is domain agnostic on purpose. A checkout, a radiology dashboard, a game settings menu, and an internal deploy console all get the same procedure. What changes is the surface class and the failure modes, and this skill names both for you. Two things it will not do. It will not hand you a visual style, because that belongs to the project's own design file or brand. And it will not let you skip framing the problem before you draw, because that is where most bad interfaces come from. ## Start here: what kind of ask is this? | The request sounds like | Do this | Read next | |---|---|---| | "Review this screen / is this good?" | Run the audit in Step 2, report by rung | `references/heuristics.md` | | "Design a screen / flow / app" | Step 0, Step 1, then build, then the ship gate | `references/visual-craft.md`, the matching playbook | | "Why is this metric bad?" | Step 1 question 3, then diagnose bottom up | `references/research.md` | | "Is this accessible?" | Run the accessibility pass on its own | `references/accessibility.md` | | "Should we build X pattern?" | Check the floor first, then Step 1 | `references/ethics.md` | | "How do we find out what users want?" | Pick a method by question type, not by habit | `references/research.md` | | "Write the copy for this state" | Voice, then clarity, then the specific state rules | `references/heuristics.md` (writing section) | |