Livery

The visual-craft lens for a frontend build — where the surface gets its color, type, depth, and motion. Use after seaworthy's build works, when establishing or auditing a visual language, or when a UI "looks off". The one shift: a polished interface is not a pile of hand-picked values — every visual value is a TOKEN derived from a small SYSTEM, and ad-hoc values are the entropy that makes a UI look amateur and impossible to re-theme. Taste picks the system; the system enforces it. Triggers on "color / theme / dark mode / oklch / contrast", "typography / font / type scale / spacing", "shadow / elevation / depth / border-radius", "gradient / icon / image", "animation / transition / motion / gesture / spring", "design system / design tokens", "make it look good / polished", "it looks off / cheap / inconsistent". The benchmark is a human nervous system, not a document, so taste is load-bearing and cannot be outsourced; the agent picks plausible-but-incoherent values and feels none of the wrongness.

mkdir -p ~/.claude/skills/livery
curl -L https://claudskills.com/skills/livery/SKILL.md \
  -o ~/.claude/skills/livery/SKILL.md

@misc{livery-2026,
  author    = {IamK77},
  title     = {Livery [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/livery/}
}