renderlisted

# Render — HTML Generation Take a `tour-spec.json` and produce a single-file `index.html`. This skill is deterministic; the heavy lifting is in `${CLAUDE_PLUGIN_ROOT}/scripts/render.cjs`. ## Trigger phrases - "render the tour" - "regenerate the HTML" - "update the embedded sources" - Auto-dispatched at the end of `learning-guide:analyze` ## Inputs - **Spec path** — `tour-spec.json` location. Default: CWD; explicit path supported. - **Output directory** — defaults to the spec's parent dir. ## Steps 1. **Locate the spec.** If the user provides a path, use it. Otherwise look for `tour-spec.json` in CWD. If neither, ask the user where the spec is. Do NOT scan the entire repository. 2. **Confirm Node is available.** Run `node --version`. If exit code is non-zero, tell the user Node.js must be on PATH and stop. Do not attempt fallback rendering. 3. **Inspect overrides.** Look for `<spec-dir>/.learning-guide/template.html`. If present, ensure `tour-spec.renderer.template_compatibility_version` matches the `<!-- template_compatibility_version: N -->` declaration on the override's first line. If missing or mismatched, ask the user to fix it before rendering. 4. **Run the renderer.** ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/render.cjs" "<spec-path>" ``` If `--output-dir` is needed, pass it explicitly. 5. **Surface output.** On success, print the renderer's stdout summary verbatim. On non-zero exit, print stderr verbatim and offer the troubleshooting table from