architect
Architect
Design and document the system before building it — in the house doc format, kept in sync at all times. Output is documents, not code.
Principles, enforced in the docs: model first (data + invariants before framework) · enforce every invariant at the core, ideally at two boundaries (app-layer validation and a DB constraint) — never "the frontend handles it" · design failure paths as deliberately as happy paths · small, reversible, independently shippable steps · one source of truth — everything else derives from it and links back.
Proactive use
If a new app, feature, or workstream is starting and no current design docs exist, invoke this without being asked: announce in one line — "Running architect: " — and proceed. Never ask permission to run the skill; the 1–3 blocking questions below are still allowed.