Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/create-architecture
Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
Passed 5 of 13 test cases with the skill, and 2 of 13 without it.
and 6 more in the full report
7 fixed2 passed either way11 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/11/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are configuring our project settings in project.yaml. We want the architecture workflow to include all sections (layers, data flow, API boundaries), but we want every section written concisely with layer diagrams and decision bullet points rather than lengthy prose essays. Which configuration key and value controls this?
| Checked | Without skill | With skill |
|---|---|---|
| Sets docs.density to terse to enforce layer diagrams and decision bullets without essay prose. | Missed | Passed |
| Maintains standard architecture sections while reducing per-section depth. | Passed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,docs.density
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
This skill produces docs/architecture/architecture.md — the master architecture
document that translates all approved GDDs into a concrete technical blueprint.
It sits between design and implementation, and must exist before sprint planning begins.
Distinct from /architecture-decision: ADRs record individual point decisions.
This skill creates the whole-system blueprint that gives ADRs their context.
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
docs.density — it controls per-section depth, where workflow
controls which sections exist. modes.rigor sets both together; set
docs.density explicitly to vary depth alone: terse (the default, via rigor: minimal) = layer diagrams + decision bullets,
no essays; balanced = diagrams + paragraph explanations of layer choices
(rigor: standard); thorough = full prose with rationale, trade-offs, and alternatives
considered per layer. Apply it to every section you author.
workflow (see .claude/docs/workflow-modes.md):
full — full architecture: all layers, module ownership, data flow, API
boundaries, full ADR audit.standard — simplified: system layer map + critical ADR list only.minimal — not required. Can still be run voluntarily.Argument modes:
full: Full guided walkthrough — all sections, start to finishlayers: Focus on the system layer diagram onlydata-flow: Focus on data flow between modules onlyapi-boundaries: Focus on API boundary definitions onlyadr-audit: Audit existing ADRs for engine compatibility gaps onlytest cases passed, vs 2 / 13 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.