القائمة
Author project-level design documentation — architecture, data models, API contracts, user journeys, glossaries, and decision records (ADRs). For per-feature design, use /genesis-feature.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Design |
| description | Author project-level design documentation — architecture, data models, API contracts, user journeys, glossaries, and decision records (ADRs). For per-feature design, use /genesis-feature. |
| argument-hint | <doc-type> [name] [--update|--fresh] |
Author project-level design documentation. This is not a per-feature command — feature design belongs to /genesis-feature. Runs any time after the constitution exists.
Hard gate: refuses if no constitution exists. If asked for feature <name>, redirect to /genesis-feature.
.genesis/discovery/context.md.genesis/project-state.md.genesis/design/--update in place, --fresh to recreate, else ask (default --update).project-state.md.| Type | Path |
|---|---|
overview | .genesis/design/overview.md |
architecture | .genesis/design/technical/architecture.md |
data-model | .genesis/design/technical/data-model.md |
api-contracts | .genesis/design/technical/api-contracts.md |
integrations | .genesis/design/technical/integrations.md |
journey <name> | .genesis/design/user-journeys/<name>.md |
system <name> | .genesis/design/systems/<name>.md |
decision <name> | .genesis/design/decisions/<name>.md (ADR) |
glossary | .genesis/design/glossary.md |
content-map | .genesis/design/content-map.md |
- "design overview"
- "write the architecture doc"
- "create an ADR"
- "document a user journey"
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.