Produce and maintain the complete Markdown documentation set for an Odoo implementation - requirements, questions and decisions, fit-gap matrix, technical limitations, demo DB configuration log, project phases, detailed workflow explanations (why and how), step-by-step review guide and customization specifications - in the client's confirmed language(s).
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
Write, review, and audit code documentation to the standard the language and the project actually use — Python docstrings (PEP 257, Google, NumPy, reST), C and C++ comment blocks (Doxygen, kernel-doc), plus READMEs and API reference docs. Use this skill whenever the user asks to document code, add or fix docstrings or comments, explain a module so other developers can use it, write or refresh a README or API reference, check documentation coverage, or judge whether existing docs are still accurate — including short requests like "document this", "add comments here", "describe this module for the team", or handing over a file and asking what its docs are missing.
Documentation, prose, wording, terminology, examples. Apply concise evidence-driven writing conventions when enabled; use polish-docs for an onboarding redesign.
Use when writing, revising, reorganizing, or reviewing technical documentation — concept guides, feature docs, API references, developer-tool docs, tutorials, or docstrings that compile into user-facing docs. Covers both how to teach a single concept on one page and how to keep an entire documentation set coherent as it grows. Also covers short user-facing product text — UI copy, error messages, empty states, tooltips, and help text — which follows ASD-STE100 Simplified Technical English conventions (see "User-Facing Text"). Trigger whenever a task involves producing or improving end-user or developer-facing documentation, or when writing product strings a user will read. Not for README files (use crafting-effective-readmes), conversational walkthroughs of existing code or changes (use explain), or inline code comments.
813mo agoReviewMountCreate a free account to mount
Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when deciding documentation scope or creating or reviewing a technical document.
23611d agoReviewMountCreate a free account to mount
Bring README, CONTRIBUTING, the user guide and the roadmap current before a NanoLang release is tagged. Use when make release-docs-check names one of them, or when preparing a release by hand.
6284mo agoReviewMountCreate a free account to mount
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
2235d agoReviewMountCreate a free account to mount
Automate doc generation with JSDoc/TSDoc, linters, and pre-commit hooks. Use when setting up markdownlint, configuring doc linting pipelines, integrating JSDoc/TSDoc, or building automated documentation workflows.
2213d agoReviewMountCreate a free account to mount
Refresh the gobifrost site by re-capturing screenshots and (optionally) authoring missing pages. Trigger phrases - "refresh docs", "update screenshots", "/bifrost-documentation", "rebuild docs site". Has three modes - bootstrap (one-shot manifest generation, mandatory first run), diff (default - only refresh entries whose Bifrost source changed), full (re-capture and re-author everything).
645mo agoReviewMountCreate a free account to mount
Use when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since, @history), complete routine documentation (tables read/written, MV_* parameters, entry points, execution flow, dependencies), or REST API endpoint documentation (path/query parameters, request/response JSON, status codes). Also triggers on Portuguese phrasing like "documentar rotina", "gerar cabecalho Protheus.doc", "documentar endpoint", "documentar API REST", or requests to add documentation to legacy/undocumented code.
18348d agoReviewMountCreate a free account to mount
Use Antithesis documentation efficiently for product, workflow, and integration questions. Prefer the snouty docs CLI when available, and otherwise request markdown versions of documentation pages directly.
1.6ktodayReviewMountCreate a free account to mount
Update documentation affected by a completed task, after technical review and before the task is marked done. Use when review identifies documentation targets.
1926d agoReviewMountCreate a free account to mount
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
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.