critique
Skill441 starsChanged 3 months agoMITView on GitHub
Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table, no code edits unless asked. Use when the user wants a design review, says \"what's wrong with this UI\", or needs a second opinion before a handoff or presentation. Invoke when the user asks for critique on their UI, or mentions 'critique' alongside design / UI / frontend work.
80 other projects use a version of this.
Adopted by
Most recently taken up by
- Lucface/claude-skillstheir own version, first seen Nov 16, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- bas1l/claude-skillstheir own version, first seen Nov 11, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 10, 2026
- BSchrift/critique.nvimtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use teach-impeccable, overdrive and 3 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.
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 19 projects that use this
HK-hubSkilloverdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.
Also in 25 projects that use this
zwy123zwySkillnormalize
将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。
Also in 19 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
- +1 more from HK-hub
Other versions80 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 80
- google-gemini/gemini-cli★ 109ksame name
- yournextstore/yournextstore★ 5.5ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- remorses/critique★ 1.3ksame name
- talesofai/cohub★ 585same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- Southclaws/storyden★ 348same name
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 327same name
70 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/ui-craft/references/agents.mdAGENTS.md
- adaptSkill
- animateSkill
- auditSkill
- bolderSkill
- briefSkill
- clarifySkill
- colorizeSkill
- craftSkill
- delightSkill
- distillSkill
- extractSkill
- finalizeSkill
- hardenSkill
- heuristicSkill
- polishSkill
- quieterSkill
- redesignSkill
- rememberSkill
- sddesignSkill
- shapeSkill
- startSkill
- tokensSkill
- typesetSkill
- ui-craft-dense-dashboardSkill
- ui-craft-editorialSkill
- ui-craft-minimalSkill
- ui-craftSkill
- unhappySkill
- friction-logSkill
- friction-logSkill
- ui-craft-dense-dashboardSkill
- ui-craft-editorialSkill
- ui-craft-minimalSkill
- ui-craftSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 73 edited versions we read keep these.
2
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
- Distinctive: line 26
Do not begin the review until visuals are captured or provided.
- Very specific: line 28
If the user declines to provide screenshots, run a code-only pass and clearly mark the report [CODE-ONLY REVIEW — visual issues not …
- Distinctive: line 51
Do NOT edit code. This is a critique.
“Common” is measured: kept by at least 6 in 10 of the 73 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.
Files
<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.
Critique the UI at $ARGUMENTS through a design lens. Load the ui-craft skill.
Step 0: Visual capture (mandatory)
Code-only review is insufficient. Every audit/critique starts with the surface as the user sees it. Try the following in order; use the first one available:
- Playwright MCP — if
playwrightMCP server is available, use it. Capture full-page screenshots at three viewports: desktop (1280×800), tablet (768×1024), mobile (375×812). Capture dark mode if the app supports it. - Browser DevTools / Chrome MCP — second choice; same viewport set.
- Other browser automation (
agent-browser,cursor-ide-browser) — third choice. - Ask the user — last resort. If no automation is available, request screenshots from the user before proceeding. Be specific:
- "Visual review needs screenshots. Please provide:
- Full-page at 1280px (desktop)
- Full-page at 768px (tablet)
- Full-page at 375px (mobile)
- Dark mode of each, if supported."
- "Visual review needs screenshots. Please provide:
Do not begin the review until visuals are captured or provided. State this explicitly to the user when no automation succeeds — don't silently fall back to code-only review.
If the user declines to provide screenshots, run a code-only pass and clearly mark the report [CODE-ONLY REVIEW — visual issues not assessed] at the top so the limitation is explicit.
Knob awareness (CRAFT_LEVEL sets the bar for what counts as "needs work"):
CRAFT_LEVEL 3→ flag only anti-slop Critical items. Skip Minor polish.CRAFT_LEVEL 5-7→ flag Critical + Major. Mention Minor polish as optional.CRAFT_LEVEL 9+→ flag everything, including Minor polish and missing signature detail.
Run these lenses in order:
- Anti-Slop Test (from SKILL.md): flag every item present. Critical first (ALL CAPS, purple gradients, identical card grids, bounce easing, emoji icons, glassmorphism + neon). Then major (colored pills on trends, thick colored borders, uniform radii, gradient text, walls of text). Then minor (straight quotes, missing
tabular-nums, generic CTAs). - Craft Test (from SKILL.md): where does the design fall short of "one accent, 3-5 placements; plain secondary text for comparisons; functional color only; every section earns its space"?
- Hierarchy: can the user tell what's primary, secondary, tertiary at a glance? Or does everything shout equally?
- Clarity: is the value prop legible in 5 seconds? Are CTAs specific (not "Learn more")?
- Signature detail: is there one memorable element that makes this feel designed, not assembled? If not, suggest one (motif, layout break, custom marker, distinctive hover).
- Inspiration gap — read
references/inspiration.md: which observed pattern from the archetypes / signature details applies here, and how does the current state diverge from it?
Output format — the Review Format table:
| Before | After | Why |
Prioritize by impact, not by file order. End with a one-paragraph summary of the top 3 changes that would raise this from "AI-generated" to "designed".
Do NOT edit code. This is a critique.
Close with a Craft Report (references/review.md → Craft Report) as the final wrapper around the findings table and top-3 summary — Checked names the lenses actually run (Anti-Slop, Craft Test, Hierarchy, Clarity, Signature, Inspiration gap) and at what CRAFT_LEVEL bar, Passed carries whatever held up under those lenses, Changed stays empty (critique doesn't edit), Left alone covers anything flagged but out of scope, Verdict is the one-sentence state. Produce it even when the surface passes clean — that's the validation the user is asking for.
Next step: /polish — apply the fixes this critique named (rung 1).
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
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.

