Summarize and execute civ-game version update workflow, including change classification, changelog entry authoring, release highlights, and verification steps. Use when the user mentions version update, changelog, release notes, patch notes, or asks to prepare a new version.
Answer civ-game mechanic questions by strictly grounding every claim in the current repository code and config. Use when users ask how gameplay systems work, why a value changes, unlock conditions, formulas, event effects, diplomacy/economy logic, UI behavior, or balance details. Require file-level evidence, avoid speculation, and explicitly state when the code does not contain enough information.
Systematic grounding workflow for this civ-game repository. Use when handling any feature, bugfix, refactor, balancing change, UI update, or architecture adjustment in this repo. Force a "read-first, understand-first" process covering project architecture, gameplay logic, economic mechanisms, and numeric systems before implementation. Reuse existing systems by default; if a new subsystem is truly unavoidable, notify the user first and wait for confirmation.
Diplomacy system work for civ-game (foreign economy/development/military simulation, treaties, alliances/organizations, relations like colony or subject, diplomatic actions, and diplomacy UI or events). Use when implementing or modifying diplomacy logic, diplomatic AI, treaties or agreements, nation relations/organization systems, foreign market calculations, or DiplomacyTab UX in this repo.