Reimagine It Audit
Kayforkind/reimagine-it
Design Health — runs 19 deterministic quality checks on HTML output.
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
Install Design Critique
$ npx skills add paperclipai/paperclip --skill design-critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install paperclipai/paperclip design-critique --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills-catalog/catalog/optional/product/design-critique .claude/skills/design-critique && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-critique" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critique into .claude/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critiqueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add paperclipai/paperclip --skill design-critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install paperclipai/paperclip design-critique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/skills-catalog/catalog/optional/product/design-critique .agents/skills/design-critique && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-critique" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critique into .agents/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add paperclipai/paperclip --skill design-critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install paperclipai/paperclip design-critique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/skills-catalog/catalog/optional/product/design-critique .cursor/skills/design-critique && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-critique" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critique into .cursor/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/paperclipai/paperclip.git --path packages/skills-catalog/catalog/optional/product/design-critique--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add paperclipai/paperclip --skill design-critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install paperclipai/paperclip design-critique --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/skills-catalog/catalog/optional/product/design-critique .gemini/skills/design-critique && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-critique" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critique into .gemini/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install paperclipai/paperclip design-critiqueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add paperclipai/paperclip --skill design-critique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/skills-catalog/catalog/optional/product/design-critique .github/skills/design-critique && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-critique" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critique into .github/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add paperclipai/paperclip --skill design-critique -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install paperclipai/paperclip design-critique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/skills-catalog/catalog/optional/product/design-critique .opencode/skills/design-critique && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-critique" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/optional/product/design-critique into .opencode/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
design-critique- GitHub stars
- 100k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 607 words
- Files
- 1
- Skills in repo
- 60
- Repo updated
- First seen
- Licence
- MIT
At a glance
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
- Works in 9 steps: Clarity of the user job. → Visual hierarchy. → Affordance and signifiers. → …
- Tasks that involve Design review and critique
- SKILL.md covers When to use, When not to use, Pre-critique context and The pass (in order), plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Critique is an agent skill from paperclipai/paperclip. Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative, covering Design review and critique. The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.
When your agent uses it
- Tasks that involve Design review and critique
Example prompts
- “/design-critique”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Clarity of the user job.
- Visual hierarchy.
- Affordance and signifiers.
- States.
- Inputs and forms.
- Accessibility.
- Consistency.
- Copy.
- Edge cases.
What it can do on your machine
Read from SKILL.md and the folder at commit de9ab8e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design Critique loads about 1.2k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 607 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from paperclipai/paperclip at commit de9ab8e, republished under its MIT licence (© paperclipai). 607 words, ~1,211 tokens.
Download SKILL.mdSave it as
.claude/skills/design-critique/SKILL.md (or your agent's skills folder).- name
- design-critique
- description
- Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
- key
- paperclipai/optional/product/design-critique
- recommendedForRoles
- designer, product, engineer
- tags
- design, product, ux, review
Product Design Critique
A structured critique pass for a screen, flow, or component. The output is a prioritized list of changes a designer or engineer can act on — not adjectives. Critique is not redesign; recommend, do not rebuild.
When to use
- A designer or engineer asks for feedback on a screen, mock, or live UI.
- A feature is shipping and someone wants a final UX read.
- A flow is suspected of causing user drop-off and you want a pre-research read before instrumentation.
When not to use
- The user wants a redesign. That is a design project, not a critique.
- The work is so early that no concrete artifact exists. Sketch with them instead of critiquing air.
- You have no context on the user job. Ask for it first; design critique without user context devolves into taste.
Pre-critique context
Before opening a screen, get:
- Who is the user. Specific role and competence, not "users".
- What job they are doing on this screen. One sentence.
- What success looks like. What the user can do after this screen that they could not before.
- Where this screen sits in the larger flow. What precedes and follows.
If any of these is missing, ask. Critique without these is opinion.
The pass (in order)
Clarity of the user job.
- Within 3 seconds of opening, is it obvious what this screen is for?
- Does the primary action match the user's actual job, or a designer's preferred path?
Visual hierarchy.
- The most important thing on the screen should be the most prominent (size, weight, position, color).
- Secondary actions should look secondary. Tertiary should be findable but not loud.
- Headings should chunk content into the right groups for the task.
Affordance and signifiers.
- Clickable things look clickable.
- Disabled things look disabled and explain why on hover/focus.
- Drag, scroll, or swipe interactions are discoverable, not hidden.
States.
- Empty state (no data) is designed, not a blank rectangle.
- Loading state communicates progress, not just spins.
- Error states say what went wrong and what to do next, in the user's words.
- Success state confirms without celebrating banal actions.
Inputs and forms.
- Labels visible, not just placeholders.
- Validation runs at the right time (on blur, not on every keystroke unless the user is in a known-format field).
- Required fields marked.
- Field order matches the user's mental order, not the database order.
Accessibility.
- Sufficient color contrast (WCAG AA at minimum; AAA where reasonable).
- Focus order is logical for keyboard navigation.
- Interactive elements are reachable without a mouse.
- Critical information is not color-only (icons, text, position back it up).
- Touch targets at least 44×44 px on mobile.
Consistency.
- Tokens, components, and patterns match the rest of the product.
- "Borrowed" patterns from other products are intentional, not accidental drift.
Copy.
- Buttons are verbs that name the outcome ("Save changes" beats "Submit").
- Microcopy explains, does not decorate.
- Tone matches the product voice.
Edge cases.
- Long content (long names, many items, RTL languages).
- Tiny content (one item, zero items).
- Slow network and offline behavior.
- Permissions denied.
Show full SKILL.md (100 more words)Show less
Output format
Group findings by severity, then by category. Each finding is one issue and one suggested fix.
## Design critique: <screen name>
### Must-fix (blocks ship)
- **<category>:** <one-line issue>. **Try:** <one-line suggestion>.
### Should-fix (before broader rollout)
- **<category>:** <one-line issue>. **Try:** <one-line suggestion>.
### Nice-to-fix (when there's room)
- **<category>:** <one-line issue>. **Try:** <one-line suggestion>.
### Strengths to keep
- <one-line thing the design got right>Always include the "strengths to keep" section. It is not flattery — it is signal to the designer about what not to change in the next round.
Anti-patterns
- "I would do it differently" without saying what or why. That is preference, not critique.
- Long critiques that bury must-fix items under nice-to-haves.
- Suggesting net-new features under the guise of a critique.
- Ignoring user context and grading on taste.
- Treating a critique as approval. State approval explicitly if asked; otherwise critique is feedback, not sign-off.
© paperclipai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/skills-catalog/catalog/optional/product/design-critique of paperclipai/paperclip.
Open the folder on GitHubat commit de9ab8e
Compare with similar skills
Design Critique next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Critique this skillpaperclipai/paperclip | 100k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Reimagine It AuditKayforkind/reimagine-it | 205 | — | ~756 | Automated safety check: Pass | MIT | |
| Design Reviewtsubotax/melta-ui | 201 | — | ~504 | Automated safety check: Pass | MIT | |
| Canva Design Feedbackcanva-sdks/canva-skills | 119 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Design CritiqueWrongStack/WrongStack | 374 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Steve Jobs Design Reviewwondelai/skills | 2.4k | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
Design Review
tsubotax/melta-ui
HTMLファイルをmelta UIデザインシステムに照らしてレビューし、違反を検出・分類・修正提案する。トリガー: 「デザインレビュー」「DSチェック」「禁止パターンチェック」「design review」「check compliance」「DS準拠確認」。対象ファイルのパスを引数で受け取る。
Canva Design Feedback
canva-sdks/canva-skills
Read a Canva design and return structured, actionable design feedback — visual hierarchy, copy/messaging, layout & spacing, consistency, readability, and accessibility.
Design Critique
WrongStack/WrongStack
A skill your agent uses to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states…
Steve Jobs Design Review
wondelai/skills
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence.
Openclaw Design
openclaw/clawhub
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance.
More from paperclipai/paperclip
All 60 skills in this repoGarden Inbox
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
Paperclip
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
Paperclip
paperclipai/paperclip
A skill your agent uses for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and…
Design Guide
paperclipai/paperclip
Paperclip UI design system guide for building consistent, reusable frontend components.
Paperclip Page
paperclipai/paperclip
Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.
Paperclip Create Agent
paperclipai/paperclip
Create new agents in Paperclip with governance-aware hiring.
Related
Categories
Questions about Design Critique
What does Design Critique do?
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why. Design Critique is an agent skill from paperclipai/paperclip. Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
When should I use Design Critique?
Design Critique fits situations like: tasks that involve Design review and critique.
How do I install Design Critique in Claude Code?
Run `npx skills add paperclipai/paperclip --skill design-critique -a claude-code`. Or copy the skill folder (packages/skills-catalog/catalog/optional/product/design-critique in paperclipai/paperclip) into .claude/skills/design-critique in your project. Claude Code loads it when a task matches its description.
How do I install Design Critique in Codex?
Run `npx skills add paperclipai/paperclip --skill design-critique -a codex`. Or copy the skill folder (packages/skills-catalog/catalog/optional/product/design-critique in paperclipai/paperclip) into .agents/skills/design-critique in your project. Codex loads it when a task matches its description.
Can I use Design Critique in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add paperclipai/paperclip --skill design-critique -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-critique, .gemini/skills/design-critique, .github/skills/design-critique and .opencode/skills/design-critique in your project.
What does Design Critique need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Critique is instructions for the agent only.
Does Design Critique access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Design Critique safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Design Critique use?
Design Critique is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design Critique use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design Critique?
Skills that share tags, products or a category with Design Critique: Reimagine It Audit (Kayforkind/reimagine-it, 205 stars), Design Review (tsubotax/melta-ui, 201 stars), Canva Design Feedback (canva-sdks/canva-skills, 119 stars) and Design Critique (WrongStack/WrongStack, 374 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Critique?
paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 99,905 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 11, 2026.
Source: paperclipai/paperclip on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.