What is ui-aesthetic-review?

A review guide for judging the visual craft of an implemented user interface. It looks beyond whether the interface works to assess details such as hierarchy, spacing, and whether the result feels intentionally designed.

Use it after building an interface to critique its visual quality and find details that need refinement. It is not intended for checking exact matching to a design file or compliance with style tokens.

It helps identify generic or unfinished-looking choices that ordinary bug checks and design-rule checks may miss.

ui-aesthetic-review — Skill for Claude Code by volomydyr

Install

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.

Any agent

npx skills add volomydyr/design-engineer-plugin --skill ui-aesthetic-review

Clone the repo

git clone --depth 1 https://github.com/volomydyr/design-engineer-plugin

Made for: Claude Code.

Or install design-engineer, the plugin that ships this one along with the rest of its 57 skills, 11 commands, 10 agents, 6 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/ui-aesthetic-review/github.svg)](https://agentmods.dev/skills/volomydyr/design-engineer-plugin/ui-aesthetic-review)

Your own site

<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/ui-aesthetic-review"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/ui-aesthetic-review/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/ui-aesthetic-review"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/ui-aesthetic-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,147 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00066	$0.03147
Opus 5	$0.00033	$0.01573
Sonnet 5	$0.00013	$0.00629
Haiku 4.5	$0.00007	$0.00315

Measured 11d ago against content hash 9ca210746819, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

ui-aesthetic-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 11d 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.

skills/ui-aesthetic-review/SKILL.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Critique

Why This Matters

There is a distance between correct and crafted. Correct means the layout holds, the grid aligns, the colors do not clash. Crafted means someone cared about every decision down to the last pixel. You can feel the difference immediately – the way you tell a hand-thrown mug from an injection-molded one. Both hold coffee. One has presence.

Your first output lives in correct. This skill pulls it toward crafted.

This is not about finding bugs or catching design system violations – that is what ui-design-to-code-qa does. This skill asks a different question: "Would a design lead put their name on this?"

Good taste is trained, not innate. Develop it by surrounding yourself with great work, thinking deeply about why something feels right, and studying the best interfaces with curiosity – reverse-engineer animations, inspect spacing, understand hierarchy.

"All those unseen details combine to produce something that's just stunning, like a thousand barely audible voices all singing in tune." – Paul Graham. Beauty is underutilized in software. Most teams stop at correct. Craft is leverage.

Interaction Method

If AskUserQuestion is available, use it for all prompts below.

If not, present each question as a numbered list and wait for a reply before proceeding. For multiSelect questions, accept comma-separated numbers (e.g. 1, 3). Never skip or auto-answer without explicit user consent.

Step 1: Determine Critique Scope

question: "What would you like to critique?"
header: "Scope"
options:
  - label: "Full page or screen"
    description: "Critique an entire page layout, composition, and all elements"
  - label: "Specific component"
    description: "Deep critique of a single component – card, form, nav, etc."
  - label: "Multi-screen flow"
    description: "Critique consistency and craft across a user journey"
  - label: "Overall product feel"
    description: "High-level critique of the product's visual identity and coherence"

Read the full file on GitHub · 244 lines

Files

What ships with it

14 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.

Changes

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.

11d ago First seen · 244 lines · 66 tokens per session scan A 9ca210746819

Subscribe to this mod's changes

ui-aesthetic-review is a skill published in the GitHub repository volomydyr/design-engineer-plugin (20 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 3,147 once invoked, about $0.0003 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.

Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

ui-aesthetic-review