Sparkore Core

balance-analysis

Use for the receiving project's balance modeling, audits, calibration, scenario comparison, pass generation, or validation across Weapon, Hero, Equipment, Enemy, progression, economy, and player-loadout power.

game-project-planner

Build or revise a game Project Plan spreadsheet from a project brief, feature backlog, team capacity and delivery goals. Use for Feature List review and milestone planning; not for detailed GDD authoring or publisher operations unless explicitly in scope.

gdd-authoring

Create a new GDD or substantially revise a canonical game-design document with explicit rules, source ownership, evidence, and review gates.

gdd-migration

Use when migrating legacy, fragmented, Figma-based, spreadsheet-based, or otherwise non-canonical game-design material into the receiving project's canonical KB.

kb-bootstrap

Initialize a project knowledge base shared by Codex and Claude Code, or onboard an existing KB to shared agent guidance, canonical-source routing and handoffs. Use when asked to set up the KB; not to scaffold game code, infrastructure or accounts.

kb-maintenance

Use for the receiving project's KB linting, stale-content review, context refresh, lifecycle hygiene, contradiction/duplication audits, archival, and safe cleanup.

knowledge-steward

Use whenever creating, editing, migrating, reorganizing, superseding, archiving, or otherwise changing durable knowledge in the receiving project's knowledge base.

runtime-audit

Verify or reconcile canonical game design against code, designated live configuration, synced CSV, builds, logs, and runtime evidence.