BOOK
Book Prompt Generator User guide · Complete Books 1.1
View PRO plans

Official desktop app guide

How to use the Book Prompt Generator to create full books in phases.

This page explains the generator section by section: from FREE/PRO licensing and profiles, to book phases (bible → outline → chapters → editorial QA), and practical examples you can copy/paste into ChatGPT, Gemini, Claude or any LLM.

  • · Build a reusable master prompt that forces continuity, coherence and non-repetition.
  • · Use profiles (personas) to standardise output across genres and languages.
  • · Generate optional cover prompt + chapter image prompts for visual workflows.

If you just installed the program, start with “Overview”.

1. Overview: what the Book Prompt Generator is and why “write me a book” fails

The Book Prompt Generator – Complete Books 1.1 is a desktop tool that converts your book idea into a master prompt designed to produce consistent long-form writing in phases. It is not “another AI writer”: it’s a prompt architecture system.

When you tell an LLM “write me a book”, it usually breaks on: continuity (names, timelines), repetition (same beats/phrases), pacing, unresolved arcs and inconsistent POV. This generator prevents that by enforcing: bible, outline, chapter prompts and optional editorial QA.

The application typically offers:

  • FREE: limited prompts per session and fewer advanced controls (ideal to test the logic).
  • PRO (monthly/annual/lifetime): full control layer, unlimited prompting, best for daily production.
  • Enterprise Pack: tailored templates and workflows for publishers/teams.

Tip: Even in PRO, the best results come from phase-writing: generate bible first, then outline, then chapters — instead of pushing the model to do everything at once.

2. Main interface: tabs, toolbar, prompt area and export

The app is designed like a productivity dashboard: you configure the book, generate the master prompt, then copy/export your history to reuse what works.

2.1 Plan banner

The top banner shows your plan (FREE/PRO), expiry date, and prompt counter (FREE mode). It’s your quick signal to know if advanced controls should be available.

2.2 Core actions

  • Generate Book Prompt: builds the master prompt from your configuration.
  • Clear: resets fields (useful when switching projects).
  • Copy: copies the prompt for immediate use in your AI tool.
  • Export: export your project/history as JSON for versioning.

2.3 “How it works” tab

Inside the app, the “How it works” tab is meant to teach new users the phase approach and show examples of correct workflows. This web page mirrors that intent.

2.4 Language: UI vs Book language

The program separates UI language (menus/buttons) from book language (the content you generate). Example: you can keep UI in Spanish while generating a book in English or French.

Recommended rule: write the brief in the same language as the book whenever possible. If you brief in Spanish but want an English book, be explicit about locale (US/UK) and tone.

3. Profiles & personas: your “production presets”

A profile (preset) is a snapshot of your configuration: genre, book type, rigor, POV, pacing, style rules and more. Profiles are how you avoid “starting from zero” every time.

3.1 What a profile should contain

  • Book type: novel, novella, series, non-fiction, workbook, lead magnet…
  • Genre: romance, thriller, fantasy, self-help, business…
  • Rigor: BASIC → PRO → STUDIO → PUBLISHER (more constraints + QA gates).
  • POV / pacing: consistency rules for narrative voice and rhythm.
  • Audience & reading level: YA vs adult vs academic.
  • Format: Markdown book-ready, chapter pack, JSON outline…

Think of a profile as your “editorial fingerprint”. If a profile works, reuse it.

3.2 Personas (personifications) you can use

Personas are not “roles for fun”; they are a method to enforce quality. Here are safe, useful personas:

  • Senior developmental editor: focuses on structure, arcs, pacing.
  • Line editor: consistency, clarity, rhythm, style polish.
  • Fact-checker (non-fiction): requires sources or flags uncertain claims.
  • Ghostwriter (brand authority): strong voice + story-based persuasion.
  • Course designer: exercises, worksheets, step-by-step progression.

Tip: If you want a style “inspired by X”, describe traits (pace, sentence length, humor, imagery) instead of copying living authors.

3.3 Example profiles you can create today

Profile A

Thriller · Fast pace · 3rd limited

  • · Rigor: STUDIO
  • · POV: 3rd limited (past)
  • · Pacing: Very fast
  • · Output: Prompt pack

Profile B

Self-help · Authority · Case studies

  • · Rigor: PUBLISHER
  • · Reading level: Adult general
  • · Output: Book-ready Markdown
  • · Include: QA checklist

Profile C

Lead magnet · Short · Conversion-first

  • · Rigor: PRO
  • · Length: short book
  • · CTA blocks: included
  • · Output: PDF-ready structure

4. The phase method (the secret sauce)

The generator is designed to produce a master prompt that you execute in phases. This solves the “LLM forgets everything after 30 pages” problem.

4.1 Phase 1: Book Bible

The bible defines the rules of the universe:

  • · Premise, promise, theme, audience.
  • · Characters (goals, wounds, contradictions, arcs).
  • · Setting rules (time, locations, tech level, constraints).
  • · Voice rules (POV, tense, dialogue ratio, reading level).
  • · “Do not do” list (banned clichés, repetition, meta-commentary).

