← ClaudeAtlas

coordinate-readmeslisted

Coordinate a Foundry plugin's Claude and Codex README editions, preserving common product content and verifying platform-specific installation, availability and benchmark evidence. Use for paired README edits, benchmark updates or a README parity review before release.
V-Songbird/foundry · ★ 4 · Code & Development · score 77
Install: claude install-skill V-Songbird/foundry
# Coordinate plugin READMEs This skill coordinates Claude/Codex edition pages and their shared main overview. Main retains the shared product story, branding, animation, benefits, mechanism, usage examples and general limitations, with a clear edition choice. Keep native install commands, compatibility details and measured tables in their editions. Use scripts/build-main-readmes.js to regenerate common content and validate main with check-main-frontpage.js --claude-ref Claude --codex-ref Codex. Common edition changes also update main before release. Flint is excluded from this main policy. Locate both platform checkouts before editing. Use `git worktree list` or inspect the other branch read-only; preserve uncommitted work and stay off `main`. This is a Foundry development skill, not a skill shipped inside each plugin. Use the same product narrative, headings, section order, common outcomes and decorative branding in both editions. Read the current Foundry README template and `readme-parity` rule. Preserve only the six named exception blocks: `identity`, `install`, `commands`, `compatibility`, `benchmarks`, `links`. Each difference needs a real platform or edition reason. Do not hide a rewrite of the shared product story inside an exception or remove a supported feature just because the other edition lacks it; identify that availability difference. Use the same questions and table columns for benchmarks. Check original evidence for the actual host, model, comparison, sour