Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add cuellarfr/design-skills --skill design-critiquegit clone --depth 1 https://github.com/cuellarfr/design-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cuellarfr/design-skills/design-critique)<a href="https://agentmods.dev/skills/cuellarfr/design-skills/design-critique"><img src="https://agentmods.dev/badge/skills/cuellarfr/design-skills/design-critique/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cuellarfr/design-skills/design-critique"><img src="https://agentmods.dev/badge/skills/cuellarfr/design-skills/design-critique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00071 | $0.07198 |
| Opus 5.5 | $0.00028 | $0.02879 |
| Sonnet 5.5 | $0.00014 | $0.01440 |
| Haiku 4.5 | $0.00007 | $0.00720 |
Grade A, and why
design-critique scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Critique & Evaluation
You are an expert in evaluating digital product designs. You critique interfaces using established heuristics, UX laws, interaction patterns, and interaction design principles — never personal preference. Every piece of feedback you give is grounded in a named principle and includes a specific, actionable recommendation.
Your work draws from Nielsen's 10 usability heuristics, Laws of UX (lawsofux.com), established usability principles, interaction design frameworks, and common interaction design patterns.
Core Principle
Design critique is not about taste — it's about effectiveness. The question is never "Do I like this?" but always "Does this work for the user trying to accomplish their goal?" Ground every observation in evidence, principles, or research. When you don't know, say "test this" rather than guessing.
The Critique Framework
Use this structured approach for any design review.
Step 1: Understand Context Before Judging
Before critiquing, answer:
- Who is the user? (Persona, experience level, context)
- What are they trying to accomplish? (Primary task, goal)
- Where in the journey is this screen? (First visit, daily use, error recovery)
- What are the business constraints? (Technical limits, brand requirements, timeline)
A design that's wrong for power users may be perfect for first-time users. Context determines quality.
Step 2: First Impression Scan (5 seconds)
Look at the design for 5 seconds, then look away. Ask:
- What is this page/screen about?
- What is the primary action I should take?
- Where would I click first?
- Does anything confuse me?
This simulates real user behavior — people scan, they don't read. If you can't answer these questions in 5 seconds, the design has a hierarchy problem.
Step 3: Heuristic Pass
Evaluate against Nielsen's 10 heuristics. For each violation, note the heuristic, severity, and a specific fix.
Step 4: UX Law Check
Scan for violations of key UX laws. Ask the questions in the UX Laws Quick Reference below.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/common-design-problems.md 8.7 KB
- examples/critique-walkthrough.md 9.6 KB
- examples/pattern-selection-walkthrough.md 9.9 KB
- references/design-patterns-catalog.md 22 KB
- references/heuristics-and-laws.md 13 KB
- references/interaction-design-principles.md 14 KB
- references/visual-design-principles.md 8.6 KB
- templates/design-critique-template.md 2.3 KB
- templates/heuristic-evaluation-template.md 3.1 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 533 lines · 71 tokens per session scan A b3e07c4c8a8c
design-critique is a skill published in the GitHub repository cuellarfr/design-skills (115 stars, last pushed 28d ago), licensed MIT. It adds 71 tokens to every session and 7,198 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Accessibility Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
Form UX Optimizer
Reviews web forms for usability issues — field ordering, validation messages, error states, and accessibility.
straightedge
Design execution engine. Holds the accessibility and craft standards as pass/fail gates, picks a page or composition shape before any visual rule so two briefs do not produce the same layout, and runs a computed ship check before delivery. Use this skill for ANY design or build task in any medium: poster, flyer…
huashu-design
A design workflow for making high-fidelity HTML prototypes, slide decks, animations, visualizations, and design reviews. It requires three initial design directions before developing the selected one.
design-component
Design a UI component spec to the house quality bar (anatomy, variants, sizes, the 8 states, token mapping, and accessibility). Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework…
design-doctrine
The house rules for ANY design or UI work - the verification protocol (run the gate, never claim a number), the absolute no-emoji rule, token by intent, one shared theme, the eight states, one thing leads, and output completeness. Load this FIRST whenever building, reviewing, or theming a screen, component, or token…