Calm ui audit

Skill yiyaw-lab/agent-armor/calm-ui-audit

Armor for coding agents: a playbook of Claude Code skills that make an agent prove its work, not describe it.

Install

npx -y skills add yiyaw-lab/agent-armor --skill calm-ui-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audits UI for prototype tells and applies calm Design Covenant fixes (subtraction-first, token tweaks, ≤3 CSS wins). Use when the user says the app feels primitive, prototype, unpolished, or asks for design polish, empty states, or Cursor/Linear-level UI density.

SKILL.md

2.7 KB, as published. Nobody here has run it

Calm UI Audit

Goal

Move one screen from "internal tool" to "shippable product feel" in one session — without a redesign, new dashboard, or feature creep.

Reference bar

Reference	Borrow
Cursor	Calm density, muted chrome, status-not-toast
Linear	Typography hierarchy, tight empty states
Notion	Plain-language empty copy, soft borders

Workflow

Scope one surface — user picks or infer from open files (one panel/page, not whole app).
List prototype tells — aim for ≥5 real tells, up to 10. Specific elements only, e.g. "mixed padding on cards (p-2 vs p-4)", "headers same weight as body", "empty state is single word 'Empty'". No vague "looks bad". Stop at 5 if the surface is already tight; do not pad with filler.
Optional DESIGN-NOTES.md (≤1 page) — only when the user wants to keep an audit artifact on disk:
- Spacing scale (4/8/12/16/24)
- Type scale (10/12/13/14px roles)
- Muted text rule (primary / secondary / tertiary)
- One accent usage rule
Apply ≤3 CSS-only wins (total diff <50 lines):
- Prefer: remove borders, unify radius, fix empty state copy, reduce font weights
- Use the project's existing spacing/type tokens — do not invent a parallel scale
- Avoid: new components, animations, glow, badge stacks, architecture refactors in the same pass
Verify — no new notification toasts, KPI tiles, or fifth navigation items.

Design Covenant (hard rejects)

Do not add: notification center, analytics widgets, prompt libraries, graph theater, engagement bait, red error theater in non-error feeds, simultaneous map + map (dual SVG).

Do not violate: one primary ask per screen, progressive disclosure, calm copy.

Continuum-specific

If repo is Continuum, read docs/brief/continuum-design-brief.md and docs/brief/surface-design-prd.md §2 before editing. Match existing tokens in src/index.css and src/lib/themes/.

Output template

# UI audit — [surface name]

## Prototype tells (≥5, up to 10)
1. ...

## Quick wins applied
- [file:line] — ...

## Deferred (needs product call)
- ...

Adversarial self-check

Did I subtract more than I added?
Are all listed tells actionable (file/element named)?
At least 5 real tells (not padded to hit 10)?
Under 50 lines of CSS changed?
Empty states use calm prose, not "No data"?