agentleFS
Sign inStart free
adityareddy-devadityareddy-dev/deskstudio/skills/design-critique/SKILL.md

design-critique

Skill43 starsChanged 23 days agoMITView on GitHub

A heuristic critique of a screen or flow against the Nielsen ten usability heuristics plus the studio rubric, from a screenshot, a file or a URL. Use when you want a usability read, not a redesign.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use color-system, ux-writing and 7 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.
  • launchapp-devSkill

    color-system

    Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.

    Also in 3 projects that use this

  • brianciouSkill

    ux-writing

    UX writing guidelines for reviewing and optimizing interface copy. Use when the user asks to review, improve, or rewrite UI text including button labels, error messages, onboarding flows, or any interface copy. Apply when auditing microcopy for web apps, mobile apps, or any digital product requiring clear, user-centered communication.

    Also in 5 projects that use this

  • jpoindexterSkill

    design-system-audit

    Audit code for design system violations - grid spacing, tokens, existing components

    Also in 3 projects that use this

  • agentes100xSkill

    brand-identity

    Proporciona la fuente única de verdad para lineamientos de marca, tokens de diseño y voz/tono. Usa esto para mantener consistencia visual y de comunicación.

    Also in 3 projects that use this

  • nandanosqlSkill

    design-brief

    Create a design brief that clearly communicates the product context, user needs, constraints, and success criteria to the design team — bridging PM requirements and design execution.

    Also in 3 projects that use this

  • AnthropicSkill

    competitive-analysis

    Framework for building competitive landscape decks — market positioning, competitor deep-dives, comparative analysis, strategic synthesis. Use when the user asks for a competitive landscape, competitor analysis, peer comparison, market positioning assessment, strategic review, or investment memo deck. Also triggers on "who are the competitors to X", "benchmark X against peers", "build a market map", or any request to systematically evaluate competitive dynamics across an industry.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 31 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

Critique a design as the Design Manager. No roughs, no pick, no polish: the studio looks, names what works and what fails, and says what to change.

Deliverable and standard. A critique report. Scored on two lists: the Nielsen ten (visibility of status, match with the real world, user control, consistency, error prevention, recognition over recall, flexibility, minimal design, error recovery, help) each rated pass, weak or fail with the evidence, and the studio rubric's eight axes. The standard is whichever matches the input, else the house style.

Desks.

DeskAgentTierDoes
UX Designerdesk:ux-designerseniorthe ten heuristics, with the element and the fix for each weak or fail
Content Designerdesk:content-designerbuilderlabels, errors, empty states and microcopy against the copy standard
Creative Directordesk:creative-directordirectorthe rubric scores and the three changes that matter most

Inputs. A screenshot (the default mode), a set of screenshots for a flow with --flow, an HTML file, or a URL. Screenshot mode is the common case: nothing is rendered, the desks read the images. A file or URL is rendered by proof at the sizes first so the critique is of the real thing, and the proof failures are listed under the heuristics as evidence.

Proof sizes. Screenshot mode: none. File or URL: --sizes, else phone,desktop.

Output under .desk/out/<id>/:

  • critique.md: a one-paragraph read, the heuristics table (heuristic, rating, where, fix), the rubric scores, the copy findings, then "Three things to change first".
  • renders/ when a file or URL was rendered.

Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: design-critique. Changes to the loop for this command:

  • Skip roughs, pick, polish and sign-off as gates. Phase order: intake, render (file or URL only), critique (UX Designer and Content Designer in parallel), score (Creative Director), report.
  • The Creative Director's scores are a reading, not a gate: under-bar does not loop. The report carries them as they are.
  • In screenshot mode the brief's Sizes line says "screenshot" and state records proof: [].

The ask: $ARGUMENTS

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