design-rubriclisted

ONE-TIME-PER-PROJECT setup. Codifies the project's design system (Arutyunov IDS + Birman/Bureau Gorbunov) as machine-checkable criteria in design-contract.json at the project root. Future /contract invocations inherit from it; design-prototyper agent (invoked from /grill-with-docs or /build-loop) reads it before drawing. Use when starting the FIRST frontend feature for a project, when the design system changes (e.g. token rename), or when user says "design rubric", "codify the design system", "set up design contract", or invokes /design-rubric. Not for per-feature runs — re-run only when project-level design rules change.
createusernam/setup_project · ★ 0 · Web & Frontend · score 68

Install: claude install-skill createusernam/setup_project

# /design-rubric — Design System as Contract (Project-Level) ## Mandatory phase guard Before reading or writing `design-contract.json`, run `setup-pipeline guard 3` from the project root. If it fails, stop without creating, changing, or attesting any design artifact. Enter Phase 3 only through `setup-pipeline enter 3`; never change the ledger first and validate afterward. ## Why this skill exists Your design principles (Arutyunov IDS, Birman, UI copy) live in prose at `~/.claude/design-guidelines.md`, if you keep such a file. Prose is unenforceable. Neither the design-prototyper agent (drawing the mockup) nor the evaluator in `/build-loop` (grading the implementation) can mechanically check against prose. This skill **translates project-level design rules into machine-checkable criteria** in `design-contract.json` at the project root. It runs **ONCE PER PROJECT** — the artifact then lives forever, attested with sha256, until the design system itself changes. After this skill runs: - The **design-prototyper agent** (called from `/grill-with-docs` or `/build-loop` for UI features) reads `design-contract.json` BEFORE drawing the mockup, so the prototype already complies. - The **frontend-developer agent** (called from `/build-loop` generator phase) reads it during implementation. - The **evaluator** in `/build-loop` grades against it on every iteration via Playwright + grep. - Each per-feature `contract.json` inherits its criteria via `"inherits": ["design-contract.json"]`