astro-conversion-kit — скилл

---
name: convert-site
description: Convert a live website (WordPress first; Drupal, Webflow, Squarespace, Wix and static sites too) into a static Astro site with the same URLs, content, head tags, media, redirects and look, proven by parity gates and a pixel-level visual review, ending in one pull request, a noindexed staging deploy and a launch runbook. Use when asked to convert, rebuild, migrate or clone a site to Astro, when handed a site URL with this kit's link, to resume a conversion from .conversion/state.json, or with --apply <id> to apply one suggestion as a proposal.
---

# convert-site

The orchestrator. It asks one message of questions, then runs every other skill in order without
stopping again, and ends with a pull request the person merges and a runbook they launch from.

## The golden rules

1. **One intake message, then no stops.** Every question carries a default. Anything that later
   needs an account, a login or a token you do not have goes on the "needs you" list
   (`state.needsYou` and `docs/LAUNCH.md` section A) and the run carries on.
2. **The live site is read-only.** Only these read it, paced: the capture scripts, `shoot.mjs`
   and `styles.mjs` on live, `css-coverage.mjs`, `launch-audit --old-url` and `pre-launch
   --predecessor-url`. Analytics are blocked on their live page loads, so no visit is counted.
   Never submit a form on it, log in, or fetch a page by hand to fill a gap.
3. **The default build equals live, faults included.** Content is moved from captured markup,
   never retyped or tidied. Every oddity is a decision row that says "reproduce live by default".
   A forced difference is an exception; an improvement is a proposal (`PROPOSALS=on` only).
4. **Gates on every commit, never softened.** Never edit `baseline/` to pass (only the `keep`
   flags in `baseline/scripts.json`). A skip is not a pass; "Not covered" is never a pass.
5. **`main` gets the scaffold commit and nothing else.** On a new, empty repository init-site
   makes one commit on `main`, the exception to "never commit to main": the PR needs a base.
   Everything after it is on `astro-rebuild`, one PR. Never force-push, never merge, never
   touch DNS, the old host or a dashboard setting.
6. **No secrets in chat or in the repository.** Never ask the person to paste a token.
   Credentials come from the environment or a CLI's own login.

## Names used below

`KIT` is the absolute path of this kit (the folder holding `skills/` and `package.json`).
`LIVE` is the live origin. `SITE` is the absolute path of the new site repository (default
`<current folder>/<slug>`); the capture and the run state are written into it from the start,
and `init-site.mjs` scaffolds around them. Run every command from `SITE`. Every script prints
`--help`; run that rather than reading the source. Every Node command in a fresh shell starts
with `source ~/.nvm/nvm.sh && nvm use 22.23.4` (or runs in a shell that reads `.nvmrc`).

## Step 0a: a kit that can run

The scripts import `parse5`, `playwright` and the rest from the kit's `node_modules`. If
`$KIT/package.json` or `$KIT/node_modules` is missing (an install that copied only the skill
folders has neither), clone the kit and install it, then use the clone as `KIT`: