documenter
Documenter
Documentation workflow for repo docs, technical writing, and inline API comments.
Priorities
- keep docs accurate, scannable, and current
- identify audience, document type, and source of truth before drafting
- prefer examples and concrete structures over vague prose
- match README/docs to actual build, test, install, and release behavior
- keep public API comments complete enough for generated docs
- keep one document one job; link to neighboring docs instead of mixing modes
Not For
- binary document manipulation such as
.docx,.pdf,.pptx, or.xlsx - tiny typo, grammar, or copy edits that do not require document-type decisions, repo-truth checks, or restructuring
- regulatory document-control systems, compliance programs, or quality records
More from n-n-code/n-n-code-skills
project-vendor-boundary
Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.
19coding-guidance-cpp
C++ implementation and review skill. Use when writing, modifying, refactoring, or reviewing C++ code, especially modern C++17/20/23 code that needs strong ownership, type safety, and testable design. Portable across C++ repos and build systems.
18project-platform-diagnose
Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.
18security
Security workflow skill for repo-grounded threat modeling, exploit-focused security review, and secure-by-default implementation guidance. Use when the user explicitly asks for security work, or when security properties are the primary concern in a high-risk change. Do not trigger for ordinary code review, routine endpoint work, or general backend implementation just because a repo contains APIs, auth, or secrets.
18project-release-maintainer
Overlay for release-facing docs, install layout, workflows, licenses, and hygiene scripts. Portable across repos with a release/packaging pipeline. Use for publication-facing changes.
17project-core-dev
Overlay for day-to-day feature work and bug fixes in repo-owned code. Provides a validation checklist for build, test, format, and analysis. Use alongside the repo's principle skill.
17