alterlab-ieu/alterlab_gameforge

1. What this repository is

- This is not a game app or engine plugin; it is a prompt/skill toolkit for Claude Code and Claude Projects.

- The repository packages 34 production-grade game-development skills as Markdown files, plus shared references, templates, hooks, starter configs, and CI validation.

2. Top-level orchestration boundary

- CLAUDE.md is the main routing/config entry point for the repo.

- It defines how Claude should interpret the repository and ties together the skill system, project conventions, and contribution rules.

- For a diagram, treat this as the central control plane that points to all other content layers.

3. Primary content subsystem: skills

- skills/ is the core product surface.

- It is split into:

- skills/agents/ — 11 studio-role skills such as Producer, Designer, QA Lead, Technical Director, etc.

- skills/workflows/ — 20 process skills such as Game Start, Brainstorm, Code Review, Sprint Plan, Launch, Playtest, Balance Check, CI Pipeline, and GDD Author.

- skills/engine-specialists/ — 3 engine-specific skills for Godot, Unity, and Unreal.

- Each skill is a standalone .md prompt artifact, designed to be loaded into Claude and activated by intent.

4. How the skills are organized conceptually

- The skills model a virtual game studio plus workflow automation plus engine specialization.

- The architecture boundary is important: the repo is intentionally engine-agnostic at the core, with engine-specific guidance isolated into specialist skills and starter configs.

- This makes the skill set reusable across different game stacks.

5. Shared knowledge base

- docs/ contains the reference layer used by multiple skills.

- It includes governance, workflow guidance, coding standards, collaboration protocols, genre/spec docs, MCP integration guidance, and FAQs.

- In the architecture, this is the common “knowledge substrate” that skills consult rather than duplicating content.

6. Genre packs as consumable domain libraries

- genre-packs/ contains reusable genre-specific design references, not standalone skills.

- Current packs are:

- narrative/

- roguelike/

- These enrich workflows like Brainstorm, Designer, Balance Check, and GDD Author with genre patterns, balance models, and example references.

7. Template subsystem

- templates/ provides the output artifacts that skills are meant to produce or fill in.

- Examples include game design documents, sprint plans, post-mortems, accessibility audits, release checklists, economy models, and systems indexes.

- In diagram terms, this is the output contract layer: skills generate structured artifacts from these templates.

8. Starter configurations for real projects

- starters/ contains bootstrap config for Claude-enabled game projects.

- There is a shared base config in starters/claude-config/ and engine-specific additions for:

- Godot

- Unity

- Unreal

- These are the handoff boundary between this repository and an actual game codebase.

9. Lifecycle hooks and operational automation

- hooks/ contains session and validation scripts such as session start/stop, compact handling, commit validation, and logging.

- These hooks enforce workflow discipline around Claude sessions and repository changes.

- They function as operational glue, not end-user content.

10. Validation and release pipeline

- scripts/validate.sh and .github/workflows/validate-skills.yml form the quality gate.

- The repo advertises automated validation of skill structure and content consistency, making the Markdown-based skill system safe to maintain at scale.

- marketplace.json and package.json provide repo metadata and distribution/tooling integration points.

11. External integration surface

- The repo references MCP integrations in the docs, with several skills containing built-in MCP sections.

- These integrations connect the skills to external tools/services such as engine tooling, asset workflows, and project management systems.

- Architecturally, MCP is an extension layer rather than a core dependency.

12. Overall data flow

- A user or project loads CLAUDE.md and selected skill Markdown files into Claude.

- Claude consults shared docs, genre packs, and templates to produce structured game-dev outputs.

- Hooks and validation scripts enforce consistency, while starter configs bridge the skill system into real Godot/Unity/Unreal projects.