cli-forge-readmelisted

> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the README in that language. If the project is bilingual, ask the user which language to use before proceeding. # README Generator — Production First Generate professional README.md files where **results come first, plumbing comes second**. **Gotchas** — read `../../gotchas.md` before producing output to avoid known mistakes. ## Philosophy A README is a **landing page**, not a technical manual. - 90% of visitors want to know: what, why, how to start - 10% want to contribute or understand internals - Structure for the 90%, don't punish them with the 10% **Tone rule: Friendly on the surface, technical in depth.** - Tier 1–2: plain language, no jargon, a junior dev or a PM can understand - Tier 3: full technical depth, assume the reader codes ## Workflow ### Step 1 — Detect project context Build the shared reconnaissance brief first — read `../../shared/recon.md` (what / who / problem / headline / differentiator / golden-path). The same brief feeds prez and demo, so the README, slides, and live demo tell one story. Then read the project root to auto-detect the type: | Signal | Project Type | |--------|-------------| | `Cargo.toml` | `rust-lib` or `rust