What problem does it solve? Keeping backend data dictionaries consistent with frontend module definitions is error-prone when done manually: modules get duplicated, labels drift from values, and writes hit the wrong environment. This Skill makes the module dicts.ts file the single source of truth and reconciles it with the backend through a preview-then-confirm workflow. ## Core Features & Use Cases - Project-wide discovery and reconciliation: Scans all src/views/**/dicts.ts files, builds a backend index, and produces a safe-additive plan that only adds missing modules, dictionaries, and items while blocking on any name, order, or value/label drift. - Bootstrap for legacy projects: Aggregates existing api.md dict-contracts via wls_dict_bootstrap to create local dicts.ts files without guessing enumerations from code. - Guarded writes: Every publish requires environment verification (gatewayPath, sysAppNo), a preview with a planHash, explicit user confirmation, and post-write re-query; conflicts like DICT_MODULE_HIDDEN_CONFLICT halt execution with guided remediation. - Use Case: After adding a new order-status dictionary to src/views/produce/order/dicts.ts, run a project-scope preview, confirm the returned plan hash, and publish only the missing dictionary entries to the SIT environment. ## Quick Start Ask the AI to preview and sync all module dictionaries from the project's dicts.ts files to the backend, confirming the plan hash before any write.
