- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add educlopez/ui-craft --skill critique -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add educlopez/ui-craft --skill critique -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add educlopez/ui-craft --skill critique -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add educlopez/ui-craft --skill critique -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/educlopez/ui-craft/tree/HEAD/.agents/skills/critiqueFrom the publisher
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.
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 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.agent-browser, cursor-ide-browser) — third choice.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:
tabular-nums, generic CTAs).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:
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).
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 wi
---name: critiquedescription: Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table…---# .agents/skills/critique/SKILL.mdOverview
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.
FAQ
Download .agents/skills/critique/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/educlopez/ui-craft.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.