wotb-sync

What problem does it solve? In the WoTBTools project, a single data change must propagate through many layers: Java replay parsing, REST API keys, trilingual frontend locale files, Excel export column definitions, Flyway migrations, and documentation. Missing one layer causes inconsistent labels, broken builds, or failed ddl-auto validation. This Skill provides a checklist of recipes so every cross-layer change is applied completely and consistently. ## Core Features & Use Cases - Recipe-based playbooks: Twelve targeted recipes (A–L) covering column renames, new data columns, parser/protobuf changes, frontend-only tweaks, rating config, map names, tankopedia updates, Hall of Fame schema, cross-site state, Extended page, Keycloak auth, and FE↔BE OpenAPI contracts. - Golden rules enforcement: API stays pure English snake_case keys; display names live in locales/{zh,en,ru}.json plus Columns.java/AggregateSheets.java; controllers stay thin with logic in services. - Mandatory verification and docs: Each recipe ends with mvn test (JDK 21), npm test/build, and documentation updates. - Use Case: When adding a new player statistic column to battle results, follow Recipe B to update ReplayParser, Columns.java, Mapper.AGG_COLS, AggregateSheets, all three locale files, and the developer guide in one pass. ## Quick Start Ask the AI to add a new replay data column or rename an existing label, and it will follow the matching wotb-sync recipe to update every affected layer and run the required tests.