These guides are for people doing the work. They cover repository setup, instruction scope, static rendering, deployment boundaries, and verification. If a step does not need a client framework or server runtime, the guide will say so.
Start with a build path
Start with the guide that matches the next irreversible decision. Agent guides cover context and implementation. The Cloudflare guide begins at the deployment boundary. The AGENTS.md guide defines the repository rules that should survive both workflows.
The common sequence
Begin with the brief and repository rules. Inspect the existing system before editing. Make the smallest coherent change. Run targeted checks while working, then the full release suite. Review the output in the browser and in generated HTML. Only then commit or deploy.
That sequence sounds ordinary. It is also where many agent-led builds fail: the result is judged from a screenshot while the route graph, document head, error states, and production headers remain untested. The problem library makes those hidden gaps easier to recognize.