Hi HN, I m Stefan, CTO at amaiko (https://amaiko.ai). We build our agentic AI platform with Claude Code, so we built our own website the same way, then generalized it into an MIT-licensed Astro template, passionfruit. Our partner PASSION4IT moved several WordPress sites onto it (passion4it.de is live on it today): ~€26.5k/yr of hosting plus a contracted WP developer dropped to ~€0, and one non-technical person now maintains all their sites part-time.It s for bilingual (DE/EN) marketing sites you set up and maintain by talking to Claude Code instead of editing code: `pnpm create passionfruit my-site`, then `/onboard`.The interesting part is making a codebase an LLM can maintain without quietly breaking it. Agents ship plausible-looking garbage, so the repo is mostly build gates that fail instead of trusting the model:- a bilingual gate (no half-translated site can ship) and a fixture-leak gate (a scaffold can t go live as the placeholder) - strict TypeScript over the frontend and the Cloudflare backend, alt-text as an error, a CSP that blocks any un-allowlisted script host - for what gates can t see, like layout and spacing, Claude Code drives the dev server with Playwright and screenshots its own outputThe result is a plain static Astro 7 site (zero JS by default, near-perfect Lighthouse, JSON-LD/hreflang/WCAG AA) you can still edit by hand or hand to any dev. Nothing locks you in beyond the authoring workflow.Demo: https://passionfruit.passion4it.de Code: https://github.com/passion4it-gmbh/passionfruitFeedback welcome, especially the build gates so an agent can t ship junk idea. Right approach, or over-built?