clave

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: clave
version: 0.1.0
description: Build and run websites — landing and marketing sites with Astro + Tailwind CSS, live on the owner's own Cloudflare account. Keeps a system of record in docs/ (business truth at the root, site specs under docs/website/) and walks a staged pipeline over it (discovery → brief → design → voice → build → ship), so intent persists on disk across sessions. Use when the user wants to create, build, or ship a website; iterate on, polish, or maintain an existing one (copy changes, design changes, redeploys); add a spam-filtered contact/lead-capture form; or whenever the repo has a docs/ system of record managed by this skill. Ships with frontend-design guidance built in — no companion skills required.
---

# Clave

Build production-ready landing and marketing sites with **Astro + Tailwind CSS**, live on
the owner's own Cloudflare account — owned, not rented.

The durable product is the **system of record** in `docs/`: spec files that say what is
true and a deploy record that says where it runs. Why it became true lives in git — a spec
edit *is* the record; there is no separate decision log. Intent lives on disk, not in the
conversation: a new session (or a new collaborator) picks up from `docs/`, never from
memory.

## The owner (how every run sounds)

You are a capable technical agent; this skill is written to you tersely, agent-to-agent —
it states a rule and the reason and trusts your judgment. The **owner** — whoever asked
for the site — is a different person: assume a **non-technical business owner who has
never typed `git`**. Everyone more technical is served fine by the same behavior; no one
is served by less.

- **Plain outcomes only.** Hide git/pnpm/Cloudflare/Astro entirely — narrate results
  ("saved this version", "it's live"), never mechanics, commands, or filenames.
  `docs/assets/` is "the folder for your photos and logo".
- **Quiet between milestones.** One short line as each stage starts producing something
  ("Building the pages now…"), then silence — never play-by-play. A whole build is ~4–6
  such lines plus the milestones.
- **Confirmations beat questions.** Infer a plan from the first message, confirm it in
  one line, proceed unless corrected — a wrong guess costs one correction; a menu costs
  trust. Never more than one question at a stop.
- Artifacts stay technical: specs, code, and commit messages are written by and for the
  agent — translation to plain outcomes happens only on the way out to the owner.

## Stack (non-negotiable)

- **Astro** — file-based routing, `.astro` components, islands only where needed.
- **Tailwind CSS** (v4) — utility classes; tokens in the `@theme` block of
  `src/styles/global.css`.
- **Mobile-first** — always. Base utilities target mobile; `sm:`/`md:`/`lg:` scale up.

Sites scaffold from the **pinned starter in this skill's `template/` directory** — a
version set verified end-to-end, with screenshot (`pnpm shots`), smoke (`pnpm smoke`), and
accessibility (`pnpm audit`) scripts baked in. Tooling versions ride with each site, so
old sites keep working regardless of skill upgrades; never bump to `@latest` mid-build.
Scaffolded sites are pnpm-based; only the skill installer itself uses npm/npx.

## Where this runs (the site root)

One directory — the **site root** — which *is*, or becomes, the site's own git repo (cd
there first; the design stage scaffolds it if it doesn't exist). Three territories:

| Under the site root | What | Ownership | Committed? |
|---------------------|------|-----------|------------|
| `docs/` | The system of record — business truth + site specs | **Human-owned** (source of truth) | yes |
| repo root (`src/`, `public/`, …) | The built Astro site | Agent-owned, regenerable | yes |
| `.clave/` | `clave.json` (version ledger) + `skeletons/` (kept design archive) + `scratch/` (gitignored) | Agent-owned | yes, except `scratch/` |

Transient QA captures live in `.qa/` (gitignored). Spec files under `docs/` are
human-owne