sync-site-docslisted

# Sync Site Docs Keeps the documentation of the 6 personal sites coherent across two layers : 1. **Project-local docs** — `CLAUDE.md`, `README.md`, and any pertinent memory note (`<app>_state_*.md`, `<app>_imagery.md`, etc.) inside the touched repo. 2. **Cross-site case study** — the matching page on `claude-code-codex/frontend/src/pages/case-studies/<slug>.astro` (architecture Mermaid diagram, Pivots & lessons learned section, Tools tested if a new third-party tool was just experimented with). ## When to use - ✅ The site got a **new top-level page** (e.g. `/start` was added on claude-code-codex — README pages table needs an update, the case-study page should mention it). - ✅ A **menu/nav** was reorganized. - ✅ An **architecture pivot** happened (new backend, new data source, removed feature, swapped framework). - ✅ A **new third-party tool** got tested in sandbox (Ruflo-style) — the case-study `/case-studies/ruflo` pattern lives on, plus a Watchlist memo update. - ✅ A **new live feature** went into prod that visitors will see. ## When NOT to use - ❌ Tiny fixes (typos, copy tweaks, color shift) — no doc impact. - ❌ Refactors that don't change the user-visible surface — internal cleanups don't need cross-doc sync. - ❌ The change hasn't been committed yet — work on a clean tree, this skill reads `git log` to detect what landed. --- ## Procedure Track each step with TodoWrite from the start. ### Step 1 — Identify the site ```bash git rev-p