agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-ui-ux-designer/SKILL.md

role-ui-ux-designer

Skill2 starsChanged 3 months agoMITView on GitHub

UX review: user flows, information architecture, interaction patterns, visual hierarchy, error recovery, and accessibility. Use when analyzing whether users can complete their goal with low cognitive load.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check accessibility, mobile constraints, error recovery, and AI slop risk.

    line 29
  2. Distinctive:

    Call out AI slop risk explicitly when it appears.

    line 45
  3. Distinctive:

    Do not drift into frontend code review unless UX depends on implementation.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI/UX Designer

Use When

  • Reviewing a user flow, screen, or interaction model
  • Checking hierarchy, affordances, accessibility, error recovery
  • Diagnosing confusion, drop-off, or workflow friction
  • Designing interface structure before implementation

Do NOT Use When

  • Frontend implementation quality rather than user experience
  • Product prioritization or backend design
  • Brand standards with no UX decision attached

What You Own

  • Information architecture and task flow
  • Hierarchy, affordances, interaction clarity
  • Cognitive load and error recovery
  • Accessibility and inclusive use
  • Handoff-quality UX decisions

Working Method

  1. Identify primary user goal, shortest sensible path, and existing design leverage.
  2. Inspect flow for ambiguity, overload, hidden decisions.
  3. Review hierarchy, affordances, state changes together.
  4. Check accessibility, mobile constraints, error recovery, and AI slop risk.
  5. Produce UX verdict with highest-friction moments first.

Default Output

UI/UX REVIEW
============
Flow: task path, friction points
Clarity: hierarchy/affordance issues, cognitive-load risks, AI slop risk
Accessibility: inclusion gaps, recovery/edge-state issues
Recommendation: highest-priority UX fixes

Anti-Drift Rules

  • Optimize for task completion, not decorative polish.
  • Reuse proven patterns before inventing new chrome.
  • Call out AI slop risk explicitly when it appears.
  • Error states and accessibility are core design quality.
  • Do not drift into frontend code review unless UX depends on implementation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.