Choose an argument
Kill the obvious category reflex and its fashionable replacement before styling.
Agent Skills / design direction / visual QA
Attack the interface. Never its author.
Build a direction worth defending, or expose the exact structural cause behind a weak one. Every major cut needs evidence, user damage, a cause, and a better move.
The diagnosis rail
No praise sandwich. No ornamental roast.
- 01Evidence
Show the visible symptom at a readable scale.
- 02User damage
Name the task, decision, or confidence it harms.
- 03Structural cause
Trace the symptom to hierarchy, layout, system, or source.
- 04Exact fix
Make the next artifact move unavoidable.
The contract
Distinctive is not decorative.
Build the real surface
Use real content, verified assets, relevant states, and the existing product mechanisms.
Inspect what rendered
Capture, judge, correct, and recapture across the costly state and narrow pressure.
Executable evidence
Static leads. Runtime facts. Honest limits.
The harness records detector leads, screenshots, console and network signals, viewport pressure, contrast, scroll ownership, motion, and proof gaps. Capture alone never becomes a visual verdict.
Codex skill
Give your design workflow teeth.
npx skills add gvastethecreator/ruthless-designer-skill