Gameplay Systems Architecture

Community

peterbamuhigire

gameplay-systems-architecture

Use when specifying or implementing engine-neutral gameplay systems such as movement, combat, AI, quests, dialogue, inventory, progression, save/load, world state, spawning, cameras, or narrative state; engine skills own framework integration.

Overview

Publisher	peterbamuhigire
Repository	`chwezi-dev-engine`
Skill name	`gameplay-systems-architecture`
Stars	29
Forks	6
Bundled files	4
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by peterbamuhigire on GitHub. Read the source before you install it.

Installation

Install the Gameplay Systems Architecture AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/peterbamuhigire/chwezi-dev-engine/tree/main/skills/game-development/gameplay-systems-architecture
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/peterbamuhigire/chwezi-dev-engine/tree/main/skills/game-development/gameplay-systems-architecture

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/peterbamuhigire/chwezi-dev-engine.git /tmp/chwezi-dev-engine
mkdir -p .claude/skills
cp -r /tmp/chwezi-dev-engine/skills/game-development/gameplay-systems-architecture .claude/skills/gameplay-systems-architecture

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gameplay Systems Architecture in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gameplay Systems Architecture on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gameplay Systems Architecture is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Gameplay Systems Architecture

Turn game rules into deterministic, inspectable systems with clear state, ownership, events, persistence and test seams.

Prerequisites

Load the approved player verbs and system requirements, world-class-engineering, and the selected engine skill for integration constraints.

Use When

Designing or coding combat, AI, interaction, quests, dialogue, inventory, abilities, progression, cattle/herd, companions, world state, camera or saves.

Do Not Use When

Selecting the overall game concept or implementing engine packaging.

Required Inputs

Approved player verbs, rules and invariants; system dependencies; content schema; save compatibility; target scale; failure cases; determinism and networking needs.

Workflow

Write the system promise, authoritative state, invariants, inputs, outputs, events and failure modes.
Model explicit states and transitions; separate simulation, presentation, authoring data and persistence.
Choose event, command, query and ownership boundaries; prevent circular dependencies.
Design data schemas and stable IDs before authoring large content sets.
Add deterministic tests for rules, integration tests for boundaries, save migrations, debug views and telemetry.
Integrate through the chosen engine's composition root and profile worst-case content.

Quality Standards

Make time, randomness, identity and persistence injectable or reproducible where tests require it.
Version save data and content schemas; recover safely from corruption and interrupted writes.
Treat AI as readable state/utility/behaviour logic with perception and action budgets, not uncontrolled per-frame search.
Keep narrative branches, quests and dialogue data-validatable and localisation-safe.

Anti-Patterns

God object player controller. Fix: capability components and orchestrated state.
Events with no owner or lifecycle. Fix: explicit subscription and cleanup contract.
Save by serialising scene objects blindly. Fix: versioned domain snapshot and migration.
AI state hidden across coroutines. Fix: explicit state and debug trace.
Content authored before schema validation. Fix: validators and stable identifiers first.

Outputs

System specification; state/sequence diagrams; data schema; interfaces/events; implementation plan; automated tests; debug tooling; save migration and performance evidence.

References

Gameplay systems patterns
Save, quest and narrative state
Resource vitality and carrying capacity systems

Evidence Produced

Category	Artifact	Format	Example
Correctness	Gameplay state and invariant test pack	Markdown plus deterministic fixtures	state transition, authority, save/load, exploit case, failure recovery, and replay

Decision Rules

Need	Pattern
Mutually exclusive behaviour modes	Explicit state machine
Many scored alternatives	Utility selection with inspectable scores
Authored sequential objective flow	Validated quest graph
Cross-system notification without command authority	Typed event
Durable player/world state	Versioned snapshot plus migrations

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Gameplay Systems Architecture AI skill do?

Why use Gameplay Systems Architecture on TypingMind?

Because you install it once and use it with any model. Gameplay Systems Architecture is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gameplay Systems Architecture in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/peterbamuhigire/chwezi-dev-engine/tree/main/skills/game-development/gameplay-systems-architecture. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Gameplay Systems Architecture?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gameplay Systems Architecture?

As many as you like. As long as a model supports skills, you can use Gameplay Systems Architecture with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gameplay Systems Architecture AI skill free?

Yes. It is published on GitHub by peterbamuhigire under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Html Ppt Zhangzara Block Frame

nexu-io

OrganizationPopular

Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.

Html Ppt Zhangzara Cartesian

nexu-io

OrganizationPopular

An economics senior thesis on the employment effects of local minimum-wage increases — identification strategy, evidence, and limitations. Built as a decision-grade coursework defense deck for thesis…

Constraint Driven Development

addyosmani

CommunityPopular

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no…

Spec Driven Development

addyosmani

CommunityPopular

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and…

Gameplay Systems Architecture

Overview