Set up your site with an AI agent

Sat, 04 Jul 2026 00:00:00 GMT

This starter is built to be handed to an AI coding agent. Every convention it
follows is written down in AGENTS.md,
so Claude Code, Codex, Cursor, or whatever you use can read the codebase, make it
yours, and keep the docs and the site in sync. Here's the whole loop.

1. Get the code

Use it as a template on GitHub, or start from the CLI:

npm create astro@latest my-site -- --template Zmoki/zmoki-astro-starter
cd my-site
npm install

2. Open it in your AI agent

Point your agent at the repo and let it read the two files that describe the
project: AGENTS.md (the technical spec) and
SETUP.md
(the checklist). Everything site-specific lives in src/site.config.ts, so most
of the work is one well-scoped file.

3. Make it yours

Work down SETUP.md with your agent. The essentials:

Identity. Set domain, name, and other things like the organization and
social links in src/site.config.ts.
Look. Check the brand pages at /-/astro/brand/ and run the /brand skill
to adapt the palette, fonts, and voice to your brand and needs. The whole site
and the OG cards follow.
Platform. Switch the deploy target and the image CDN by editing
src/site.config.ts. The redirects, headers, and CSP follow on the next build.
Content. Replace this post, add your own resources, and fill in the legal
pages. Ask your agent to draft them in your voice.

Because the brand system is a living style guide, you can just say "make the
accent green" or "switch the font to Inter" and the agent knows which files to
touch and how to keep the guideline honest.

[Image: Close-up of weathered tree bark, with a blurred sandy beach and blue sea in the gap beyond.]

Content images are hosted on a remote origin and optimized at build. Responsive `webp`, content-hashed, and served from your deploy host. The origin is decoupled from where the site deploys.

4. Run it

Ask your agent. The /run skill launches the dev server and verifies it is up:

$ claude
> /run

Prefer the classic way? npm run dev works too. Open the local URL and click
through. The site ships with a blog, resources, RSS, analytics, email forms,
structured data, and build-time OG images already wired. Nothing to bolt on.

5. Verify and deploy

Before you push, run the same checks CI does:

npm run format
npm run check
npm run lint
npm run build

After the build, CI also validates the structured data, internal links, and the
sitemap, so an SEO mistake turns the build red instead of shipping.