tdm_rulesgen

Use when adding, renaming, reordering, or linking Rulesgen public docs that flow to the tdm-docs Docusaurus site and tdspora.ai. Covers the import pipeline, sidebar/.order mechanics, the "link locally until published" rule, and the lychee link-check and docs-contract validation battery.

Use for authoring or updating Rulesgen documentation — public docs (`docs/public/`), repo-root design docs, contributor docs, sample READMEs, and the glossary. Produces testable, glossary-aligned, link-integral docs.

Use for testing Rulesgen documentation — executes Markdown code fences via Sybil, validates link integrity, lints glossary usage, and cross-checks docs against Settings, schemas, and routes.

Use for authoring, reviewing, or correcting natural-language → Python generation DSL rules for Rulesgen.

Use for implementing production-grade Rulesgen features or non-trivial code changes.

Use for Pydantic v2 validation errors, DSL parser/validator rejections, and API request validation issues in Rulesgen.

Use for FastAPI route, middleware, lifespan, dependency injection, or Problem Details response issues in Rulesgen.

Use to verify or set up the local Rulesgen development environment (uv venv + all extras synced from the lockfile). Run this if any subsequent command fails with `ModuleNotFoundError`, `command not found`, or "no such tool installed", or before running quality gates on a fresh checkout.

Use for GitHub Actions CI failures (ruff, mypy, pytest, uv build, pip-audit, semantic-release) in Rulesgen.

Use when a coding or testing session reveals that a Rulesgen harness file (rule, skill, agent, or doc) is inaccurate, incomplete, or blocking correct work. Requires human approval before any harness file is changed.

Use for release readiness, packaging, versioning, wheel, or dependency validation in Rulesgen.

Use for selecting the correct test, lint, type-check, or packaging command for a given Rulesgen change.