@blazium-engine/subagents
v0.8.1
Published
Studio roster that loads Blazium agent skills.
Readme
Blazium Subagents
A Blazium-only studio roster. 49 working studio/engine agents plus a
routing orchestrator and blazium-ci-watcher.
GETTING-STARTED.md · CONTRIBUTING.md · AGENTS.md · GROK.md
Baseline: Blazium 0.8.x (Godot 4.8.x fork, branch blazium_4.8). GDScript-first. Skills live in
blazium-skills. Do not apply
non-blazium_4.8 APIs. Do not use Unity or Unreal.
This roster publishes its own semver to subagents.json.
Community
- Official website: https://blazium.app/
- IndieDB blog: https://www.indiedb.com/engines/blazium-engine
- Official community: Blazium Discord
- Docs: docs.blazium.app
Ecosystem
| Product | Role | Release |
|---------|------|---------|
| CLI | Install editors, projects, remote control, Steam/itch deploy | npx @blazium-engine/cli. Linux and Windows, x64 and ia32. Catalog: cli.json |
| Hub | Desktop companion; installers bundle the CLI | Linux and Windows, x86_64 and x86_32. Engine builds track blazium_4.8 |
| Crash reporter | Sidecar UI for engine and Hub crash reports | Linux and Windows, x86_64 and x86_32. Catalog: crash_reporter.json. Engine builds track blazium_4.8 |
| Toolchain | PS1, PS2, N64, and Interactive DVD | npx @blazium-engine/toolchain. Linux and Windows, x64 and ia32. Catalog: toolchain.json |
| Skills | Agent skill packs for Claude, Cursor, Codex, and Grok | Own semver, separate from the 0.8.x API baseline. Catalog: skills.json |
| Subagents | Studio roster that loads those skills | Own semver. Catalog: subagents.json |
Install
npm install @blazium-engine/subagentsThe package contains agents/, this README, and the MIT license. Host zip packs stay on the CDN catalog.
Copy or link agents/ into a game repo:
.claude/agents/ ← Claude Code
.cursor/agents/ ← Cursor
.codex/agents/ ← Codex
.agents/agents/ ← Codex (plugins layout)
.grok/agents/ ← GrokFrom this repository:
python scripts/install_links.py
python scripts/validate_agents.pyInstall blazium-skills as a
marketplace so listed skills: resolve. Grok also auto-reads the Claude
marketplace; see GROK.md.
How it works
- Start with
blazium-orchestrator(or/start). - Orchestrator reads
blazium-routerand picks design / prototype / development. producerspawns at most two more specialists in development mode.- Each agent opens only the
blazium-*skills in its frontmatter.
Never mix editor MCP 6506, game MCP 6507, remote_control 6508, Hub 39218, and Games cloud.
Roster
See AGENTS.md and mapping.yaml.
Studio seats use common production titles (producer, gameplay-programmer, …).
Engine seats are Blazium specialists (blazium-mcp-specialist, blazium-luau-specialist, …).
Thin commands (Claude Code)
| Skill | Role |
|-------|------|
| /start | Run the orchestrator |
| /help | Print the roster |
| /setup-blazium | Pin engine=blazium 0.8.x |
On Grok, ignore frontmatter model: and paste one agent file as the specialist system prompt.
