What this guide sets up
This is the set-the-rules-for-the-worker stage. The coding agent needs clear boundaries before it starts production work.
These rules prevent the agent from guessing, overbuilding, or ignoring the prepared files.
Steps
Guide
Agent Definition
Agent Definition states the agent role, write boundaries, allowed actions, validation duties, and things it must never invent.
Use it so the coding agent knows its job is implementation, not strategy.
Read Order
Read Order defines which sources the agent loads first: prepared inputs, reusable Skills, implementation rules, repo template, then task notes.
Use it so the agent does not start coding before it understands the context.
Memory Rules
Memory Rules define which decisions survive across runs, where they are saved, and when they should be updated.
Use them to preserve durable decisions without turning temporary chat into project truth.
Build Flow
Build Flow defines the production order: load inputs, apply reusable parts, build pages, add integrations, add tracking, run checks, and write notes.
Use it so the agent follows the same factory sequence every time.
Per-Run Checklist
A Per-Run Checklist defines sources read, files changed, checks run, issues found, and decisions updated.
Use it to make every agent run auditable.
Stop / Escalation Rules
Stop / Escalation Rules define when the agent must pause because information is missing, risky, legal, or outside the approved scope.
Use them to stop the agent from guessing through important decisions.
Recurring Checks
Recurring Checks define scheduled checks for broken links, metadata, tracking, sitemap, content freshness, accessibility, and dependency drift.
Use them so the website keeps being checked after the first build is done.
Be Aware
The agent starts coding before loading context.
Make read order part of the rules and require the agent to state which source files it used.
Return to the Main Guide?
Main guide
Start Your Website Factory
