What problem does it solve? Adding, renaming, or deleting a data column in a full-stack replay analytics project touches many layers—Java core definitions, web DTOs, Excel export headers, frontend i18n files, and tests—and missing any one layer causes silent inconsistencies or build failures. ## Core Features & Use Cases - Layered Checklist: Ordered verification steps covering Columns.java, PlayerResult.java, ReplayParser.java, Mapper.java, Excel sheet headers, and three-language locale files (zh/en/ru). - Test & Documentation Gates: Includes ParityTest.java, WebApiTest.java, Maven test runs, frontend builds, and CHANGELOG/DEVELOPER_GUIDE updates. - Sub-agent Split: Suggests dividing work into core-sync, ui-sync, and verify-sync agents for parallel cross-layer execution. - Use Case: When adding a new "assisted damage" column to battle results, follow the checklist to update the Java column definition, DTO mapping, Excel headers, all three locale JSON files, and tests without missing a layer. ## Quick Start Ask the AI to add a new data column to the replay results and follow the column-sync checklist to update every layer consistently.