design-sync

Align design documentation with current codebase architecture and flag unsafe changes.

Updated Jan 20, 2026

Search Tags:#automation #architecture #documentation #codebase #verification #design-sync

Ready to run

npx skills add https://github.com/spencerbeggs/claude-design-coordinator --skill design-sync-spencerbeggs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-sync
Source: https://github.com/spencerbeggs/claude-design-coordinator/tree/main/.claude/skills/design-sync
Command: npx skills add https://github.com/spencerbeggs/claude-design-coordinator --skill design-sync-spencerbeggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align design documentation with the current codebase state to ensure docs reflect implemented architecture.

Core Features & Use Cases

Design-Doc Alignment: Verify references, exports, and architecture against code, and update docs safely.
Discrepancy Reporting: Flag misalignments and generate actionable remediation steps.
Safe Auto-Updates: Apply safe updates (timestamp, minor edits) automatically while flagging unsafe changes for review.
Use Case: When code changes introduce new packages or API surface, run /design-sync to align docs across modules.

Quick Start

Run a module-wide sync to align its design documentation with the current codebase state.

Frequently Asked Questions about design-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep design documentation aligned with a changing codebase?▼

To keep design documentation aligned with a changing codebase, you can run an automated sync that verifies references and architecture against current code, applying safe updates automatically while flagging unsafe changes for manual review.

How do I automatically update design docs when new API surfaces are introduced?▼

You can automatically update design docs when new API surfaces are introduced by running a module-wide sync that verifies implemented architecture and applies safe edits, such as timestamps and minor metadata, without overwriting complex manual changes.

What is the best way to detect misalignments between architecture documentation and code?▼

The best way to detect misalignments between architecture documentation and code is to run an automated verification process that compares design references against the current codebase state and generates actionable remediation steps for flagged discrepancies.

Can I automatically apply safe edits to design docs while flagging complex changes for review?▼

Yes, you can automatically apply safe edits like timestamp updates to design docs while flagging complex architectural changes for manual review, ensuring documentation metadata remains accurate without overwriting critical manual modifications.

How do I track the last-synced timestamp for documentation across multiple modules?▼

You track the last-synced timestamp for documentation across multiple modules by running an automated synchronization process that maintains accurate last-synced timestamps and updates design metadata as code changes are applied across the codebase.

What should I do when code changes introduce new packages that break existing design docs?▼

When code changes introduce new packages that break existing design docs, you should run a discrepancy report to flag misalignments and generate actionable remediation steps to manually update the affected architecture documentation.