sitekit is an alignment layer for building websites with an AI agent — not a website generator. The agent writes every line of HTML, CSS, and TypeScript. sitekit gives it a versioned playbook (a brand voice, a visual style, a page shape), scaffolds the project, and runs a verify loop that holds the output to that playbook. What comes out reads like it was designed for you, on purpose — and it stays that way as your business changes.
“Build the marketing site — editorial style, our voice.” “The pricing page header looks broken on mobile — fix it.” “We just shipped SSO. Work it into the site.”
You don’t run the commands. You talk to your agent; the agent runs sitekit; sitekit keeps it on-brand and structurally sound.

Install sitekit

The binary, the agent skill, and everything you need on a fresh machine.

Build your first site

Init a project, hand it to your agent, verify, deploy.

​
Why sitekit

Ask any AI to “build me a website” and the result is usually fine — but generic. Stock phrasing, a look like every other AI-built site, images that don’t quite exist, sections that don’t quite fit your business. sitekit gives the agent a brand kit, a structural rulebook, and an automatic quality check, so it works inside those constraints instead of improvising.

Designed, not generated

A voice pack (tone + forbidden phrases) and a style pack (real CSS — type, color, motion) the agent can’t reinvent. The output looks deliberate because it is.

It has to pass verify

After every change, sitekit runs around fifty automatic checks — brand rules, required sections, mobile, accessibility, real images. Each failure says exactly what’s wrong and how to fix it.

Real images only

sitekit refuses invented image paths. You bring real images, search a stock library, or have the agent generate new ones — but they have to actually exist.

Keeps up with the business

Edit one section and prove nothing else moved. Cascade a reposition across pages. Run an on-brand A/B test. The first build is the start, not the end.

Works on sites it didn't build

Point sitekit at a site you already run — WordPress, Squarespace, a custom build — and keep it on-brand without rebuilding or moving it.

Yours to keep

One command deploys to Cloudflare Pages. The result is plain static files you own — cancel anytime and the site keeps serving.

​
How it works

You install two things once, then drive everything by talking to your agent:
1

Install the binary

A single self-contained executable — no Node, no source clone. See Installation.
2

Install the agent skill

sitekit init-skill teaches your agent (Claude Code, OpenCode, or any compatible harness) how to drive the CLI. Your agent reads the bundled manual and just knows the commands, conventions, and what to do when something fails verify.
3

Talk to your agent

Describe what you want. The agent reads the playbook, emits pages with sitekit run, runs sitekit verify, fixes what it flags, and ships with sitekit deploy. You watch and steer.

​
The four loops

A site has a life beyond launch day. sitekit is built around four loops — your agent reaches for the right one when you describe the task in plain language.
LoopYou sayThe agent runs
Build”Build the marketing site.”init → run → verify → deploy
Maintain”Fix this section / restyle / what’s drifted?”inspect → reconcile → verify --maintenance
Experiment”A/B test this headline; ship the winner.”experiment new → start → status → promote
Evolve”We repositioned — update the whole site.”brand evolve → record → reconcile --brand-delta

Start here

The Quickstart walks through your first site end to end — install, init, hand it to your agent, verify, deploy.
sitekit is the engine behind Auxon — “powered by sitekit.” These docs are for people running the sitekit CLI directly with their own agent.