game-architecture

Orchestrate game engine lifecycle across GameManager, ScenarioManager, and SceneManager.

2|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/C-Ross/LlamaOfFate --skill game-architecture-c-ross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-architecture
Source: https://github.com/C-Ross/LlamaOfFate/tree/main/.github/skills/game-architecture
Command: npx skills add https://github.com/C-Ross/LlamaOfFate --skill game-architecture-c-ross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide engineers to modify and extend the core game loop, engine lifecycle, and NPC behavior without breaking existing systems, by outlining a clear architectural map of layers and interactions.

Core Features & Use Cases

  • Layered orchestration between the engine core, prompt layer, and UI, including GameManager, ScenarioManager, and SceneManager.
  • Detailed workflow guidance for ActionParser, Conflict System, NPC turns, and scenario progression.
  • Use Case: A developer adds a new input handling hook or a debugging toggle and integrates it across the lifecycle to observe end-to-end behavior.

Quick Start

Implement a small feature by extending the SceneManager lifecycle to observe an end-to-end scene from input handling through conflict resolution.

Frequently Asked Questions about game-architecture

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

FAQPage Schema
How do I design a game engine lifecycle that supports modular extension and deterministic action handling?

Game engine lifecycle design requires orchestrating GameManager, ScenarioManager, and SceneManager layers to ensure modular extension and deterministic action handling. This architecture separates engine core, prompt, and UI layers to prevent system breaks during modification.

What is the best way to orchestrate NPC behavior and scene progression across multiple game scenes?

Orchestrating NPC behavior and scene progression requires a layered SceneManager workflow that handles ActionParser, Conflict System, and NPC turns. This ensures deterministic action handling and robust scenario progression across scenes without breaking existing systems.

How does LLM integration work within a game engine architecture for prompt-driven guidance?

LLM integration within game engine architecture uses a dedicated prompt layer between the engine core and UI. This layer guides ActionParser, Conflict System, and NPC turns, ensuring LLM-driven guidance maintains separation of concerns across the lifecycle.

Can I extend the game engine input pipeline to add debugging toggles without breaking existing systems?

Extending the game engine input pipeline with debugging toggles is supported through layered lifecycle orchestration. By extending SceneManager lifecycle hooks, developers can observe end-to-end behavior from input handling through conflict resolution without breaking existing systems.

When do I need deterministic conflict orchestration in a game engine framework?

Deterministic conflict orchestration is needed when modifying core game loops and NPC behavior in an end-to-end game framework. It ensures robust separation of concerns during scenario progression, ActionParser workflows, and conflict resolution across scenes.