// Use when editing or reviewing TAAC docs, zensical configuration, generated site artifacts, GitHub Pages deployment workflows, docs CI behavior, or questions about whether documentation changes deploy correctly.
Use when: inspecting TAAC/Taiji platform pages on taiji.algo.qq.com, especially model training instances, checkpoint pages, metrics plots, TensorBoard-like scalars, browser MCP sessions, authenticated cookies, or direct platform API calls. Prefer API data over screenshots.
Use when changing TAAC PCVR experiment packages or shared PCVR runtime code under experiments/, src/taac2026/domain, src/taac2026/application, or src/taac2026/infrastructure, including model contracts, experiment discovery, packaging, training/evaluation/inference hooks, and accelerator-backed modeling behavior.
Use before running TAAC repository Python commands, pytest, console scripts, packaging/docs CLIs, or run.sh, and when working on local setup, uv/CUDA dependency flow, online training or inference bundles, package contents, platform Python execution, or environment/debug docs.
Use when Dev Container attach is slow, VS Code Remote Containers leaves stale helper processes, /tmp/.X11-unix has many displays, /root/.vscode-server has old versions/logs, or extension caches need safe cleanup inside a dev container.
| name | taac-docs-pages-pipeline |
| description | Use when editing or reviewing TAAC docs, zensical configuration, generated site artifacts, GitHub Pages deployment workflows, docs CI behavior, or questions about whether documentation changes deploy correctly. |
Use this skill to avoid stale-docs and Pages false positives. Treat workflow files, docs config, and touched docs as the source of truth.
docs/index.md for changed docs, when changing navigation or page roleszensical.toml, when changing navigation, assets, theme, or page paths.github/workflows/deploy-docs.yml and .github/workflows/ci.yml, when making claims about CI or Pages behaviordocs/guide/local-site.md, when changing local build, deployment, or generated-site behaviorindex.md pages are directional guides. Leaf docs should carry implementation details: commands, inputs/outputs, environment variables, source entrypoints, and failure modes.site/ is generated local output. Do not treat drift between docs/ and site/ as a GitHub Pages regression unless the user explicitly cares about committed static output.For docs content or zensical.toml changes:
uv run zensical build --strict
For workflow changes:
uv run --with ruff ruff check .github src tests
Only refresh or remove site/ when the user asks for generated output handling, or when a local docs command intentionally produced it.