eBook Studio

Where this comes from

eBook Studio was designed by Hector Diaz for the AI Automations by Hector community, from a five-screen interface mockup and a set of research notes read from each store's own pages on 2026-10-05: Amazon KDP, Barnes & Noble Press, Etsy, Shopify, Gumroad, Stan Store, USPS, OpenRouter and Higgsfield. The promotion planner is built on the frameworks in Alex Hormozi's books $100M Offers and $100M Leads - the value equation, the Grand Slam offer and the Core Four - summarised in our own words, with the books credited by name.

Most of a self-published nonfiction book is the same work every time. The topic changes and the judgement changes; the rest is assembly: an outline, chapters in a consistent voice, bonuses, a cover that does not misspell its own title, an interior with the right margins, a spine as wide as the page count says, and a listing for each store. So the pack does not give you a book. It gives you sixteen prompts that build the app that makes books, and the app is yours, running on your laptop, with your own API keys.

What you build

When it runs, it feels like a small publishing house with one person in it. You type a topic, let the Niche Scout show you what people are searching for (every score labelled as an estimate, with its inputs on screen), or start from your own writing: a single line, a paragraph of notes, a few chapters or a whole draft, pasted or uploaded as .txt, .md or .docx, with a note on how you want the book. Your own chapters stay exactly as you wrote them and are marked "Your text"; the app proposes only the missing chapters, in a voice profile taken from your writing that you approve first.

You approve the outline. The chapters stream in one at a time. A Read mode shows the whole book in order; the editor has find and replace across the book, saved versions and undo; and the Fix tools - grammar and typos, clearer, longer, shorter, match my voice, and a full manuscript review - return every change as a proposal side by side. Nothing changes until you accept it. The model describes a wordless scene, Higgsfield paints it, and code typesets your title and author name, so the cover never misspells anything. Your photo, bio and imprint go on the back cover from Settings. Then the exporters build the EPUB, the eBook PDF, the 6x9 interior and a wraparound cover sized from the real page count.

What it deliberately does not do: it never publishes, posts or sends anything for you, and no outline, chapter, cover or listing goes into an uploadable file until you have approved it. It does not give legal, tax or medical advice, does not clear trademarks, and does not pretend a draft is finished. The book is yours to read, correct and stand behind.

Do you need this? Be honest first

If you want to write one book about your own expertise and you enjoy writing, use a word processor and an editor. This is for the person who wants a repeatable process: a coach or consultant turning what they teach into a lead magnet and a paperback, a creator who wants a book, a workbook and a mini course from one topic, or a builder who wants to understand how an AI app keeps a human in charge of every approval.

You are building a drafting tool, not a ghostwriter you can trust blind. If you plan to publish chapters you have not read, close the tab. KDP asks whether a book's content is AI-generated, and the app tells you how to answer it honestly.

What you need

• The machine. Any laptop. The app binds to 127.0.0.1, keeps each book as a folder on your disk, and needs no database and no Docker.
• The accounts. Claude Code logged in (Pro, Max or Team), Node and git. The setup guide starts at "open a terminal" on Windows (WSL2), a Mac with Apple Silicon, or Linux with Omarchy.
• The AI. OpenRouter for text: free models to start, credits when you write a book to sell. Higgsfield for cover art, pay as you go. A YouTube Data API key is optional for the Niche Scout. Every part has a keyless demo, so all sixteen prompts run for $0.
• The time. Setup in 30 to 45 minutes, then the sixteen prompts over five or six evenings.

The setup guide is one HTML file you open in a browser. Every command has a copy button, every step has a checkbox, and a progress bar shows how far along you are.

Print and ship at home: the gear list

The app's Print & Ship screen lists what you need to print, bind and mail your own copies, in three budgets. These are the matching product searches on Amazon. Prices change daily, so check them there. Under about a hundred copies a month, print on demand through KDP is usually cheaper per copy; printing at home makes sense for signed copies, workbooks, events and local sales.

Budget - booklets, workbooks and your first copies

• Monochrome laser printer with automatic duplex for interiors
• Ink tank color printer for covers
• 24 lb printer paper, case and 80 lb cardstock
• 12 inch paper trimmer, long reach stapler, bone folder and a pouch laminator
• Bubble mailers, a digital postal scale and packing tape with dispenser

Mid-range - real paperbacks in small batches

• High-yield laser printer and a wide-format ink tank printer
• Cream book paper and 100 lb cover stock
• Ream paper cutter, paper creaser and a hot glue perfect binder
• Roll laminator for cover film
• 4x6 thermal label printer, rigid book mailers and a 50 lb shipping scale

Pro - steady volume

• Office color laser printer for consistent covers
• Electric stack paper cutter and an electric creaser
• Professional perfect binder
• Industrial thermal label printer, custom printed shipping boxes and a tape gun

As an Amazon Associate I earn from qualifying purchases. The links are searches, not endorsements of one model: pick by reviews, warranty and the cost of toner or ink. The app itself carries no affiliate links; its Print & Ship screen opens this page.

What is in the zip

ebook-studio/
  README.md          the document: what you build, the gates, the paths, the folder map
  index.html         the clickable setup guide with all sixteen prompts (same as the browser link above)
  COSTS.md           every cost, with the date it was read
  DISCLAIMER.md       as is, no warranty, use at your own risk
  CREDITS.md         where the idea comes from, the as-is notice, what was verified
  paths/             one README per platform: Windows WSL2, Mac Apple Silicon, Linux Omarchy
  prompts/           00-project-brief ... 15-tests-and-smoke
  assets/            the cover art

What was verified and what was not

Read this first - distributed as is. This pack has not been run start to finish on a fresh machine. It is a proof of concept: the prompts were written against a reviewed design and the guide was checked in a browser, but nobody has yet built the whole app from prompt 00 to the last prompt in one sitting. There is no guarantee any step works on your setup. When something breaks, paste the full error into Claude Code and ask it to fix it, then post what broke and your platform in the community.

What was verified on 2026-10-05: the setup guide was opened in a real Chromium and driven by a script - the three platform tabs and their step counts, the progress bar, the checkboxes, progress saved across a reload, the copy buttons, every prompt matching its source file word for word, and the fallback copy path when the file is opened straight from disk. Twenty-five checks, all passing. Every text file was scanned for keys, private addresses and leftover placeholders before the zip was built. The sixteen prompts were read twice by a separate model (Codex), read-only: 35 findings on the first pass and 20 on the second, and a third pass read the 1.1.0 update (starting from your own writing, the editor and the Fix tools): 19 findings. Every one was triaged and its fate recorded, and the prompts were read in order again after each round, as a student would follow them.

What was not verified: the prompts as a sequence on a fresh machine, the three setup paths on three fresh machines, any provider against its live API, and any file the app makes against a store's own checker. Facts a store does not publish clearly - several fees, payout schedules and margins - show "check the current rate" in the app instead of a number.

Read the prompt before you run it

Hand each prompt to Claude first and ask what it plans to build. Compare that to what the prompt says. A prompt costs a minute to fix. A wrong build costs an afternoon.

Created by Hector Diaz for the AI Automations by Hector community.