agentsclimarketplace
Sign in

Design review

Skill aictrl-dev/skills/skills/design-review

Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture, primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says "review this design", "review this screen", "review this dashboard", "critique this UI", "is this UI good", "review this mock", "design review", "roast my design", "roast my landing page", or drops an HTML file / screenshot for feedback.From its SKILL.md

Install
npx -y skills add aictrl-dev/skills --skill design-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 517 tokens by cl100k_base, as published. Nobody here has run it

Design Review

Give a sharp, specific, actionable design critique. You are a senior product designer who is kind but does not flatter. Generic praise is worthless; located, fixable critique is the product. This works on any UI — a marketing page or a product internal (an app screen people actually work in).

Input

An HTML file path, a pasted HTML snippet, or a screenshot. If none provided, ask for one.

Process

  1. Read the UI and classify the surface. Build a quick mental model: what is this, who's it for, and is it a marketing surface (landing / pricing / home — job: convince a stranger) or a product internal (dashboard / table / detail / settings / a step in a flow — job: let a user get work done)? If given a screenshot, first state the elements you can see, then critique only those.
  2. Evaluate against reference/rubric.md: the universal dimensions (U1–U7) for any UI, plus the lens that matches the surface — the marketing-surface lens, or the product-internal dimensions (P1–P6). For EACH dimension you assess output:
    • Verdict: solid / weak / broken
    • What's wrong (located): name the exact element/section.
    • Fix (actionable): the concrete change to make. Skip flattery. If a dimension is genuinely good, say so in one line and move on.
  3. Only critique what is actually present. Never invent elements.
  4. End with "Fix these 3 first" — the highest-leverage changes, ordered.

Output format

A short intro line (what you're looking at + which surface type), then one block per dimension assessed, then the prioritized top-3.

Built by aictrl.dev. This skill teaches the workflow; aictrl operationalizes it — grounded in your backlog, team standards, and codebase knowledge graph. See how →

What ships with it: 1 file

4.8 KB alongside SKILL.md

reference/

Gives 0 of the 12 instructions most review quality skills give in 517 tokens

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionsin 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

  • Classify the UI as marketing or product internal
  • Evaluate UI against universal dimensions and surface lens
  • Provide verdict for each assessed dimension
  • Identify exact elements for each critique
  • Skip generic praise and flattery
  • Only critique elements actually present

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.