Verifies documentation accuracy by cross-referencing claims, CLI commands, API signatures, and configuration against source code. Use when validating documentation correctness or checking code-docs consistency. Flags unsupported or outdated claims.
Steady4 mentions in 2 weeks
1 project uses a version of this
1.3k8mo agoReviewMountCreate a free account to mount
Creates comprehensive API documentation including endpoints, parameters, authentication, request/response schemas, and code examples. Use when: documenting REST APIs, GraphQL interfaces, SDKs, or developer-facing technical specifications.
2547d agoReviewMountCreate a free account to mount
Write or restructure software documentation following the Diátaxis framework (tutorials, how-to guides, reference, explanation). Use when creating a documentation page or reorganizing existing docs, such as pages under packages/website/docs/.
1k12d agoReviewMountCreate a free account to mount
NVCF public docs style: short, plain, ASCII Markdown with no bold, emojis, em-dash, or en-dash. Use when editing public docs, READMEs, AGENTS.md, agent skills, plans, GitHub issues, or GitHub Pull Request descriptions.
2618d agoReviewMountCreate a free account to mount
Use when changing documentation ownership, generated agent guidance, review auto-fix guidance, the combined document+lint housekeeping pass, or the agent memory-file prompt rules.
No other project uses it yet
9.2k6d agoReviewMountCreate a free account to mount
Update durable engineering docs, navigation, and canonical source placement when they are stale, duplicated, or missing. Use for general docs work; feature specs and ADRs have dedicated skills.
5632d agoReviewMountCreate a free account to mount
name: documentation-discovery
description:
Essential guidelines instructing AI agents on how to incrementally discover,
read, and consult top-level monorepo documentation and example-specific
reference guides before altering code
Generates standards-based repository documentation for GitHub or any project. Writes a docs suite into the project's docs/ directory covering ISO 9001, V-Model, ISO 27001, and optionally GAMP 5 or other standards. Use when the user asks for repo documentation, compliance docs, quality docs, or to create/refresh the docs/ suite.
546mo agoReviewMountCreate a free account to mount
Use when adding or updating massCode documentation, documenting a new feature, changing docs website pages, adding docs assets, updating the VitePress sidebar, or adding README feature mentions.
7.1k2mo agoReviewMountCreate a free account to mount
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
Use when writing or modifying documentation, guides, or example READMEs. Covers documentation structure, writing style, formatting conventions, cross-referencing, and code example standards.
1324mo agoReviewMountCreate a free account to mount
Write API documentation for nvtripy following project conventions. Use when: writing docstrings for ops or modules, adding code examples, using @export.public_api document_under paths, creating Sphinx RST cross-references, understanding the docs build pipeline.
1288mo agoReviewMountCreate a free account to mount
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Create, expand, reorganize, and maintain repository documentation with deep coverage across README files, browsable docs, API/reference pages, llms.txt, llms-full.txt, changelogs, and repo-local agent skills. Use whenever the user asks for comprehensive project documentation, documentation refreshes, LLM-friendly docs, documentation synchronization after code changes, or agent guidance that teaches future LLMs how to use the project docs.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.