docs-sync

To sync design docs with user documentation, this skill detects changes via timestamp comparisons and hashes, then propagates updates across READMEs, repository guides, and site docs while preserving manual edits.

Change detection works by comparing timestamps and hashes between design docs and user docs to identify stale files, then performing impact analysis to determine which README, repository, or site docs require updates.

Yes, manual edits are preserved during sync. The process handles conflicts selectively, ensuring custom user content in READMEs and site docs remains intact while propagating necessary design-doc updates to affected files.

The best way to sync READMEs with design documents is using a configuration-driven approach via .claude/design/design.config.json that validates content, handles conflicts, and updates sync timestamps after propagating changes.

Yes, documentation sync is driven by the .claude/design/design.config.json file, which controls change detection, selective updates, validation, and conflict handling across your Level 1, 2, and 3 documentation layers.