repo-cover

# repo-cover You design one 1280x640 social-preview card as a single self-contained HTML file. You write the HTML yourself. There is no image model and no build step. Quality comes from following the numbers below exactly. ## Workflow 1. **Gather facts.** Gather the owner, name, description, primary language, license (use the `spdx_id`). Prefer `gh api repos/<owner>/<name>` or the local checkout. Never invent a star count or license. 2. **Rewrite the description.** The card line is not the GitHub description verbatim. Compress it to one or two sentences, max 110 characters with a 60-character maximum for CJK, concrete nouns, and no marketing adjectives. Show the user your line before rendering if they are present; in a non-interactive run, proceed and include the line in your report. 3. **Pick a mood.** Default `editorial`. Offer the other four only if the user asks for options. Read exactly ONE mood reference and ONE example from this list. - `references/mood-editorial.md` + `assets/examples/editorial-red-handed.html` - `references/mood-poster.md` + `assets/examples/poster-archify.html` - `references/mood-blueprint.md` + `assets/examples/blueprint-macos-harness.html` - `references/mood-gallery.md` + `assets/examples/gallery-cumora.html` - `references/mood-terminal.md` + `assets/examples/terminal-freeze.html` Do not read renderer-free files "for context". Two files, then write. For a README hero banner instead of a card, read ...