beastcoverlisted

# BeastCover People see the title and the cover before anything else. If the cover does not grab them, they scroll past. Make covers with impact: one clear subject, a short headline in large type, strong contrast. Keep every platform version of one piece in the same style and palette. ## Setup Use an installed `beastcover` command when available. Otherwise prefix each command with `npx --yes --package @liustack/beastcover@0.5.0`. Run `beastcover doctor` once on a new machine. If it reports Chromium missing, run `npx --yes --package @liustack/beastcover@0.5.0 playwright install chromium`, then run doctor again. Do not run a bare `npx playwright install`: it can resolve a different Playwright version and download a browser this package cannot use. ## Workspace first Run `beastcover project` before generating anything. - If a workspace exists, keep it. Do not create another one. - If the command says no workspace was found, run `beastcover new <name> --style <style>` once. - Every cover in the workspace uses its style and palette, on every platform. - Write every generated PNG to `.beastcover/out/`. Do not invent extra image folders in the user project. - Keep `.beastcover/project.json` as the project style and palette. Commit it. - Keep `.beastcover/history.jsonl` as the generation log. Commit it. - Leave `out/`, `cache/`, and `refs/` untracked. Fetched stock photos and their `.json` sidecars live in `refs/`. Force-add only the refs the user names. - Copy a style prompt