Validates documentation structural integrity including heading hierarchy, metadata, file naming, navigation, and cross-references. Use when checking documentation organization or validating toctree structure.
Steady4 mentions in 2 weeks
3 projects use a version of this
1.3k9mo agoReviewMountCreate a free account to mount
Writes and reviews code documentation: dartdoc, JSDoc, Python docstrings, and implementation comments, with per-language conventions for Dart, Python, and TypeScript. Use when writing new code or features, documenting public APIs, improving existing docstrings or comments, or checking a change for missing or unhelpful documentation. Don't use for prose documents such as READMEs, design docs, or PR descriptions (use write-prose).
Technical documentation writing skill covering API reference guides, architecture documents, deployment guides, and operations manuals. Use this skill when creating technical documentation, writing API reference guides, drafting deployment guides, or need templates for operations manuals.
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.
11329d agoReviewMountCreate a free account to mount
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Generates project documentation including READMEs, docstrings (JSDoc, JavaDoc, Python docstrings), OpenAPI prose, and CI/CD doc pipelines. Use when asked to generate docs, write docstrings, automate documentation, or create README files.
356mo agoReviewMountCreate a free account to mount
Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
27k9mo agoReviewMountCreate a free account to mount
Author and validate Zero-Fluff technical documentation, root AGENTS.md, Google DESIGN.md alignment, Diátaxis guides, and Mermaid diagrams with strict conciseness caps and relative link verification.
3210d agoReviewMountCreate a free account to mount
Repository documentation placement and writing guidance. Use this skill whenever writing, modifying, reviewing, or planning README.md, anything under docs/, setup or installation instructions, troubleshooting or FAQ content, configuration references, operational guidance, or user-facing documentation in a feature or fix. Keep the README concise and put detailed material in its canonical documentation page.
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.
864mo agoReviewMountCreate a free account to mount
Add comprehensive documentation for the current code/feature and format it according to the ...; keywords: api, architecture, error. Use only on explicit request; skip in routine implementation discussions.
Automatically generate and maintain API documentation from code. Supports OpenAPI, AsyncAPI specifications and interactive documentation. Use when adding new endpoints, updating API contracts, or ensuring documentation consistency.
기술 문서를 자동 생성하고 관리합니다. "문서화", "README 작성", "docs 생성", "JSDoc", "API 문서", "변경 로그", "CHANGELOG", "온보딩 가이드", "기술 문서 업데이트" 등의 요청 시 사용합니다. README, API 문서, ADR, CHANGELOG, 온보딩 가이드를 코드베이스 분석 기반으로 생성합니다. (개발 일지·ADR·문제 해결 기록은 dev-journal 스킬 참조)
Use when a significant architecture decision that is hard to walk back is taken: the ADR template, what belongs there rather than in inline docs, and the never-delete-always-supersede rule.
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.