Critique
A structured design-critique protocol that turns "looks off" into ranked, concrete changes with exact values (px, ms, curves, colors) — never vibes. Use this skill whenever evaluating any rendered visual: reviewing a screenshot, judging your own just-built UI/chart/slide/game screen before shipping, responding to "does this look good?", "review this design", "why does this feel off?", "roast my l…
Install
$ agentstack add skill-jangles-byte-atelier-critique ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jangles-byte-atelier-critique) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Critique
A critique is an ordered list of changes with exact values, produced by evaluating a real render against a fixed rubric. "Feels unbalanced" is not critique; "increase section gap 32px→64px so the pricing table separates from the hero" is.
Workflow
- Get a real render. Screenshot the running artifact (browser preview, simulator,
plot output, game capture) — never critique source code or imagination. If anything moves, a still is not a render. Capture the motion and watch it: ``bash ../motion/scripts/capture-motion.py index.html --out review.gif --duration 1200 `` Then interact with it directly — hover, open and close, mash the trigger — because interruption bugs only appear under abuse.
- Inventory — one paragraph of what is objectively on screen (elements, reading
order as encountered, palette, faces in use). Forces looking before judging.
- Score the rubric — eight dimensions, 1–5 each, using
[references/rubric.md](references/rubric.md). Cite evidence per score.
- Write the change list — every scored weakness becomes a change in the exact
format of [references/change-format.md](references/change-format.md): ranked by impact, each with location, current value → new value, and the principle it serves. 3 changes minimum, 10 maximum; past 10, ship the top 10 and re-critique after.
- Apply and re-render. A critique that isn't applied and re-verified is a memo.
Iterate until the weakest rubric dimension scores ≥ 4 or the user stops you.
Which reference to load
| Situation | Load | |---|---| | Scoring any render; the eight dimensions with anchors | references/rubric.md | | Writing the output; worked example of a full critique | references/change-format.md |
Rules
- Judge against the design philosophy first (does it keep its own promises?), the
rubric second. If no philosophy exists, write a one-line inferred intent and say so.
- Diagnose over prescribe when uncertain of intent — but never emit a finding without
a proposed exact value. Uncertainty goes in a parenthetical, not in vagueness.
- Strengths get one sentence, findings get the rest. Flattery is not calibration.
- Accessibility findings (contrast, motion, hit targets) always rank above aesthetic
findings, whatever their scores.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jangles-byte
- Source: jangles-byte/atelier
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.