New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Architecture Review

by Donchitos in Donchitos/Claude-Code-Game-Studios

Traceability matrix mapping GDD requirements to ADRs. An agent skill from Donchitos/Claude-Code-Game-Studios.

MITAuto-check: notesDevelopment

Install Architecture Review

skills CLI
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill architecture-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Donchitos/Claude-Code-Game-Studios architecture-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/architecture-review .claude/skills/architecture-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architecture-review
GitHub stars
26k
Token cost
~1.5k tokens
SKILL.md length
773 words
Files
10 (incl. references)
Skills in repo
73
Repo updated
First seen
Licence
MIT

At a glance

Traceability matrix mapping GDD requirements to ADRs. An agent skill from Donchitos/Claude-Code-Game-Studios.

  • Works in 9 steps: Load Everything → Extract Technical Requirements from… → Build the Traceability Matrix → …
  • Tasks that involve Architecture decision records
  • SKILL.md covers Phase 1: Load Everything, Phase 2: Extract Technical…, Phase 3: Build the… and Phase 4: Cross-ADR Conflict…, plus 7 more sections
  • Calls bash

What it does

Architecture Review is an agent skill from Donchitos/Claude-Code-Game-Studios. Traceability matrix mapping GDD requirements to ADRs. Finds gaps, cross-ADR conflicts, engine compatibility. PASS/CONCERNS/NOT ASSESSED/FAIL.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/1-load.md`, `references/2-extract-requirements.md` and `references/3-traceability.md`).

It sits in Development, covering Architecture decision records, Game design and Software architecture. The repository describes itself as: Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy. The licence is MIT.

When your agent uses it

  • Tasks that involve Architecture decision records
  • Tasks that involve Game design
  • Tasks that involve Software architecture

Example prompts

  • “/architecture-review”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash, Write, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/architecture-review/../../hooks/yaml-helper.sh" resolve_config *)

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Load Everything
  2. Extract Technical Requirements from Every GDD
  3. Build the Traceability Matrix
  4. Cross-ADR Conflict Detection
  5. Engine Compatibility Cross-Check
  6. Architecture Document Coverage
  7. Output the Review Report
  8. Write and Update Traceability Index
  9. Handoff

What it can do on your machine

Read from SKILL.md and the folder at commit be8993b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash
    • Write
    • Agent
    • AskUserQuestion
    • Bash(bash "*/.claude/skills/architecture-review/../../hooks/yaml-helper.sh" resolve_config *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architecture Review loads about 1.5k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 773 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash, Write, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/architecture-revi

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Donchitos/Claude-Code-Game-Studios at commit be8993b, republished under its MIT licence (© Donchitos). 773 words, ~1,521 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-review/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
architecture-review
description
Traceability matrix mapping GDD requirements to ADRs. Finds gaps, cross-ADR conflicts, engine compatibility. PASS/CONCERNS/NOT ASSESSED/FAIL.
allowed-tools
Read, Glob, Grep, Bash, Write, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/architecture-review/../../hooks/yaml-helper.sh" resolve_config *)
argument-hint
[focus: full | coverage | consistency | engine | single-gdd path/to/gdd.md]
user-invocable
true
model
opus

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow

Architecture Review

The architecture review validates that the complete body of architectural decisions covers all game design requirements, is internally consistent, and correctly targets the project's pinned engine version. It is the quality gate between Technical Setup and Pre-Production.

Argument modes:

  • No argument / full: Full review — all phases
  • coverage: Traceability only — which GDD requirements have no ADR
  • consistency: Cross-ADR conflict detection only
  • engine: Engine compatibility audit only
  • single-gdd [path]: Review architecture coverage for one specific GDD
  • rtm: Requirements Traceability Matrix — extends the standard matrix to include story file paths and test file paths; outputs docs/architecture/requirements-traceability.md with the full GDD requirement → ADR → Story → Test chain. Use in Production phase when stories and tests exist.

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).

workflow (see .claude/docs/workflow-modes.md):

  • full — full traceability matrix across all GDDs and all ADRs.
  • standard — reduced scope: architecture doc + critical ADRs only.
  • minimal — not applicable (no architecture doc required).

Phase 1: Load Everything

Read references/1-load.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 2: Extract Technical Requirements from Every GDD

Read references/2-extract-requirements.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 3: Build the Traceability Matrix

Read references/3-traceability.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 4: Cross-ADR Conflict Detection

Read references/4-conflicts.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 5: Engine Compatibility Cross-Check

Read references/5-engine.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 6: Architecture Document Coverage

Read references/6-document-coverage.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 7: Output the Review Report

Read references/7-report.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 8: Write and Update Traceability Index

Read references/8-write.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 9: Handoff

Read references/9-handoff.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Show full SKILL.md (308 more words)Show less

Error Recovery Protocol

First, verify the artifact. If the return contract named a path, check the path exists before treating the phase as done — a named artifact that is not on disk is a failed phase, however fluent the response reads. An agent can burn a full phase and return a plausible preamble having written nothing, which is neither BLOCKED nor an error nor "fails to complete", so the trigger below never fires. Resume it naming the unmet contract; the context is usually still there.

If any spawned agent returns BLOCKED, errors, or fails to complete: surface it immediately, don't proceed past a dependency it blocks, and always produce a partial report (retry scope here = fewer GDDs / single-system). Full procedure: .claude/docs/error-recovery-protocol.md.

Collaborative Protocol

Applies in collaborative mode (the default). For guided and autonomous modes, see .claude/docs/automation-modes.md — the rules below describe what collaborative mode requires, not universal behavior.

  1. Read silently — do not narrate every file read
  2. Show the matrix — present the full traceability matrix before any write approval; let the user see the state
  3. Don't guess — if a requirement is ambiguous, ask: "Is [X] a technical requirement or a design preference?"
  4. Draft before approval — always show the content that will be written (the report, the updated ADR section, the systems-index row) inline in the conversation before requesting approval. Never ask to write something the user has not yet seen.
  5. Use AskUserQuestion for write approvals — plain text "May I?" is not sufficient. Use the structured tool with labeled options [A]/[B]/[C] so the user can choose between "write now", "show full draft first", and "not yet". Multi-file changesets must list every file and what changes, then ask once with grouped options — not a separate plain-text question per file.
  6. Non-blocking — the verdict is advisory; the user decides whether to continue despite CONCERNS or even FAIL findings

© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in .claude/skills/architecture-review of Donchitos/Claude-Code-Game-Studios.

  • SKILL.md
  • references/1-load.md
  • references/2-extract-requirements.md
  • references/3-traceability.md
  • references/4-conflicts.md
  • references/5-engine.md
  • references/6-document-coverage.md
  • references/7-report.md
  • references/8-write.md
  • references/9-handoff.md

Open the folder on GitHubat commit be8993b

Compare with similar skills

Architecture Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architecture Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Review this skillDonchitos/Claude-Code-Game-Studios26k—~1.5kAutomated safety check: NotesMIT
Create Vibe Featuremistralai/mistral-vibe5.1k—~1.4kAutomated safety check: PassApache-2.0
Architecture Decisions and ADRsfirst-fluke/oh-my-agent1.3k—~2.6kAutomated safety check: PassMIT
System Architecture DesignerJeffallan/claude-skills12k—~1.2kAutomated safety check: PassMIT
Light System DesignLight0305/Light-skills640—~3.6kAutomated safety check: PassMIT
Architecture DesignerAratKruglik/claude-laravel1551 repos~895Automated safety check: PassNone

Similar skills

  • Create Vibe Feature

    mistralai/mistral-vibe

    Official

    Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.

    5.1k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Architecture Decisions and ADRs

    first-fluke/oh-my-agent

    Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.

    1.3k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • System Architecture Designer

    Jeffallan/claude-skills

    Guides system architecture design end to end: gathering requirements, matching them to a pattern, documenting trade-offs with ADRs, and reviewing.

    12k GitHub stars~1.2k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Light System Design

    Light0305/Light-skills

    Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.

    640 GitHub stars~3.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Architecture Designer

    AratKruglik/claude-laravel

    A skill your agent uses when designing new system architecture, reviewing existing designs, or making architectural decisions.

    155 GitHub starsUsed in 1 repo~895 tokens
    DevelopmentAuto-check passed

  • Architecture Decision Record Writer

    dralgorhythm/claude-agentic-framework

    Writes Architecture Decision Records with title, status, context, decision, rationale and consequences for significant technical choices, kept short and numbered.

    125 GitHub stars~529 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from Donchitos/Claude-Code-Game-Studios

All 73 skills in this repo

  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Dev Story

    Donchitos/Claude-Code-Game-Studios

    Implement a story: ADR guidelines, right programmer agent, code plus test.

    26k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check: notes

  • Game Asset Audit

    Donchitos/Claude-Code-Game-Studios

    Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.

    26k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Game Asset Spec Writer

    Donchitos/Claude-Code-Game-Studios

    Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.

    26k GitHub stars~5k tokensUpdated 2 days ago
    Auto-check passed

  • Game Balance Check

    Donchitos/Claude-Code-Game-Studios

    Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.

    26k GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

  • Structured Bug Reports

    Donchitos/Claude-Code-Game-Studios

    Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

    26k GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check: notes

Categories

Questions about Architecture Review

What does Architecture Review do?

Traceability matrix mapping GDD requirements to ADRs. An agent skill from Donchitos/Claude-Code-Game-Studios. Architecture Review is an agent skill from Donchitos/Claude-Code-Game-Studios. Traceability matrix mapping GDD requirements to ADRs.

When should I use Architecture Review?

Architecture Review fits situations like: tasks that involve Architecture decision records; tasks that involve Game design; tasks that involve Software architecture.

How do I install Architecture Review in Claude Code?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill architecture-review -a claude-code`. Or copy the skill folder (.claude/skills/architecture-review in Donchitos/Claude-Code-Game-Studios) into .claude/skills/architecture-review in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Review in Codex?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill architecture-review -a codex`. Or copy the skill folder (.claude/skills/architecture-review in Donchitos/Claude-Code-Game-Studios) into .agents/skills/architecture-review in your project. Codex loads it when a task matches its description.

Can I use Architecture Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill architecture-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-review, .gemini/skills/architecture-review, .github/skills/architecture-review and .opencode/skills/architecture-review in your project.

What does Architecture Review need to run?

Going by SKILL.md and its folder, Architecture Review needs the command-line tools its instructions call (bash). Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash, Write, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/architecture-review/../../hooks/yaml-helper.sh" resolve_config *).

Does Architecture Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architecture Review safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Architecture Review use?

Architecture Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architecture Review use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.7k tokens, read only when the agent opens those files.

What are the alternatives to Architecture Review?

Skills that share tags, products or a category with Architecture Review: Create Vibe Feature (mistralai/mistral-vibe, 5.1k stars), Architecture Decisions and ADRs (first-fluke/oh-my-agent, 1.3k stars), System Architecture Designer (Jeffallan/claude-skills, 12k stars) and Light System Design (Light0305/Light-skills, 640 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Review?

Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 26,031 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on October 8, 2026.

Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.