From an empty repository to a live website: a recipe
Someone asked on r/ClaudeCode how to make a theme for a brand website when none of the ready-made ones fit. Our answer there was short:
Ask Claude to create for you a design system for your website. Describe what the website does and what you want. Ask it to generate 3-4 different options for you to choose between. Give it a sense of your taste for how you want it, point it to sites you like. Ask it to give you options for typography, colors. From then on, iterate.
This post is the long version: the same advice, run through Zeus Mode for Claude Code and Codex, from an empty repository to a site that is live. It works like a recipe. Each step says what to run, what to type, and what comes back to you.
One thing first, said plainly: these steps come from our guides, Getting started and Planning with metis. We have not yet recorded a run of this exact build. When we do, we will post it, with the numbers. Until then, if a step does not go the way it says here, tell us.
What you need
- A Mac with macOS 14 or newer.
- Claude Code (or Codex).
- A GitHub account, and
gh, GitHub’s command-line tool:brew install gh. - Zeus Mode:
brew install zeus-mode/tap/zeus
Or download it from zeusmode.ai/download. Open it once: its first screens set it up on your Mac and sign in gh for you.
The shape of it
Four agents, in this order:
| Step | Agent | What it does | What it leaves behind |
|---|---|---|---|
| 1 | daedalus | Thinks the site through with you, design included | A plan document, plan.md |
| 2 | metis | Turns the document into a plan of steps | A plan in Zeus Mode, P-n, and its tasks on the board |
| 3 | prometheus | Builds the worker that will build the site (a step of the plan) | A worker agent, through one pull request |
| 4 | coordinator | Runs the plan, starting each step’s agent for you | The site, through one pull request to main |
You start daedalus, metis and the coordinator. You answer their questions. You merge every pull request that reaches main.
Step 0: an empty repository
gh repo create my-brand-site --public --clone --add-readme
cd my-brand-site
A public repository is the simplest place to host the site later, with GitHub Pages.
Step 1: daedalus shapes the idea
zeus run daedalus
Daedalus says who it is, and asks for the idea. Its first question wants two things: the idea in one sentence, and what matters most to you. Give it both. Our example is a made-up studio:
New idea: a one-page website for Kettle & Clay, a small studio that sells
handmade ceramic mugs. Visitors should see the work, read the story behind
it, and find the shop. What matters most to me is that it feels calm and
handmade, not like a template.
Then do what the Reddit answer said, one message at a time. Describe the taste, and ask for options:
Before we decide anything, propose a design system for the site:
3 or 4 different options for me to choose between. For each one give me
the typography (a heading font and a body font), the colours (background,
text, one accent), and one sentence on the feeling it gives.
Sites I like, and what I like about each:
- <site 1>: the amount of white space
- <site 2>: the serif headings
- <site 3>: product photos that fill the width
Use these as taste, not as something to copy.
I like option 2. Keep its fonts, but try two warmer accent colours.
Daedalus keeps all of this in one running document, a single page with a poster drawn beside it. When a question needs research, such as which fonts are free for a commercial site, it names the topic and asks first. Say:
Yes, run it.
Every sitting ends with one pull request for the page, and one question: go on, shelve it, or hand it to metis. Merge the pull request. When the design and the pages are settled, say:
Hand it to metis.
Daedalus writes plan.md, and ends with the next step: next: run metis — zeus run metis — and give it <path>.
Step 2: metis writes the plan
zeus run metis
Metis asks what matters most to you in the plan, then how you want to start. Give it the document:
Here is the document: <the path daedalus gave you>.
Then tell it how you want the work cut:
This repository has no worker agent yet. Make the first step prometheus
building one: a site builder that works on the HTML, CSS and images, and
whose done is a page that opens in a browser with no errors.
After that: the design options as real pages, my pick, the pages, and the
deploy to GitHub Pages.
Metis drafts the whole plan and shows it to you once, as a page, in plain words. For this site it would look something like this:
| Step | Kind | Whose |
|---|---|---|
| Build the site-builder worker | task | prometheus |
| The design options, as real pages | task | site-builder |
| Pick a design | gate | you |
| Build the pages | task | site-builder |
| Turn on GitHub Pages and bring the site’s address | handoff | you |
| Deploy | task | site-builder |
| Live | milestone | — |
A gate is a question only you answer. A handoff is something only you can bring, here a link. The metis guide lists all six kinds of step.
One honest note on the first row. The metis guide says only an agent your repository declares can take a step, and prometheus comes built into Zeus Mode rather than declared. In our own repository prometheus takes plan steps: plan P-44 had three. If metis shows the step as “nobody yet”, run zeus run prometheus yourself first, merge its pull request, and give the step to the worker it built.
When the plan reads right:
Approve.
Metis writes the plan into the repository in one pull request. Merge it: the steps that build things wait for that merge. Then it asks “Shall I set P-n in motion?”:
Yes.
Every task goes on the board for its agent.
Step 3: the coordinator runs it
In a second terminal, in the same repository:
zeus run coordinator P-n
P-n is the plan’s number, which metis told you. If it asks whether to start metis, because no metis is serving the plan, say:
start Metis
From here the two run side by side. The coordinator starts each ready step’s agent as a worker inside its own session: first prometheus, then the site builder. When a worker has a question, it goes to metis first, and metis answers from what you already decided. Only what metis cannot answer comes to you, in Needs you in the Zeus Mode app, with metis’s recommendation.
Each worker opens one pull request to the plan’s own branch, and the coordinator merges it there. Two things will come to you on the way:
- Pick a design. The site builder makes the options as real pages. Open them, then answer the gate: approve the one you want, or say what to change.
- The site’s address. On GitHub, open the repository’s Settings → Pages, turn Pages on, and bring the address back to the plan.
One note from prometheus’s own rules: a worker needs a way to check its work. A fresh site has no test command, so prometheus will say so in its pull request and suggest one as the worker’s first task. Take it. It is what lets the coordinator trust each pull request before it merges one.
At the milestone, the coordinator opens one pull request from the plan’s branch to main. That one is yours. Merge it, and the deploy step’s work goes live.
Step 4: iterate
The Reddit answer ended with “From then on, iterate.” Two ways to do that:
- A small change, such as a colour, a line of copy or a new photo: start the worker and say it.
zeus run site-builder
Make the accent colour a shade warmer, and check the contrast of the
buttons against the background.
- A bigger change, such as a new page or a new section: start daedalus again. It lists the ideas already there; continue the same one, and hand it to metis when it is ready.
What Zeus Mode never does for you
- It never merges to main. Every merge to main is yours.
- It never answers a gate for you, such as the design pick.
- It never starts daedalus or the coordinator. You do. The coordinator starts metis only when you say so.
- It never decides that an idea is ready. “Hand it to metis” is your sentence.
Try it
Zeus Mode is a Mac app: download it here. Start with Getting started, then Planning with metis. The posts on daedalus, metis and the coordinator each give four things to say to that agent.
If you build a site with this, we would like to see it. And if a step falls short, tell us where at hello@zeusmode.ai.