Rules and logic for creating, managing, and closing project documentation (tasks, journals, ADRs), conformant with the Open Knowledge Format (OKF v0.2). Activate this skill when creating new tasks, distilling chat sessions into journals, closing tasks, or maintaining index.md/log.md files.
Rules and logic for creating, managing, and closing project documentation (tasks, journals, ADRs), conformant with the Open Knowledge Format (OKF v0.2). Activate this skill when creating new tasks, distilling chat sessions into journals, closing tasks, or maintaining index.md/log.md files.
Guides writing or revising technical docs for a named reader — README, tutorial, how-to, API reference, docstrings, runbook, package docs, or vignettes. Use when drafting or updating documentation for a specific audience.
Author and verify documentation, diagrams, and programmatic office documents. Use for docs verification, runbooks, ADRs, guides, Mermaid diagrams as code, ASCII and terminal figures, code snippet images, PDF/DOCX generation, and OpenAPI reference. Trigger on 'document this', 'write a runbook', 'draw a diagram', 'generate a PDF', 'are these docs still true'.
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.
Enforce minimum documentation standard across uFawkes* repos. Use when auditing a repo before release, onboarding a new repo to the suite, or implementing roadmap item 0.6 (cross-repo README links). Directly supports DORA AI Capability 3 and the 2023 DORA finding that documentation quality amplifies all technical capabilities.
Craft phase 9 - refresh affected documentation pages, tick the backlog entry under guard, fold in-scope findings into the PR and defer the rest to impact triage; runs in parallel with the background validation run.
Writes or reviews developer documentation in the project style with SEO guidance. Use when adding, changing, or removing content in a docs page, a README, an option or API description, a guide, a FAQ, or a blog post, even when the request only says "document this".
Documentation toolkit, one skill with sub-skills. (1) doc-style: write and build documentation for any work product (API, deploy or update, system, feature, release, test round) in one house style, seven fixed skeletons, a TH Sarabun theme with change highlighting, and a matching PDF + DOCX from one Markdown source; (2) pdf-operations: merge, split, extract, reorder, rotate or overlay PDF pages through an existing pdf-lib pipeline instead of reimplementing it. Use WHENEVER the user wants to document, write up, report on or hand over something ("write an API spec", "เขียนเอกสาร", "ทำรายงานอัปเดต", "make a user guide", "changelog for this release", "export as PDF and Word"), make a document match the house style, or merge / split / rotate / stamp PDFs. Read the sub-skill's SKILL.md before acting.
Expert technical documentation architect specializing in developer experience, API portals, interactive documentation, and documentation-as-code strategies.
Documents code the way the language's own toolchain expects: the native doc format per language, contract-first doc comments on every public symbol, module-level overviews, examples the test suite runs so they cannot drift, and inline comments that explain why rather than what. Use whenever code is written, added, refactored, or reviewed, whenever a public API changes, and whenever asked to write, fix, or review comments, docstrings, doc comments, or API reference documentation.
Durable Documentation
**Status:** experimental.
Governs durable, edited repository knowledge. Unlike the append-only log, documentation is actively edited as plans and decisions evolve.
## Directory Structure
A project managed by Agent
Generate or improve documentation for code, APIs, architecture, or processes. Use when the user asks to document something, create a README, write ADRs, or explain code.
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.