design-synclisted

# design-sync · Synchronize Design Docs During Feature Extensions Load this skill before implementing **any feature extension or behavioral change** in code. Ensure that "implementation = design specifications = reference documentation" remain strictly synchronized. Never write code first and backfill documentation later. ## Trigger Scenarios - Adding or modifying command family classification (`classify`), guard gate semantics (`gate`), configuration options (`config`), or localization messages (`i18n`). - Adding or modifying client integrations or hook protocols (`platform`/`wire`/`cli`/`index`/`pi`). - Any changes that impact interception behavior (decision evaluation, encoding, degradation, wiring). ## Steps 1. **Locate Changes**: Identify which architectural layer and file the extension belongs to (refer to the mapping table below) before editing code. 2. **Update `docs/design.md`** (Authoritative Specification): Update corresponding sections including the guard matrix, classifier hardening surface, platform protocol table, configuration schema, and test strategies. 3. **Update `docs/design/<client>.md`** (Per-Client Implementation Details): Update files for affected clients. If changes involve the shared pipeline (`evaluateCommand` core), review the relevant sections across all client files. 4. **Update `.agents/hooks/references/<client>.md`** (Protocol Quick Reference): Keep in strict parity with wire artifacts and `platform.ts` encoding (AGENTS.md §8 checklist it