game-data-driven-design

Translate game design intent into per-entity data definition documents.

Updated Mar 23, 2026

Search Tags:#architecture #data-driven #game-design #ER-diagram #entity-definition #definition-docs

Ready to run

npx skills add https://github.com/angus945/skill.angushcy-data-driven --skill game-data-driven-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: game-data-driven-design
Source: https://github.com/angus945/skill.angushcy-data-driven/tree/main
Command: npx skills add https://github.com/angus945/skill.angushcy-data-driven --skill game-data-driven-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Data-driven architecture design for game development helps teams turn design intent into scalable data models, reducing ambiguity and rework.

Core Features & Use Cases

Translate GDD concepts into per-entity data definitions and relationships.
Produce independent definition documents per entity using the provided templates.
Generate an index and ER diagram to visualize system architecture and support versioning.

Quick Start

Provide the system scope and entity requirements, then generate an OutputDirectory with one document per definition using the specified templates.

Frequently Asked Questions about game-data-driven-design

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

FAQPage Schema

How do I translate game design intent into data-driven architecture structures?▼

Data-driven architecture translates game design concepts into per-entity data definitions and relationships, reducing ambiguity. It maps GDD scope to structured entity definitions, creating independent documents that maintain system scalability and minimize rework.

What is the best way to generate ER diagrams and entity definitions from a Game Design Document?▼

Generating entity definitions from a GDD involves applying a per-entity definition workflow to produce an OutputDirectory. This directory contains an _index.md file and individual {DefinitionTypeName}_Def.md files for each core game entity, visualizing architecture and supporting versioning.

How do I structure data-driven game entities for version compatibility and persistence?▼

Structuring data-driven entities requires mapping core game relationships and integrating them with chosen persistence formats. This approach satisfies the definition workflow by producing structured markdown documents that explicitly track version compatibility and engine integration.

Does this data-driven game design approach work with specific game engines and persistence formats?▼

Yes, the data-driven architecture approach applies to core game entities and their integration with chosen persistence formats and engines. It structures entity relationships to ensure compatibility within the specified engine environment.

When do I need to create independent definition documents per game entity?▼

You need independent definition documents per entity when translating GDD concepts into scalable data models. This per-entity workflow reduces ambiguity by generating structured definition files that support system architecture visualization and version control.

What are the limitations of data-driven architecture for game system design?▼

The approach requires providing clear system scope and entity requirements upfront to generate the OutputDirectory. Without explicit design intent and defined entity relationships, the generated definition documents and ER diagrams cannot accurately map the game architecture.