How to use this map
This is the top level. It does not teach any step. It tells you which stage you are in, what that stage has to settle, and which guide to open.
The order matters. Specify before you build, set the rules before the agent writes code, and publish before you automate. Skipping a stage does not save time; it moves the work to the stage where mistakes are expensive.
Three rules hold for every guide in the series, so they are written here once and not repeated. Mark what you do not know as unknown instead of letting a person or an agent invent it. Keep the first version small: every extra feature is another thing to check, own and fix. And keep decisions in files, not in chat history, because that is the only version an agent can read next week.
I built MagicBetting.BE this way myself, design to CI/CD: competitor-analysis-driven design, Codex writing the code section by section, PageSpeed tuning, deployment on Netlify, and a pipeline for content updates and vulnerability checks. Where a stage below describes something I did there, it says so.
Steps
Guide
- 1
1. Spec: decide what the site has to do
Read GuideSettle the job of the site before anyone opens an editor: what kind of site it is, who it is for, the smallest version worth publishing, and what it should be found for.
Guides: Prepare Website Inputs · Defining the Website Type · Identify Your Target Audience · How to Define MVP Website Functionality · Generate Keyword Ideas With AI · SEO, AEO, GEO: What To Prepare
- 2
2. Rules: tell the agent what it may do
Read GuideAn AI coding agent needs a constitution before it needs a task: which files it reads first, which file wins when two disagree, which work is packaged as a reusable Skill, and when it has to stop and ask.
Guides: Set Rules & Workflows · Codex Technical Setup · Pick the Source of Truth Before the First File · Reusable Skills: The Website Superpower · Footer Skill Setup
- 3
3. Build: produce the site from the spec
Read GuideThe agent implements what the first two stages decided. It starts from a template, applies the Skills, builds the pages, and then closes the gaps where separately built parts meet.
Guides: Build the Website · Closing Website Gaps With Codex Glue
- 4
4. Edit: fix what the build got wrong
Read GuideCheck the site before anyone else does: desktop, mobile, the paths a visitor actually takes, accessibility, and speed. The output is a short fix queue, not a redesign.
Guides: Review & Finalisation
- 5
5. Publish: put it live and make it measurable
Read GuideGoing live is more than a deploy: the site needs analytics behind consent, verified ownership in Google and Bing, and a sitemap that matches what you actually launched.
Guides: Website Intelligence Layer
- 6
6. CI/CD: keep it running without rebuilding it
Read GuideA published site is not finished. Content updates, scheduled publishing, dependency and vulnerability checks, and the context the next agent needs all belong to a pipeline, not to your memory.
Guides: Internal Links Under Control · Finalization and the Next Agent
Be Aware
Codex package updates can remove custom Skills.
If you create a Skill through Codex as a package, updates can delete custom Skills. Save every Skill in your chosen custom local folder, then point the agent to that folder explicitly.
The series is read as a list of articles instead of a route.
Start at the stage you are in. Each stage settles one decision, and the guides under it are the work. Reading ahead is cheap; building ahead is not.
