Documentation practices — comment guidelines, ADR conventions, API documentation, inline docs philosophy, doc health scanning and maintenance. USE WHEN documentation, write docs, comment guidelines, ADR, architecture decision, API docs, JSDoc, OpenAPI, document code, when to comment, how to document, self-documenting code, README, doc health, doc drift, stale docs, fix docs, doc maintenance, check docs.
Use when writing or updating specs, READMEs, API/reference docs, ADRs, or runbooks — record an ADR per decision, update docs when a feature ships, fix drifted docs.
Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs
Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs
Documentation strategy and artifact-selection protocol. Use when updating README/changelog/docs, choosing timestamped vs cumulative records, or producing validation and fixes-applied artifacts after substantive changes.
Documentation audit, writing and upkeep - starts from who needs which answers (new contributor, operator, API consumer, user, coding agent), maps the docs that exist, checks them against the code for accuracy, and finds what is missing, misplaced or stale. Writes README, guides, reference, decision records, runbooks and agent files on approval, marking anything the code cannot prove. Stack-agnostic.
Technical documentation workflow for capturing work done — decisions, commands, issues, and resolutions — into structured Markdown notes saved to an Obsidian vault.
Writing documentation people actually read — READMEs, API docs, ADRs, comments, changelogs, and technical writing style. Use when writing any docs, README, comments, or explaining a system in writing.
Defines authoring, multi-version tabbing, multi-SDK code example, and diagram standards for the A2UI developer site (docs/site/). Use when creating, editing, or reviewing public documentation, conceptual guides, tutorials, or quickstarts.
Surging38 mentions in 2 weeks
1 project uses a version of this
17k10d agoReviewMountCreate a free account to mount
Specialized skill for creating and editing high-quality Kener documentation. MUST be used whenever creating or editing documentation files in the src/routes/(docs)/docs/content/ directory or updating docs.json navigation.
Steady3 mentions in 2 weeks
42 projects use a version of this
5.2k8mo agoReviewMountCreate a free account to mount
Enforces project documentation style guide compliance for tone, voice, terminology, punctuation, and formatting. Use when checking documentation style or validating MyST/reST syntax. Cites specific style guide violations.
Steady3 mentions in 2 weeks
4 projects use a version of this
1.3k8mo agoReviewMountCreate a free account to mount
How to write and maintain package-level (package-info.java) and module-level (module-info.java) Javadoc in JabRef, including deep links into devdocs.jabref.org. Use when adding a package or changing a package's or module's public surface.
No other project uses it yet
4.9k5mo agoReviewMountCreate a free account to mount
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
mj-devingSkill
