Run the spec-driven loop for a dev-challenge exercise — read the spec and its acceptance criteria, clarify ambiguity, plan, build, verify with the harness, iterate on failing criteria. Use whenever someone is working through a challenge from specs/challenges/, mentions a challenge id like backend-05-balance or…
Compare an implemented UI against the dev-challenge design tokens and mockups — colours, type scale, spacing, layout and the required testids. Use when someone asks "does this match the design", wants a design review of a screen they built, is working on a web or mobile challenge's visual fidelity, or asks which…
Add or change a challenge in the dev-challenge spec layer — frontmatter, acceptance criteria with stable IDs, the matching harness test, and the validation that keeps them in sync. Use when someone wants to add a new challenge or track, edit an existing spec or acceptance criterion, change API behaviour that a spec…