rd-design-doc

Use the six-section template: System Positioning, Gameplay Mechanics, Numeric Design, Player Experience, Edge Cases, and A测 Scope. Each section has required sub-questions, and every design decision must include rationale and alternatives.

Create a design doc for new mechanics, system interaction changes, player-visible behavior changes, balance design, UX flows, or content structure. Use a session doc for pure implementation, bug fixes, refactors, and small tuning changes.

Include base values, formulas with actual math, scaling curves, balance targets like TTK or depletion rates, and tuning knobs. Numbers are design targets, not implementation truth; mark unknowns as TBD with the guiding design principle.

Design docs go in .agent/design/{subsystem}/{topic}.md using kebab-case ASCII filenames with no dates, Chinese characters, or spaces. Subsystem directories like character/ or combat/ organize docs by game area.

Every system has boundary conditions: zero and maximum values, conflicting system interactions, missing dependencies, save/load behavior, and multi-entity scenarios. The template requires at least five edge cases in a table mapping each case to expected behavior.