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.
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.
11114d agoReviewMountCreate a free account to mount
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.
355mo 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.
17 projects use a version of this
27k8mo 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.
Write software documentation structured by Diátaxis. Use when the user wants a tutorial, how-to guide, reference page, explanation doc, or user guide — "write docs", "document this", "we need a guide for X". Not for READMEs (write-readme) or docstrings (update-docstrings).
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.
Write or update project documentation such as READMEs, setup and usage guides, and API references so it matches what the code actually does, with every command and example verified. Use when the user asks to write, update, or fix documentation, a README, or usage instructions. Do not use for code comments during feature work, changelogs for releases, or explaining code to the user in chat.
Create comprehensive technical documentation including API docs, component libraries, README files, architecture diagrams, and developer guides using tools like JSDoc, Storybook, or Docusaurus. Use when documenting APIs, creating component documentation, writing README files, generating API references, documenting architecture decisions, creating onboarding guides, maintaining changelogs, documenting configuration options, or building developer documentation sites.
2710mo 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).
Manage Taiga wiki pages and documentation using MCP tools. Use when: creating wiki pages, updating documentation, managing wiki links and navigation, tracking wiki changes, organizing project documentation.
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.