Use Gen Book to produce a multi-issue comic series — with story continuity, character arcs, and a franchise bible.
What this framework builds
56 production-ready prompts across 7 pipeline stages for producing a complete 3-issue comic series inside Pure.v2 Comic Studio. Franchise Bible setup, Gen Book configuration, Story Intelligence arc tracking, cross-issue continuity management, issue-to-issue handoff design, and Franchise Intelligence for universe expansion — every stage has a prompt sequence that tells you exactly what to do and in what order.
The problem it solves
A single issue is a creative exercise. A series is a production system. The jump from Issue #1 to a 3-issue arc breaks most creators because continuity management, character arc tracking, and cliffhanger design are not creative problems — they are structural ones. This framework gives you the structure: a Franchise Bible that tracks every state change, a Gen Book pipeline that maintains visual consistency across issues, and a continuity system that catches errors before they become print problems.
How it works — 7 stages
Stage 1 builds the Franchise Bible: universe canon, character arc tracking (goal, fear, wound, want vs need mapped across all 3 issues), and a world-state log that records every change after each issue. Stage 2 structures Issue #1 as an origin: world introduction, protagonist establishment, inciting incident, first antagonist encounter, and cliffhanger design. Stage 3 configures Gen Book for automated multi-page generation with style lock, character DNA injection, and color script import. Stage 4 runs Story Intelligence: emotional arc charting, pacing analysis, and the Predictive Panels system. Stages 5 and 6 structure Issues #2 and #3 with specific escalation and confrontation prompts, including the issue-to-issue handoff system (cliffhangers, callbacks, foreshadowing). Stage 7 runs Franchise Intelligence: spin-off potential analysis and universe expansion prompts.
What you get
56 prompts · 7 pipeline stages · Franchise Bible setup · Gen Book pipeline · Story Intelligence arc tracking · Cross-issue continuity system · Issue structure prompts (origin, escalation, confrontation) · Issue handoff design · Franchise Intelligence · Lifetime updates
Who it's for
Creators who have completed Issue #1 and want to build a series, writers planning a multi-arc story that needs continuity management, creators who want to use Gen Book for automated multi-page generation, and anyone building a comic franchise with spin-off potential.
Sample output
A 3-issue comic series: Issue #1 (origin), Issue #2 (escalation), Issue #3 (confrontation) — each with a cover, 22 interior pages, and a shared franchise bible tracking character arcs, world-state changes, and continuity flags across all three issues.
Full Access Unlocked
All 56 prompts · All 7 modules
Need expert implementation?
Hire an OrchestratorConnect with a certified Prompt.Doctor Orchestrator to deploy this framework for you.
No coding required. You will use ChatGPT or Claude as your AI tool. Follow these steps in order — do not skip ahead.
Purchase & download the framework
Click the buy button on this page. After checkout, go to the and hit Download .zip. Unzip it — you'll get a .md file (the full framework) and a .pdf (easy to read reference). Keep both open.
Open your project — new or existing
This dashboard is designed to integrate into any existing project or be built as a standalone app. If you already have a site in Airo (or Cursor, Bolt, etc.), open that project. If you're starting fresh, create a new project. The Orchestrator Prompt handles both cases — it scans what's already there and adds only what's missing.
Paste the Orchestrator Prompt into your builder's chat
Open the on this page. Copy the Orchestrator Prompt and paste it into your AI builder's chat. It will scaffold the full admin system — secure login, email marketing module, booking engine, and CMS — on top of your existing codebase. This takes 2–5 minutes.
Add your API keys as secrets
Critical — Novice UsersIn your builder, go to Settings → Secrets and add the keys your app needs. For this framework: STRIPE_SECRET_KEY (for booking payments — get it from your Stripe dashboard), ANTHROPIC_API_KEY (for AI-assisted content — get it from console.anthropic.com), and DATABASE_URL (your MySQL connection string). No key is needed for the admin login, CMS, or email modules — those run on your existing infrastructure.
Don't have a MySQL server?
You can purchase a shared hosting plan with cPanel and MySQL at host.esgwon.dev. Once your account is set up, follow the step-by-step guide to create your database and connect it to your AI website builder.
How to set up cPanel MySQL & connect to your AI website →Need help with Stripe?
Get your STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY from your Stripe dashboard. The guide covers test keys, webhook setup, and going live.
Need help with Anthropic?
Get your ANTHROPIC_API_KEY from console.anthropic.com. The guide covers model selection, cost management, and troubleshooting.
Prompting Airo after setup — always name the file
When asking Airo to add tables, columns, or features to the admin dashboard, always include src/server/lib/admin-db.ts in your prompt. Without it, Airo may target the wrong database. Example: "Add a bookings table in the admin database (src/server/lib/admin-db.ts) — do not touch any other database connection in this project."
Run the framework prompts inside your live app
Your app is now running in the builder's preview panel. Open the on this page, copy each prompt one at a time, and paste it into your builder's chat. Replace every [BRACKET] with your real data before sending. Work through the stages in order — each stage output feeds the next.
Test end-to-end, then publish or hand off to your client
Walk through the admin as a real user: log in, create a booking, send a test email campaign, update a CMS image, and run the Safe-to-Publish gate. Once everything passes, click Publish in your builder. Because this is a white-label dashboard, your client accesses it at /admin on their own domain — no Prompt.Doctor branding, no third-party login required.
7 modules · 56 prompts · 7 workflow stages
Franchise Bible Setup
Universe canon document, character arc tracking (goal, fear, wound, want vs need per issue), world-state log (what changes after each issue), and the lore continuity system.
8 promptsGen Book Pipeline
Gen Book configuration (page count, style lock, character DNA injection), automated generation workflow, production dashboard monitoring, and the Stop/Resume system for mid-generation edits.
9 promptsStory Intelligence — Arc & Pacing
Emotional arc charting across all 3 issues, pacing analysis (panel density, dialogue ratio, action ratio), scene graph construction, and the Predictive Panels system for anticipating reader needs.
10 promptsIssue #1 — Origin Structure
Origin issue prompts: world introduction, protagonist establishment, inciting incident, first antagonist encounter, and cliffhanger design that sets up Issue #2.
9 promptsIssue #2 — Escalation Structure
Escalation issue prompts: callback to Issue #1 cliffhanger, raising stakes, character arc midpoint (false victory or dark night of the soul), and the Issue #2 cliffhanger that makes Issue #3 inevitable.
10 promptsIssue #3 — Confrontation & Resolution
Confrontation issue prompts: all setups pay off, character arc completion, climax scene construction, and resolution that closes the arc while opening franchise potential.
7 promptsFranchise Intelligence
Spin-off potential analysis, universe expansion prompts (new characters, new locations, new conflicts), and the marketing studio workflow for series launch.
3 promptsPaste this into the Narrator panel. Fill in every bracket. The Narrator will set your universe, create all characters, save your franchise continuity facts to AI Memory, plan all pages for Issue #1 with layouts and panel prompts, and pre-fill the Cover Designer — all in one shot. This is your Issue #1 foundation. --- I'm building a multi-issue comic series called [SERIES TITLE]. This is Issue #1: [ISSUE SUBTITLE]. FRANCHISE BIBLE: Universe: [World name], [genre], set in [time period]. World rules: [2–3 sentences on what makes this world different] Lore: [1 paragraph on the state of the world as Issue #1 opens] Central conflict (spans all 3 issues): [What is the overarching conflict of the series?] Series arc: Issue #1 is the origin. Issue #2 is the escalation. Issue #3 is the confrontation. CHARACTERS: Protagonist — [Name]: [appearance, role, what they want, what they fear] Antagonist — [Name]: [appearance, role, their agenda] Supporting — [Name]: [appearance, role, relationship to protagonist] ART STYLE: [noir / manga / superhero / indie / watercolor / retro / webtoon / european] INK STYLE: [clean / brush / scratchy / technical / expressive] COLOR DIRECTION: [describe the overall palette — dark and desaturated / neon / warm / cold] ISSUE #1 STORY (22 pages): Act 1 (pages 1–7): [How the world is introduced, how the protagonist enters, the inciting incident] Act 2 (pages 8–17): [The escalation, what the protagonist discovers, the midpoint reversal] Act 3 (pages 18–22): [The climax, the cost, the cliffhanger that makes Issue #2 inevitable] CLIFFHANGER (final panel of page 22): [Describe the exact image and revelation that ends Issue #1] Remember these franchise continuity facts for the entire series: - [PROTAGONIST NAME] has [VISUAL DETAIL] — must appear in every panel - [ANTAGONIST NAME] has [VISUAL DETAIL] — never omit - [WORLD RULE] — applies to every scene set in [LOCATION] - Issue #1 ends with [CLIFFHANGER STATE] — this is the starting state of Issue #2 Plan the full 22-page Issue #1. Create all characters. Set art style, ink, and color. Build all pages with layouts, panel prompts, character assignments, dialogue, and per-page color scripts. Save all franchise facts to memory. Pre-fill the cover.
Paste this into the Narrator panel after completing Issue #1. Fill in every bracket with the actual state of your story at the end of Issue #1. The Narrator will save all of these as AI Memory entries — persistent continuity facts that will be injected into every future generation call for Issue #2. --- Issue #1 is complete. Before I start Issue #2, save all of these continuity facts to memory: CHARACTER STATE at end of Issue #1: - [PROTAGONIST NAME] is [physical/emotional state — injured? changed? what do they now know?] - [ANTAGONIST NAME] is [state — revealed? escaped? what did they do?] - [SUPPORTING CHARACTER NAME] is [state — alive? changed allegiance? missing?] INJURY FLAGS (must appear in Issue #2 until healed): - [CHARACTER NAME] has [injury description] on [body part] — introduced page [X] of Issue #1 - [CHARACTER NAME] is wearing [item] they picked up on page [X] — must carry it in Issue #2 WORLD-STATE CHANGES (locations that changed in Issue #1): - [LOCATION NAME] was [destroyed / revealed / changed] on page [X] — all Issue #2 scenes here must reflect this - [ORGANIZATION / FACTION] now knows [information] — affects all scenes involving them RELATIONSHIP CHANGES: - [CHARACTER A] and [CHARACTER B] relationship is now [new status] — affects all their dialogue in Issue #2 UNRESOLVED THREADS (setups from Issue #1 that must pay off): - [Thread 1 — what was set up and where] - [Thread 2] - [Thread 3] ISSUE #2 OPENING STATE: The story picks up [immediately / days / weeks] after the Issue #1 cliffhanger. [Describe exactly where the protagonist is and what they are doing in the first panel of Issue #2.] Save all of these as continuity memory. Confirm what you've saved.
Paste this into the Narrator panel after completing Issue #1. Fill in the brackets. The Narrator will design the cliffhanger ending for Issue #1 (if not already set), then plan the full 22-page Issue #2 — with all pages, layouts, panel prompts, character assignments, dialogue, and color scripts — picking up exactly where Issue #1 ended. --- Issue #1 of [SERIES TITLE] is complete. Here is the state of the story at the end of page 22: Protagonist status: [Where is [NAME] — physically and emotionally. What do they now know that they didn't at the start?] Antagonist status: [What has [NAME] done or revealed? Where are they?] World-state: [What has changed in the world because of Issue #1's events?] Unresolved: [List 2–3 things the reader doesn't know yet] The Issue #1 cliffhanger (final panel): [Describe the exact image — what the reader sees on the last page] Now plan Issue #2: [ISSUE #2 SUBTITLE]. Issue #2 story (22 pages): Opening (pages 1–3): Pay off the Issue #1 cliffhanger. [How does the protagonist respond to what just happened?] Act 1 (pages 1–7): [How does Issue #2 raise the stakes beyond Issue #1?] Act 2 (pages 8–17): [The escalation — what new threat or revelation changes everything? What is the midpoint?] Act 3 (pages 18–22): [The confrontation — what does the protagonist attempt? What does it cost them?] Issue #2 cliffhanger (page 22): [The revelation or reversal that makes Issue #3 inevitable — bigger than Issue #1's cliffhanger] Art style: [keep current / change to: ___] Color direction for Issue #2: [how should the palette shift from Issue #1 — darker? colder? more saturated?] Plan the full 22-page Issue #2. Use all characters and continuity facts already in memory. Build all pages with layouts, panel prompts, character assignments, dialogue, and per-page color scripts. Save a version checkpoint called "Issue 1 Complete" before starting.
system
8 prompts
workflow
9 prompts
architecture
10 prompts
prompts
26 prompts
templates
3 prompts
All 56 prompts across 7 modules are unlocked for your account.
Lifetime access