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 pproenca/dot-skills --skill design-reviewgit clone --depth 1 https://github.com/pproenca/dot-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/pproenca/dot-skills/design-review)<a href="https://agentmods.dev/skills/pproenca/dot-skills/design-review"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/design-review.svg" alt="Measured on agentmods" 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.00200 | $0.03217 |
| Opus 5 | $0.00100 | $0.01608 |
| Sonnet 5 | $0.00040 | $0.00643 |
| Haiku 4.5 | $0.00020 | $0.00322 |
Grade A, and why
design-review 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 8d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review
Conduct a design review of UI code and return a prioritised critique. The reviewer's lens is Emil Kowalski's design-engineering philosophy — taste is the differentiator; the unseen details compound; show the eye where to look — made concrete with the heuristics from Refactoring UI, WCAG, and MDN.
This is a read-only review skill: it diagnoses and proposes fixes; it does not rewrite the codebase. Each finding names the wrong default the code fell into, the exact fix, and why it matters.
When to Apply
- The user asks to "review this UI", run a "design review", or "critique" a component, screen, or page.
- The user says the output "looks off", "looks AI-generated", "looks like a wireframe", or "feels generic", and wants to know why.
- A PR touches CSS/JSX/Tailwind and the user wants design feedback before merge.
- The user wants to raise the visual polish or accessibility of an existing interface.
Not for building UI from scratch (use web-taste) or for the exhaustive animation rule set (use emilkowal-animations).
How to Run the Review
Two modes. A static review reads the code and is the default. A runtime review additionally drives a real browser to measure what the code can't show — animation timing and dropped frames, layout shift, the live focus order and accessibility tree, and the multi-page flow clicked through end to end. Switch to runtime whenever the verdict turns on rendered behaviour (the motion-, interact-, and flow- categories), per runtime-capture.md.
- Orient — the 0.5-second test. Before reading line by line, picture the rendered screen. Where does the eye land first? Is there a single focal point, or does everything carry equal weight? This frames which categories matter most for this UI.
- Pass the categories in priority order (table below). For each decision the code makes, read the matching reference file and check the code against it. Visual hierarchy and spacing are where the largest, most frequent problems live — start there.
- For multi-page or interaction-driven UX, walk it in a browser. When the brief is a flow ("review this onboarding") or the issue is felt in motion (jank, blank route flashes, lost focus), capture runtime evidence per runtime-capture.md so the Before column is a measured value, not a guess.
- Record each problem as a finding with a Before (the exact code or measurement), an After (the concrete fix), a Why (the principle), and a context-assigned Severity.
- Close with a verdict: the top 3 fixes, ranked by impact, so the author knows what to change first.
What ships with it
46 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.
- AGENTS.md 7.8 KB
- assets/templates/_template.md 997 B
- metadata.json 2.0 KB
- references/_runtime-capture.md 7.4 KB
- references/_sections.md 4.1 KB
- references/access-name-icon-controls.md 648 B
- references/access-respect-reduced-motion.md 741 B
- references/access-semantic-elements.md 850 B
- references/color-avoid-pure-black.md 712 B
- references/color-hsl-scales.md 682 B
- references/color-limit-accents.md 701 B
- references/color-meet-contrast.md 744 B
- references/color-not-only-signal.md 829 B
- references/flow-consistent-shell.md 962 B
- references/flow-entry-point-integrity.md 1.1 KB
- references/flow-preserve-state-on-nav.md 1003 B
- references/flow-wayfinding.md 888 B
- references/hier-emphasis-color-weight.md 925 B
- references/hier-one-focal-point.md 891 B
- references/hier-one-primary-action.md 798 B
- references/hier-replace-borders-with-space.md 878 B
- references/hier-values-over-labels.md 682 B
- references/interact-bridge-route-transitions.md 962 B
- references/interact-feedback-spans-async.md 1.1 KB
- references/interact-move-focus-on-navigation.md 1.1 KB
- references/motion-ease-out-custom.md 893 B
- references/motion-enter-origin-scale.md 1.1 KB
- references/motion-needs-purpose.md 830 B
- references/motion-transform-opacity-only.md 796 B
- references/motion-under-300ms.md 667 B
- references/resp-fluid-not-fixed.md 845 B
- references/resp-gate-hover.md 772 B
- references/resp-touch-target-size.md 669 B
- references/space-constrain-measure.md 578 B
- references/space-proximity-groups.md 715 B
- references/space-start-generous.md 616 B
- references/space-use-a-scale.md 770 B
- references/state-design-all-states.md 843 B
- references/state-empty-state.md 860 B
- references/state-focus-visible.md 738 B
- references/state-press-feedback.md 657 B
- references/type-left-align-prose.md 818 B
- references/type-limit-line-length.md 694 B
- references/type-line-height-by-size.md 616 B
- references/type-modular-scale.md 815 B
- references/type-readable-body-size.md 603 B
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.
- 8d ago First seen · 180 lines · 200 tokens per session scan A 2fb70c56509c
design-review is a skill published in the GitHub repository pproenca/dot-skills (203 stars, last pushed 23d ago), licensed MIT. It adds 200 tokens to every session and 3,217 once invoked, about $0.0010 per session on Opus 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…