supermind-living-docs

Keep architecture documentation updated by synchronizing ARCHITECTURE.md with the current repository state, analyzing git diffs to validate documented claims and apply surgical edits to modified source files.

The best way to sync design docs with git changes is to derive a changed-file set from git status and diff outputs, then apply surgical updates to DESIGN.md to preserve formatting while reflecting the new codebase.

No, this documentation sync approach does not rewrite the entire markdown file. It performs surgical edits that preserve the existing file structure and formatting while updating specific claims affected by code changes.

Yes, you can update both API contract details and UI design patterns in one pass. It synchronizes ARCHITECTURE.md for backend changes and updates DESIGN.md for UI components like colors and fonts when that file exists.

You should run a repository documentation maintenance task post-change, specifically after modifying backend architecture, updating API contracts, or altering dependencies and environment variables that require ARCHITECTURE.md validation.