agentleFS
Sign inStart free
kelgirechandrakant-cpukelgirechandrakant-cpu/vibe-coding-playbook/skills/ui-ux-review/SKILL.md

design-review

Skill4 starsChanged 3 months agoMITView on GitHub

UI/UX, accessibility, and responsiveness audit. Detects visual inconsistencies, alignment issues, and AI 'slop' design patterns. Use for UI audits or before shipping visual changes.

155 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use project-stage-detect, team-audio and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    project-stage-detect

    Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.

    Also in 16 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 10 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 10 projects that use this

  • +4 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When auditing a UI component or page layout, evaluate it against the following professional design principles:

    line 8
  2. Distinctive:

    Do multi-column grids gracefully collapse into a single column on small screens?

    line 18
  3. Very specific:

    Do interactive elements (buttons, links) have aria-labels if they lack text?

    line 21
  4. Very specific:

    Do images have meaningful alt attributes?

    line 22

“Common” is measured: kept by at least 6 in 10 of the 129 edited versions of this file we could read. “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

Design Review Protocol

When auditing a UI component or page layout, evaluate it against the following professional design principles:

1. Visual Hierarchy & Spacing

  • Does the page have a clear primary action (CTA)?
  • Are margins and paddings consistent? (e.g., using a strict 4px/8px/16px/32px scale).
  • Is the text contrast high enough for readability?

2. Responsiveness

  • Does the layout break on a 320px wide mobile screen?
  • Are touch targets at least 44x44px for mobile users?
  • Do multi-column grids gracefully collapse into a single column on small screens?

3. Accessibility (a11y)

  • Do interactive elements (buttons, links) have aria-labels if they lack text?
  • Do images have meaningful alt attributes?
  • Can the user navigate the component using only the Tab key?

4. "AI Slop" Detection

AI often generates cliché designs. Check for and eliminate:

  • Excessive, meaningless icons next to every text block.
  • Pointless gradient backgrounds where solid colors would be cleaner.
  • Dashboard layouts for tools that don't need a dashboard.

Output

Provide a list of layout fixes, starting with structural breaks (mobile overflow) down to visual polish (padding tweaks).

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.

Check your setup, free