map-systems

Decompose a game concept into systems, map dependencies, and build a prioritized systems index.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill map-systems-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-systems
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/map-systems
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill map-systems-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level game concept into an actionable design plan is hard: concepts rarely list every system, dependencies are unclear, and teams design systems in the wrong order. This Skill guides a structured decomposition of a game concept into a complete, dependency-ordered systems index. ## Core Features & Use Cases - Systems Enumeration: Extracts explicit systems from the game concept and infers hidden implicit systems (e.g., combat implies damage calculation, status effects, and combat UI), with collaborative user review. - Dependency Mapping & Prioritization: Builds a layered dependency graph (Foundation through Polish), detects circular dependencies and bottleneck systems, and assigns MVP/Vertical Slice/Alpha priority tiers. - Systems Index & Handoff: Writes a systems index to design/gdd/systems-index.md with design order and progress tracking, then hands off individual GDD authoring to the design-system skill. - Use Case: After brainstorming a tower defense concept, run the full workflow to enumerate 20+ systems, order them by dependency, and identify which MVP systems to design first. ## Quick Start Ask the AI to run $ai-game-studio:map-systems to decompose your game concept into a prioritized systems index.

Frequently Asked Questions about map-systems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a game concept into individual systems?

Run the map-systems workflow after creating a game concept document. It extracts explicit systems from the concept, infers implicit systems like save/load and UI layers, and presents the full enumeration for your approval before writing anything.

How do I decide which game systems to design first?

The skill maps dependencies between systems, sorts them into Foundation, Core, Feature, Presentation, and Polish layers, then combines this with MVP priority tiers to produce a concrete design order for authoring GDDs.

What happens if my game concept document is missing?

The skill fails with a clear message directing you to run the brainstorm skill first to create design/gdd/game-concept.md. The concept document is required context and the decomposition cannot proceed without it.

Can I resume systems design work across multiple sessions?

Yes. If a systems index already exists, the skill reads it and resumes from where it left off. Use the 'next' argument to automatically pick the highest-priority undesigned system and hand off to GDD authoring.

Does the skill detect circular dependencies between game systems?

Yes. During dependency mapping it checks for cycles in the dependency graph, highlights them, and proposes resolutions such as interface abstraction or defining a contract between the two systems.