← ClaudeAtlas

book-genesislisted

Use when the user wants to create, plan, draft, evaluate, revise, package, or run a complete AI-assisted book pipeline. Book Genesis turns a one-line idea into a book project with intake, foundation, architecture, drafting, adversarial audit, Genesis Score, and editorial package artifacts.
jodyjdc/ultimate-best-seller-studio · ★ 1 · AI & Automation · score 74
Install: claude install-skill jodyjdc/ultimate-best-seller-studio
# Book Genesis Book Genesis is Felipe's local book-production pipeline adapted for Codex. It uses the newer `book-genesis-codex` core as the canonical workflow. Use this skill for: - fiction, memoir, nonfiction, or hybrid book projects - turning a rough idea into a structured book - drafting full manuscripts chapter by chapter - auditing AI-written prose and narrative structure - producing Genesis Score evaluations - creating synopses, cover briefs, launch/editorial packages, and formatting handoff notes Do not use the legacy V4 17-phase workflow as the default. It is copied only for historical reference in `references/legacy-v4-book-genesis.md`. ## Core Rule Persist important decisions to files. A Book Genesis run should leave a durable project tree, not just chat output. Commercial-length is a hard contract, not a preference. A manuscript cannot be called complete, final-scored as publication-ready, or packaged for a bestseller/public launch unless it either: - meets the genre/audience `target_floor_words` recorded in `PROJECT_STATE.yaml`, or - is explicitly positioned from intake as a novella, short novel, or serial installment. If no explicit short-form positioning exists, default to full-length commercial book standards. Default project layout: ```text <project>/ PROJECT_STATE.yaml ASSUMPTIONS.md artifacts/ manuscript/ chapters/ evaluations/ delivery/ ``` ## Canonical Pipeline Load `references/pipeline/manifest.yaml` before starting or advanc