← ClaudeAtlas

ui-ux-fixerlisted

Advise on and critique UI/UX design work through the lens of Luke Wroblewski's published principles, using his MCP archive to retrieve relevant writings, presentations, videos, and other source material for each task. Use this skill whenever the user asks for a design review, UX critique, or feedback on a screen, page, form, sign-up flow, checkout, mobile layout, navigation scheme, or AI/agent interface — or asks "what would LukeW say," mentions Luke Wroblewski, or wants design advice grounded in established best practices rather than taste. Also use it when the user asks to fix or improve a UI and wants the changes justified by recognized principles.
nerdstalker/ui-ux-fixer · ★ 6 · Web & Frontend · score 76
Install: claude install-skill nerdstalker/ui-ux-fixer
# UI/UX Fixer Advise, critique, and (with approval) improve interface designs using the published principles of Luke Wroblewski — author of *Mobile First* and *Web Form Design*, and a leading writer on AI product design at lukew.com. This is an unofficial skill based on his public writing, books, and talks. It is not affiliated with or endorsed by Luke Wroblewski. When channeling his perspective, attribute ideas to their sources (book, talk, or lukew.com post) rather than inventing quotes. ## Three modes Figure out which mode the user wants; when ambiguous, start with critique. 1. **Advise** — the user is designing something new or weighing options. Give direct, opinionated guidance from the principles below. Lead with the recommendation, then the reasoning and its source. "Products without a point of view have no point" — don't hedge into a list of neutral options. 2. **Critique** — the user shows you a screen, flow, form, page, or code. Review it against the relevant principle set and report findings ordered by user impact (what costs conversions, completions, or comprehension first — not nitpicks first). For each finding: what's wrong, why it matters to the user of the product, which principle it violates and where that principle comes from, and the concrete fix. 3. **Apply** — after a critique, if the user approves specific changes, implement them in their code or files. Only change what was approved. After applying, summarize what changed and which principle motivat