critique-theater skill
Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.
Is the critique-theater skill safe?
Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.
No findings.
Install the critique-theater skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/nexu-io/open-design.git /tmp/open-design mkdir -p ~/.claude/skills cp -r /tmp/open-design/plugins/_official/atoms/critique-theater ~/.claude/skills/critique-theater
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Design review
Before you hand an artifact over, review it against five dimensions and fix what falls short. This is a quality bar, not a performance: do the review, apply the fixes, and describe the outcome in ordinary prose.
The five dimensions
Judge the artifact you just produced from five angles. Each one owns its own scope; do not let a strength in one excuse a failure in another.
read as deliberate work rather than a template with the words swapped out?
- Craft — layout, hierarchy, spacing, alignment, and visual rhythm. Does it
the weakest claim, the thinnest section, the thing a sceptical reviewer would attack first.
- Critique — does it actually solve the user's stated problem? Look for
voice? A brand violation is a defect even when the result looks pleasant.
- Brand — does it follow the active design system's tokens, typography, and
on interactive controls and dialogs, keyboard reachability, sensible heading order.
- Accessibility — contrast ratios, touch-target sizes, focus rings, labels
phrasing and marketing padding both count as defects.
- Copy — is the text specific, readable, and free of filler? Placeholder
What to do with the findings
Record each concrete defect and fix it in the same turn. A finding you cannot fix is worth stating plainly, with the reason, so the user can decide.
Keep iterating while defects remain and you still have room to work. Stop when the artifact clears all five dimensions, or when further rounds stop producing real improvements — whichever comes first. Three passes is a sensible ceiling.
ODMAXDEVLOOP_ITERATIONS caps the outer plugin pipeline stage; it is not this review's round limit. A pipeline's critique.score signal is a scheduler-facing projection, not something you should write into your answer.
How to report it
Write the outcome the way you would write any other part of your answer: plain prose, in the user's language, saying what you checked, what you fixed, and anything you deliberately left alone.
Do not invent a structured review transcript, a scored panel, a cast of named reviewer personas, or any tag-based envelope around your answer. Do not write a critique.json file into the project. None of those are inputs to anything — they only add noise to the user's chat.
More skills from nexu-io/open-design
- Aarticle-magazineHuashu / huashu-md-html-inspired magazine article layout for turning Markdown or notes into a polished long-form HTML essay.
- Aaudio-jingleAudio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
- Aaudio-jingleAudio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
- Ablog-postA long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
- Ablog-postA long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
- Abuild-testRun the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
- Acard-twitterTwitter quote or data card designed to pair with a post.
- Acard-xiaohongshuXiaohongshu-style knowledge cards, arranged as a swipeable multi-card carousel.
- Aclinical-case-reportStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
- Aclinical-case-reportStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
- Acode-importRead an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
- Acodex-interactive-capability-mapTurn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.