design-critique SKILL.md skillA
design-critique from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/design-critique@git:20260303.00c2750Pins git:20260303.00c2750 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/designer/design-critique/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.00c2750, committed Mar 3, 2026
- Size
- 4,787 bytes
- Repository stars
- 21
- License
- MIT
Critique a design for usability, hierarchy, and accessibility. Use when the user says "critique this design", "review this screen", "what's wrong with this UI", "design feedback", "UX review", "how can I improve this", "review my mockup", "is this good UX", or shares a design and wants structured feedback - even if they don't explicitly say "design critique".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview Based on **"The Design of Everyday Things"** by Don Norman. Norman's framework: good design makes the right action obvious and the wrong action difficult. Bad design forces users to think when they should act. A critique is not about aesthetics - it's about whether the design communicates correctly: what can I do here, how do I do it, and did it work? Norman's three key concepts: - **Affordances** - what actions does the design suggest are possible? - **Signifiers** - what cues communicate where and how to act? - **Feedback** - does the system communicate the result of every action? ## Workflow ### Step 1: Define the user goal Before critiquing, state: what is the user trying to accomplish on this screen? Critiques without a user goal produce aesthetic feedback, not usability feedback. ### Step 2: Check affordances and signifiers Walk through every interactive element: - Is it obvious this is clickable/tappable/draggable? - Does the visual design suggest the correct interaction? - Are buttons distinguishable from static content? - Does the hierarchy direct attention to the primary action? Norman: "If it requires a label, the design has failed." …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/design-critique@sha256:5592740ea8ae73b1The line at the top of this page pins the label git:20260303.00c2750, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kdwqov27jfyr4oij)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4787 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kdwqov27jfyr4oij GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/design-critique GET https://markdownregistry.com/api/v1/blob/5592740ea8ae73b15d6cb681a242285e7b718f25614db438ac03c3ae7284f4c0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills