← ClaudeAtlas

docs-sitelisted

Maintain the Zensical-powered documentation site — nav ordering in zensical.toml, the docs GitHub Pages workflow, CSS and JS assets, and link/anchor integrity across docs/**/*.md. Sibling of /techne:docsync (which only verifies prose claims against code). Use when the user wants the site itself audited — config, deploy pipeline, theming, assets, cross-page links — rather than content accuracy.
ajbarea/techne · ★ 0 · AI & Automation · score 75
Install: claude install-skill ajbarea/techne
# Docs-Site Audit and maintain the documentation site as a build/deploy artifact. `/techne:docsync` answers "does this claim match the code?"; `/techne:docs-site` answers "does this site build, deploy, render, and link correctly?" ## Repo context ```! cat .claude/skill-context.md 2>/dev/null || echo "(no .claude/skill-context.md — skill will use generic defaults for CSS/JS stack)" ``` The injected `## docs_site` section (if present) supplies this repo's CSS file list, JS file list, build command, site URL, and expected action pins. Use those over the generic defaults below when available. ## Surface - **`zensical.toml`** — nav ordering, palette, theme features, extra css/js, site URL, social links. - **`.github/workflows/docs.yml`** — trigger paths, `astral-sh/setup-uv` action, build invocation (from injected `docs_site.build_command`), Pages upload/deploy actions and versions. - **`docs/**/*.md`** — presence matches `nav` (including any nested sub-sections), internal links resolve, anchors exist, no orphan files. - **CSS files** — every file listed in `zensical.toml` `extra_css` exists on disk, and the selectors reference classes that actually appear in rendered output. The injected `docs_site.css_files` lists what to expect (single file vs. modular stack with components). - **JS files** — every file listed in `zensical.toml` `extra_javascript` exists on disk, no dead files. The injected `docs_site.js_files` lists what to expect. - **`docs/assets/`** — every asset is r