Design rigor

The auto-fire skill that keeps generations on-brand, and the polish commands you opt into

Reva ships one monorepo-wide auto-fire skill that applies across the entire codebase — apps/* (production work) and prototypes/* (vibe-coding) alike. It gives every contributor a design-aware coding agent.

Auto-fire (always on)

SkillWhat it doesSource
reva-design-system-adherenceThe single design brain: tokens-only color, @reva/ui primitives over bespoke markup, correct component APIs, spacing/forms discipline, and the anti-slop taste bar (variance 4 / motion 5 / density 5). Plus the Creative Extension Protocol for proposing new components.Reva-original

The skill lives in .agents/skills/reva-*/ (committed source) with a symlink at .claude/skills/reva-* so Claude Code auto-discovers it. No setup steps required. When you clone the repo and have Claude Code installed, it's already wired.

Reference docs (loaded on demand)

reva-design-system-adherence references two on-demand docs vendored from Bencium's UX Designer skill:

  • references/accessibility.md — WCAG 2.1 AA, color contrast, keyboard navigation, screen reader semantics
  • references/responsive-design.md — breakpoints, touch targets, mobile/tablet adaptation

The agent loads them when the work touches their domain.

Explicit polish commands (you opt in)

After building a meaningful screen or flow, suggest one of these to the agent (or invoke yourself). The agent will not auto-run them — that's deliberate. Polish is something you should consciously decide to do.

  • /impeccable polish — fixes alignment, spacing, typography, color, interaction states
  • /impeccable critique — UX critique with persona-based testing
  • /impeccable audit — accessibility + performance check before showing to anyone

These come from the Impeccable skills vendored in .agents/skills/ (symlinked at .claude/skills/). No separate plugin install — they're already in the repo. See Agent skills for the full list.

Why these skills aren't just for prototypes

The same agent ships your production code in apps/*. A developer building a new Advisor Portal page has the exact same on-brand floor as anyone vibe-coding a prototype. Consistency is the priority — prototypes can be handed over to Claude Code for production build, so they should ship at production quality from the start.

On this page