Game Dev Agentic Skills

---

📜 Updates

v0.1.1 - Artifact to Engine

October 16, 2026

• gdas-reader: reads a source tree, web bundle, asset folder, WASM module, or PE/ELF header into an evidence ledger. It is shared by both engines and is not part of either hub mirror.
• godot-rea: emits a Godot 4.7 stub project from that ledger. Unknown behavior stays pass.
• bevy-rea: emits a Bevy 0.20 stub crate from the same ledger. Empty systems stay empty until a Domain Skill fills them.
• License gate: asset bytes are copied only when you pass a real license note and --allow-assets.

---

---

Engines

Game Dev Agentic Skills is one product with per-engine trees. Pick the master for the engine you are shipping — there is no singular product-wide master.

Install one engine master or one Domain Skill — never --all. Pick the engine you are shipping; skills stay engine-scoped.

📍 Quick Navigation

---

The Philosophy

Game Dev Agentic Skills (GDAS) is an agent-first knowledge library for shipping real games — not AI slop. Each engine gets its own master and Domain Skills.

• Godot 4.7+ is fully supported: doc-true patterns, personas, and production scripts under godot-master.
• Bevy 0.20+ is fully supported: ECS ownership and Domain Skills under bevy-master.
• Skills stay engine-scoped. Install one path so you do not trigger a Context Storm.

If this project helps your development or empowers your agents, please give it a star! 🌟

---

⚡ Quick Start

Choose one path so you do not trigger a “Context Storm” (flooding the agent with every skill at once).

Path A: Godot

New Godot project, or an existing one that needs a Godot 4.7+ standards check - install the Godot hub or one Godot Domain Skill:

npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/godot-master
# or one Domain Skill:
npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/godot-characterbody-2d

Path B: Bevy

Bevy work starts at the Bevy hub or one Bevy Domain Skill:

npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/bevy-master
# or one Domain Skill:
npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/bevy-ecs-composition

Path C: One specialist skill

Need a single feature and already know which skill owns it - install only that path (either engine):

npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/godot-inventory-system
npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/bevy-inventory-system

[!DANGER] NEVER use the --all flag when installing this repository (e.g., npx skills add ... --all). That is an “Instant No-No” — it forces your agent to load every metadata entry across 184 skills and triggers an unrecoverable Context Storm.

---

🧭 Agent Installation Rubric

Use this when installing via the skills CLI, or when an agent is reading this README after a repo clone (DIA path) instead of a normal plugin install.

Rules

1. Preferred install: one path only, for example npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/godot-master -g -a -y or npx skills add thedivergentai/Game-Dev-Agentic-Skills/skills/bevy-master -g -a -y (swap the skill path for a Domain Skill when needed).
2. Verify: npx skills list -g -a
3. Restart the host agent after install — most agents load skills once at session start.
4. Clone / DIA path (no npx skills add): query skills_index.json, then read skills//SKILL.md with the agent’s file tool. Do not hand-symlink into host skill dirs unless the user asks for that.
5. Canonical store: ~/.agents/skills/ is the CLI’s shared copy; per-agent discovery paths differ by design.

Troubleshooting

• Skill installed but missing in the agent → confirm with npx skills list, re-run with the correct -a , then restart the agent.
• Do not treat a manual Claude-only symlink into ~/.claude/skills/ as the default fix — that only helps one host.

---

🧠 Context Management: Performance Guidelines

To keep your AI agent fast and accurate, follow these “Expert Efficiency” rules:

1. The “Power of One” Rule

Either use an engine master (godot-master / bevy-master) OR individual Domain Skills — never both masters plus a pile of Domain Skills.

• Godot Master is an “Orchestrator” skill. It is dense (~15k tokens) but provides a complete blueprint. Use it when the “Big Picture” matters.
• Domain Skills are “Surgical” skills (~2-5k tokens). They are fast, reliable, and keep the agent focused on one specific API.

2. Why “Install All” Fails

Installing 184 skills simultaneously creates a “Metadata Flood”:

• Token Bleed: ~15,000 tokens are “permanently” used just to tell the agent which skills exist.
• Instruction Conflicts: Having multiple overlapping expert instructions (e.g., 20+ different genre blueprints) can cause the agent to lose its specific focus.
• Reasoning Lag: The model has to sift through 100+ KB of text before deciding what to do.

3. Repository Clones vs. Plugin Installs

• Plugin Install (npx skills add): Copies/links the skill into your agent’s skill directory (see Agent Installation Rubric). The agent can then discover it automatically. This is why installing too many at once causes a “Context Storm.”
• Repository Clone: If you merely clone this repo to a folder (e.g., Downloads/GDSkills), the agent will NOT auto-load skills unless you are working inside that directory. Use skills_index.json + read each SKILL.md with the agent’s file tool (DIA loop below).