Result: a stable foundation you can paste at the start of every writing session.

4.2 Phase 2: Outline (acts → chapters)

The outline converts ideas into execution:

  • · Act structure (or module structure for non-fiction).
  • · Chapter list with objectives, turning points, cliffhangers.
  • · Foreshadowing map and payoff tracking.
  • · Continuity ledger: names, dates, places, unresolved threads.

Result: you always know what chapter must accomplish (no filler).

4.3 Phase 3: Chapter prompts

Each chapter prompt includes: goal, scenes, constraints, required callbacks, and a “no repetition” reminder. You write chapter by chapter, keeping context tight.

4.4 Phase 4: Editorial QA

The QA pass checks: consistency, pacing drift, character voice, plot holes, factual issues (non-fiction), and cuts repetition. It’s where the book becomes “publishable”.

4.5 Optional: Cover + images

If enabled, the prompt can output: a cover prompt (style, mood, symbols, format) and per-chapter image prompts for thumbnails or illustrated editions.

4.6 Copy/paste mini examples

Example · Fiction brief

Book type: Novel (fiction)
Genre: Thriller
Language: English
POV: 3rd person limited (past)
Tone: Direct, cinematic, minimal fluff
Premise: A forensic linguist discovers a serial killer uses hidden messages in live sports commentary.
Setting: London + online communities
Core theme: Truth vs narrative manipulation
Constraints: No supernatural; avoid clichés; strong chapter hooks.

Use this as input. Then generate bible → outline → chapter prompts.

Example · Non-fiction brief

Book type: Non-fiction (practical)
Genre: Business / Self-help
Language: Spanish
Reader: beginner/intermediate
Promise: Build a one-person agency in 90 days with AI workflows.
Must include: checklists, templates, mini case studies, action steps.
Style: friendly + no-BS, short paragraphs.

Great for lead magnets and authority books.

Example · “Chapter prompt” request (paste into your LLM)

You are writing Chapter 4. Follow the Book Bible + Outline.
Chapter goal: The protagonist realises the killer is communicating through punctuation patterns.
Required: 2 clues, 1 false lead, 1 character contradiction, end with a hook.
Constraints: Avoid repeating metaphors. No meta commentary. Keep POV consistent.
Output: 1,800–2,200 words. After writing, list continuity notes as bullets.

5. AI workflow: how to use this with ChatGPT / Gemini / Claude

The generator builds prompts. You can paste them into any LLM. For best results, keep a consistent workflow and store your bible/outline in a reusable document.

5.1 Recommended workflow (fast + safe)

  1. 1) Generate Book Bible and save it as “BOOK_BIBLE_v1”.
  2. 2) Generate Outline (chapters + objectives) and save it as “OUTLINE_v1”.
  3. 3) Write chapters one by one using the bible + the specific chapter prompt.
  4. 4) Run QA every 3–5 chapters (or at the end).
  5. 5) Export your best prompt sets (history JSON) for future books.

5.2 Output formats (choose based on your pipeline)

  • Book-ready Markdown: easiest to edit and export to many tools.
  • Prompt pack: one prompt per chapter (production workflow).
  • Structured JSON: best for automation and custom pipelines.
  • Google Docs/PDF-ready: useful for handing off to editors.

Tip: If you plan to automate, pick JSON and route it into your tool (Make/n8n/custom scripts).

5.3 Best practice: “continuity ledger”

A simple ledger prevents 80% of book errors. Maintain a small block like: 

Continuity ledger:
- Character names: ...
- Timeline dates: ...
- Locations: ...
- Open loops: ...
- Banned repetitions / phrases: ...
- Voice rules: POV, tense, dialogue ratio, reading level.

Paste it with the bible at the start of each chapter request.

6. Help center & common issues

Here are the most frequent problems and how to fix them fast.

6.1 “Generate prompt” feels generic

  • · Add constraints: “no clichés”, “no meta commentary”, “minimum chapter hook”.
  • · Define POV + pacing + reading level.
  • · Specify character contradictions and concrete settings.
  • · Use a profile with higher rigor (STUDIO/PUBLISHER).

6.2 Repetition across chapters

  • · Keep a “banned repetition list” in your ledger.
  • · Ask the model to vary sentence openings and metaphors.
  • · Run QA every 3–5 chapters to cut pattern drift early.

6.3 License not recognised

  • · Use the exact purchase email and paste the full key (no extra spaces).
  • · Check if the licence is expired or exceeded activations.
  • · If you changed device, you might need an activation reset depending on plan.

6.4 Writing in multiple languages

  • · Set the book language explicitly (English vs Spanish vs French…).
  • · If English: specify locale (US/UK) and spelling preference.
  • · Keep your brief in the same language as the book when possible.

6.5 Final recommendations (what professionals do)

  • · Use profiles like “editorial templates” (one per genre + audience + rigor).
  • · Always build bible + outline first, even for short books.
  • · Keep a continuity ledger and update it after every chapter.
  • · Treat QA as a real step: fix drift before it becomes a rewrite.
  • · Export your best projects as JSON so your system improves over time.