Get the base

The goal of this step is to get book-studio onto your computer. book-studio has almost no external dependencies like publish scripts, so once you get it you move straight to the next step. Usually done within 10 minutes.

1) Get the base

If you have a license and Template access, use “Use this template” to make your own repository, then clone it. Otherwise, get it directly with git clone.

cd ~/projects
git clone https://github.com/ddakit/book-studio.git my-book
cd my-book

If the ~/projects folder doesn’t exist, run mkdir -p ~/projects first. You can rename my-book to whatever you like.

Normal screen: a line starting with “Cloning into ‘my-book’…” shows, and after a moment the prompt returns.

Stuck screen:

• “command not found: git” → git isn’t installed. Go back to the git item in prerequisites.
• An auth request → if it’s a private repository, you need to be logged into GitHub. Using your own repository URL made via Template is cleaner.

2) Step into the folder you got

cd my-book
ls

If you see names like AI_AUTOMATION.md, CLAUDE.md, and .claude/, you got it right.

3) Dependencies to install

book-studio needs no separate package install. Claude Code does the writing, and book outputs pile up as markdown under _workspace/. It’s a product with no publish scripts or build tools, so after getting it you go straight to /start.

4) first-run handles git history separation

When you get the base with git clone, the base’s commit history comes along. It’s cleaner to cut the history before your own chapter commits pile on top, but that spot is something the next step’s /start detects automatically and asks about once. No need to do it by hand now.

Next

Once you’ve got it, go to first-run. You set the book identity with /start.