Spec-driven engineering pod — six Claude Code skills that move a feature from spec scaffolding and research, through direction discovery and production design variants, into code, and out the other side via visual QA. Hard handoffs between skills prevent silent assumptions.
Six-skill engineering pod for the full lifecycle: scaffold specs, research thin specs, brainstorm direction, generate variants, implement, verify visually. Spec-driven, with hard handoffs between skills that prevent silent assumptions.
Coding specialist that consults locked specs and design comps before writing code, refuses to implement when feature decisions are still open (routing to /design-explore for direction-level decisions or /design-agent for variant-level decisions), and enforces token discipline + parser philosophy + a strict comment…
Generates production design variants in Pencil WITHIN A LOCKED DESIGN DIRECTION (post-direction-lock work — for direction discovery use /design-explore). Critiques variants against the project spec + embedded aesthetic frameworks, presents structured trade-off reports, supports critique-only mode (evaluate existing…
Creative exploration and design direction discovery — runs BEFORE specs are locked, or to challenge them when something feels off. Use /design-agent AFTER direction is locked for production variants. This skill helps find aesthetic direction, critiques screenshots/references, challenges locked decisions when the user…
Bootstrap the doc structure, design scaffolds, and CLAUDE.md a project needs before /design-explore, /design-agent, /code-agent, or /visual-qa can run — those companion skills hard-block on the artifacts created here. Use whenever the user starts a new project, says "set up specs / scaffold docs / create project…
Researches a thin, stale, or gap-ridden [FEATURE]-IDEAS.md and proposes a draft decision tree (page states) plus a list of adjacent gaps (chart shape, units, taxonomy entries, design-code drift, vague verbs, locked-but-undescribed decisions) — so that /code-agent, /visual-qa, or /design-agent can run without flying…
Automated visual QA for a running frontend — screenshots the real rendered UI at the project's breakpoints and checks it against the project's own spec (tokens, layout rules, design language) AND its sibling screens, not hardcoded assumptions. Standalone on any frontend project; learns the project profile from docs/…