---

godot-master is the hub for Godot 4.7+ projects. It orchestrates 99 Domain Skills, personas, workflows, and production scripts into one architectural framework. Install the hub or a single Domain Skill when you are shipping on Godot.

bevy-master is the hub for Bevy 0.20+ apps. It orchestrates 82 Domain Skills covering ECS ownership, rendering, gameplay, UI, platforms, and genres into one architectural framework. Install the hub or a single Domain Skill when you are shipping on Bevy.

📂 Full Skill Index

All skills are catalogued in the machine-readable skills_index.json with keywords, descriptions, and dependency chains.

[!NOTE] This JSON index is a repository-level file and is only present if you have cloned the source repository.

---

🤖 For Agents — The Discovery-Ingestion-Application Protocol

AI agents must follow the DIA loop for maximum quality:

1. Discovery

Query skills_index.json and pick the engine first.

Godot example: “smooth character movement” -> godot-characterbody-2d, then godot-master if the project needs architecture.

Bevy example: “ECS player movement” -> bevy-character-movement, then bevy-master if ownership and schedules are still open.

2. Ingestion

Agents must not implement from general training data alone.

Read the chosen SKILL.md with the file tool. Godot skills carry Godot 4.7+ nuances (StringName lookups, signal direction). Bevy skills carry ECS ownership (Component, Resource, Query, Commands, .chain(), Fixed / FixedMain).

Complex Godot projects: load godot-master. Complex Bevy projects: load bevy-master. Do not load both hubs for one task.

3. Application

Follow the skill chain in the skill header. Apply patterns from the deepest dependency upward, staying inside the same engine.

Godot workflow:

User: "Build a player controller" (Godot)
Agent: Query skills_index.json -> godot-characterbody-2d
Agent: Read dependencies (godot-composition, godot-state-machine-advanced) first
Agent: Implement movement on top of those patterns

Bevy workflow:

User: "Build a player controller" (Bevy)
Agent: Query skills_index.json -> bevy-character-movement
Agent: Read bevy-master if component vs resource is unclear
Agent: Implement locomotion on Fixed / FixedMain

Anti-Erosion Policy

Documentation stays in sync with implementation. When a Godot 4 or Bevy 0.20 API changes, update the relevant SKILL.md.

---

🏗️ Infrastructure Integration

Godot programmatic building (godot-builder)

Godot scene scaffolding and headless automation go through godot-builder (also mirrored in godot-master Workflow 11). Use Godot CLI scripts such as create_scene.py, add_node.py, and run_project.py.

Bevy apps scaffold through Cargo and bevy-project-foundations (App::new(), DefaultPlugins / MinimalPlugins). Do not point Bevy tasks at godot-builder.

Project standards

Godot code follows Godot 4.7+ conventions:

• Static typing: func move(vec: Vector2) -> void:
• Signal / Callable / Tween (Godot 4 syntax)
• StringName for performance-critical lookups
• Component composition over deep inheritance

---

🤝 Contributing

We welcome contributions from developers and agents!

📖 Read the full contribution guide: CONTRIBUTING.md

Quick Guidelines:

• Every skill must provide Expert Knowledge Delta (not tutorials)
• Include anti-patterns with non-obvious explanations
• Godot skills: Godot 4.7+ GDScript, statically typed, scripts parse without warnings
• Bevy skills: Bevy 0.20+ Rust, ECS ownership explicit, no Godot types in Bevy crates

Submit: Open an issue with [Request] tag or submit a PR describing the knowledge delta your skill adds.

---

⭐ Star History

If this project accelerates your Godot or Bevy work, or empowers your AI agents, consider starring the repository!

---

📊 Repository Stats

---

💖 Sponsorship & Support

We are seeking financial sponsors and infrastructure partners to sustain Game Dev Agentic Skills across Godot and Bevy. Every contribution helps us maintain these skills and keep them free for the community.

🚀 View our Sponsorship & Support Opportunities

Get in Touch: [email protected]

---

📜 License

This project is licensed under the GNU Lesser General Public License v3.0 - see LICENSE for details.

Why LGPLv3?
We chose this license because it strikes the perfect balance for an open ecosystem. It ensures that any improvements or additions made directly to the GDSkills library itself remain open-source and shared with the community. At the same time, it empowers you to use these agentic skills to build and compile your own incredible games, which you are completely free to commercialize and keep closed-source if you wish.

By contributing, you agree that your code will be licensed under the project’s LGPLv3 License.

---