gabe-docsitelisted

Publish docs onto the project's HTML site — pick the section, wire the nav, render with working diagrams. Renders INTO a command center's shell when one exists (one site, one skin, one sidebar) and extracts the references a page makes so both link directions are derived. Markdown stays the source of truth; it places and renders, never fact-checks.
khujta/gabe-suite · ★ 0 · Data & Documents · score 63

Install: claude install-skill khujta/gabe-suite

# gabe-docsite — publish a doc into a browsable HTML site **Usage:** `/gabe-docsite <what to document, or 'add the doc I wrote at docs/src/X.md'>` ## Gabe execution contract (E1–E7) This skill runs under the suite execution contract — E1 EVIDENCE · E2 RUN-BEFORE-✅ · E3 NO SILENT DOWNGRADE · E4 REUSE FIRST · E5 STATE SYNC · E6 MISSING ANCHOR = STOP · E7 REPORT WHERE — floors, not ceilings; a skill's own gate may be stricter, never looser. Full text: `../gabe-docs/references/execution-contract.md` (if that file is missing, E6 applies — STOP). > **One line:** take a document (one you wrote, or one to author) and put it on the project's **HTML docs site** in the *right place* — the correct section, at the correct disclosure level — then render it so it displays anywhere, including straight off disk (`file://`). It is **not** responsible for whether the doc matches the code; accuracy/drift is owned elsewhere (`/gabe-docs`, reviews). Here we care about: *where does this belong, how is it structured, and does it render.* ## The site this skill operates A **self-contained, dependency-free static HTML site**, viewable over `file://`, generated from markdown — never hand-written. It builds in one of two modes, and **the build states which one it took**. ### CENTER MODE (default where a command center exists) ``` build_docsite.py --config docs/docsite.config.py \ --shell docs/center/shell \ --nav docs/site/center/nav.json ``` Doc pages rend