sitekit is built to be driven by an AI agent, and the bundled skill is how the agent learns to do it. The skill is the operating manual the agent actually reads — not these docs. It ships inside the binary and installs into your harness with one command.
The skill is the agent-facing contract, and it ships in lockstep with the CLI — it can’t drift out of sync with the version you have installed. Whatever your installed sitekit can do, its skill describes.

Install it

sitekit init-skill --target claude-code
TargetDestination
claude-code~/.claude/skills/sitekit/
opencode~/.config/opencode/skills/sitekit/
path:<absolute-path>the path you give (any other harness)
Re-run with --force to refresh after upgrading the CLI.

What’s inside

The skill is a small directory: an entry-point SKILL.md plus a set of references/ files — the command reference, the content schema, the verify checks, error recovery, the playbook and shape and style-pack guides, and the per-loop workflows. The design is progressive disclosure: the agent reads SKILL.md first (the loop, the composition rules, the enforcement contract), then opens a specific reference only when the task calls for it. It never loads everything at once.

How the agent uses it

1

A trigger activates the skill

The skill’s description lists the phrases that should load it — “build a landing page,” “restyle my site,” “A/B test this headline,” and many more. When you say something that matches, your harness loads SKILL.md.
2

The agent reads the loop

SKILL.md teaches the decomposition (voice + style + shape + valence + content), the build loop, and which constraints are rigid versus free.
3

It opens references on demand

For specifics — a verify failure, the platform shape, the experiment loop — the agent opens the matching references/ file, applies it, and continues.
4

It runs the CLI and the verify loop

The agent emits pages, runs sitekit verify, reads each fix_hint, fixes, and ships — exactly the loop these docs describe, but executed by the agent.

The design helpers that ship with it

Installing the skill also co-installs two siblings (each non-fatally — a failure never blocks the sitekit install):

frontend-design

A design-taste skill for distinctive, production-grade interfaces. When a sitekit style pack is active, the pack wins — this guides pack-less and ephemeral work, and informs capture and authoring.

open-ui-component-catalog

A catalog of free, open-source UI libraries (shadcn/ui, Magic UI, Radix, Tailwind, Lucide, and more) the agent can reach for as raw material — always themed to the active pack.
Opt out with --no-design-skill and --no-component-catalog.

Keeping it current

When you update the CLI, refresh the skill so the agent learns any new commands:
sitekit init-skill --target claude-code --force

Command reference

The same surface, organized for humans.