Guide sets up AI-ready web stack with AGENTS.md and Cloudflare Workers

The guide's structure follows the order a new project actually moves: local tools, UI and code-quality setup, database, AI instructions, repository, hosting, CI/CD, production settings and first release. Each phase ends with a concrete check, so the reader can confirm the environment works before inviting an AI agent to write features. The two-track split matters because the demands differ: a SaaS app needs routing, database and authentication, while a landing page can stay largely static. In both cases the guide keeps the number of moving parts low by relying on managed services and avoiding a custom API server or ORM. A recurring theme is separation — production data is never put into development, environment variables starting with VITE_ are treated as public, and migrations are run as a separate step from frontend releases. The AGENTS.md file is presented as the contract that keeps AI-generated changes inside these boundaries, with lint, type check, tests and review still applied to whatever the agent produces.