h4tcher-docusaurus-generatorlisted

> Last updated: 2026-07-06 # Docusaurus Generator (hatch3r maintainer skill) This skill refreshes the **hatch3r project's own** documentation site, which already exists at `website/` (Docusaurus 3.x), by re-deriving its pages from this repository's canonical corpus. It is a framework-dev maintainer tool (hence the `h4tcher-` prefix per CLAUDE.md), not a generic per-project docs generator and not a lifecycle add/refactor/remove preset. It sources content from `agents/`, `skills/`, `rules/`, `commands/`, `hooks/`, and `docs/`; the only governance source is the public `governance/inventory.json` (counts). The site lives in `website/` and deploys to `docs.hatch3r.com` via `.github/workflows/deploy-docs.yml` on push to `main` (paths filter: `website/**`). There is no `docs-site/` directory — operate on `website/` directly. Do NOT run `npx create-docusaurus`: the project is already scaffolded; creating a second project is a P4 (Lean Coverage) violation. ## Workflow Overview 1. **Analyze** the hatch3r repo corpus to identify what each page must reflect 2. **Map** corpus sources to the existing `website/docs/**` page set and `website/sidebars.ts` 3. **Regenerate** the affected pages in place under `website/docs/` 4. **Build & Preview** via the website's own npm scripts ## Step 1: Analyze the hatch3r corpus Scan this repo to identify what each page must reflect: - **CLI surface**: the commands under `src/cli/commands/` (mirror the `npx hatch3r <cmd>` help) → `website/docs/refe