docs-guardian-for-claude

Use when generating or auditing documentation in Docusaurus format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in MkDocs format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in plain Markdown format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in Sphinx format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in VitePress format — covers config, directory structure, frontmatter conventions, and build commands.

Use when writing, auditing, or generating documentation for projects in unsupported languages — covers docstring conventions, API doc extraction, and generic heuristic patterns.

Use when writing, auditing, or generating documentation for Go projects — covers docstring conventions, API doc extraction, and Go-specific patterns.

Use when writing, auditing, or generating documentation for Python projects — covers docstring conventions, API doc extraction, and Python-specific patterns.

Use when writing, auditing, or generating documentation for Rust projects — covers docstring conventions, API doc extraction, and Rust-specific patterns.

Use when writing, auditing, or generating documentation for TypeScript projects — covers docstring conventions, API doc extraction, and TypeScript-specific patterns.

Use when detecting a project's programming language and documentation framework from filesystem markers — package.json, Cargo.toml, pyproject.toml, mkdocs.yml, etc.

Use when mapping source code files to their documentation counterparts — find which docs cover which code, detect gaps, and resolve doc-to-code relationships.

Use when evaluating documentation quality — check completeness, accuracy, freshness, and adherence to project documentation standards.