What problem does it solve?
This Skill provides a structured methodology and checklist for designing, tuning, and reviewing mechanics in tactics and strategy games so decisions are readable, implementable, and fun rather than ad-hoc or unbalanced.
Core Features & Use Cases
- DYNAMICS.md process: A step-by-step design journal workflow that forces theme-first thinking, selects key psychological drivers, and produces one-line mechanics and templates before implementation.
- Mechanics-to-code discipline: Rules for converting mechanics into concise algorithmic pseudocode, avoiding snowflake implementations, and enforcing a stateful data model.
- Tuning & strategy review: Heuristics for numerical tuning (halve/double), identifying anti-strategies, and ensuring rival NPCs and escalation mechanics remain predictable and counterable.
- Use Case: When adding a new unit ability, use this Skill to name its driver, map it to an existing template, express its behavior in pseudocode, and run a strategy review to catch degenerate interactions.
Quick Start
Evaluate a proposed unit ability by naming its psychological driver, writing its one-sentence mechanic, and producing a five-line pseudocode description to validate implementability.