agentleFS
Sign inStart free
chuanglibschuanglibs/Claude-Code-Game-Studios-Codex/.agents/skills/studio-architecture-review/SKILL.md

studio-architecture-review

Skill1 starsChanged 59 days agoMITView on GitHub

Game studio workflow: Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the Codex runtime guide.

    line 10
  2. Distinctive:

    Read the shared workflow and follow its phases using that guide's translations.

    line 11
  3. Very specific:

    Use the technical-director role from its shared brief.

    line 12
  4. Very specific:

    Use text following $studio-architecture-review as the workflow arguments.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated by scripts/sync_codex.py; do not edit. -->

Studio: architecture-review

  1. Read the Codex runtime guide.
  2. Read the shared workflow and follow its phases using that guide's translations. Read referenced documents only when the current phase needs them.
  3. Use the technical-director role from its shared brief. For delegated work, its native Codex name is studio-technical-director.

Use text following $studio-architecture-review as the workflow arguments. Translate references to /architecture-review into $studio-architecture-review; translate other studio commands the same way. Do not invoke Claude-only tools or treat its frontmatter as Codex settings.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free