What this guide builds
This is the top-level map for a Website Factory. It does not try to teach every footer, header, GPT, file, and review rule in one page.
The point is to make the system navigable. The first level explains the factory. The second level follows the real stages: prepare inputs, build reusable parts, set rules, build the website, and review before launch.
Steps
Guide
- 1
Prepare Website Inputs
Read GuidePrepare Website Inputs means collecting the source material before coding starts: website type, goal, content, audience, brand assets, functional scope, optional integrations, tracking, and SEO/AEO/GEO notes.
If the files do not exist yet, Prepare Website Inputs explains how to create a small preparation pack that reduces guessing before the first MVP build.
- 2
Build Reusable Website Parts
Read GuideBuild Reusable Website Parts means turning repeated components into Skills: header, footer, colors, typography, consent, metadata, FAQ, schema, sitemap, tracking, and final QA.
Skills define how repeated parts are implemented. They should not store one project's content or brand values.
- 3
Set Rules & Workflows
Read GuideSet Rules & Workflows means defining how the coding agent behaves and how repeatable production tasks run: what it reads first, what it may change, when it must stop, and how it reports finished work.
This prevents the agent from guessing, overbuilding, or ignoring the prepared files.
- 4
Build the Website
Read GuideBuild the Website is the production stage. The coding agent uses prepared files, reusable Skills, implementation rules, and a repository template.
It should not invent strategy here. It should implement what was already prepared.
- 5
Review & Finalisation
Read GuideReview & Finalisation means using Agent Mode as the final inspector, not the builder.
It should open the website, click through it, find broken or missing things, confirm what works, and give the coding agent a clean fix list.
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.
