sync-artifacts

AGENTVIZ Artifact Sync

You enforce the Five-Artifact Sync Rule: every UI change must update all five artifacts before committing. Your job is to detect what changed, figure out which artifacts drifted, and fix them -- including regenerating screenshots.

The five artifacts:

1. README.md -- feature descriptions, architecture section, file tree
2. docs/ui-ux-style-guide.md -- token values, patterns, rules
3. docs/color-palette.html -- visual swatch reference for every color token (dark + light)
4. docs/screenshots/ -- all 8 screenshot PNGs
5. CLAUDE.md -- architecture section, conventions, file tree

Step 1: Detect What Changed

Diff the current branch against the base branch to understand what was modified:

# What branch are we on?
git rev-parse --abbrev-ref HEAD

# What files changed vs main?
git diff --name-only main...HEAD

# What's the full diff?
git diff main...HEAD --stat

Categorize the changes:

Category	Glob	Artifact impact
Components	src/components/**/*.jsx	All five artifacts potentially
Hooks	src/hooks/**/*.js	README + CLAUDE.md architecture
Library	src/lib/**/*.{js,ts}	README + CLAUDE.md architecture
Theme tokens	src/lib/theme.js	Style guide + color-palette.html + screenshots
Server/routes	server.js, routes/**	README + CLAUDE.md architecture
Config	package.json, vite.config.js	README commands section
Tests	src/lib/__tests__/**	None (tests don't affect artifacts)
Docs only	docs/**, README.md, CLAUDE.md	Self-contained, just validate consistency

Step 2: Audit Each Artifact

For each artifact, check whether the current content matches the code reality.

2a. README.md

File tree (lines ~320-400): Compare against actual src/ structure.

# Generate current file tree
find src/ -type f \( -name "*.jsx" -o -name "*.js" -o -name "*.ts" \) | sort

Check for:

• New files that exist in src/ but aren't listed in the README file tree
• Removed files that are listed in the README but no longer exist
• Renamed files where the old name is in README but the new name isn't
• New features described in component code but not in the Features section
• New keyboard shortcuts added in useKeyboardShortcuts.js but not listed in README
• Architecture changes (new hooks, new contexts, new routes)
• Command changes in package.json scripts that aren't reflected in README