Skip to content
Back to skills

Documentation Patterns

ASecurity

Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.

  • 285 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
developmentgoapisecuritydocumentation

Works with

  • claude code
  • api

Security analysis

A100/100

Pro scans all 9 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add yonatangross/orchestkit --skill documentation-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Documentation Patterns?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Documentation Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yonatangross-documentation-patterns/badge)](https://www.skillsdirectory.com/skills/yonatangross-documentation-patterns)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: documentation-patterns
license: MIT
compatibility: "Claude Code 2.1.277+."
description: Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
user-invocable: false
disable-model-invocation: true
context: inherit
effort: low
allowed-tools: "Read Glob Grep"
metadata:
  version: "1.0.0"
  author: "OrchestKit"
  complexity: "low"
  tags: "documentation, readme, adr, api-docs, openapi, changelog, writing-style, technical-writing, ci-cd"
---

# Documentation Patterns

Templates and opinionated structures for technical documentation -- READMEs, Architecture Decision Records, OpenAPI specs, changelogs, and writing style. Each category has individual rule files in `rules/` loaded on-demand.

## Quick Reference

| Category | Rule | Impact | When to Use |
|----------|------|--------|-------------|
| [README](#readme) | 1 | HIGH | Starting a project, onboarding contributors |
| [ADR](#architecture-decision-records) | 1 | HIGH | Recording architecture decisions |
| [API Docs](#api-documentation) | 1 | HIGH | Documenting REST APIs with OpenAPI 3.1 |
| [Changelog](#changelog) | 1 | MEDIUM | Maintaining release history |
| [Writing Style](#writing-style) | 1 | MEDIUM | Any technical writing task |

**Total: 5 rules across 5 categories**

## Quick Start

```markdown
## README Skeleton
# Project Name
Brief description -> Quick Start -> Installation -> Usage -> API -> Config -> Contributing -> License

## ADR Format
# ADR-001: Title
Status -> Context -> Decision -> Consequences (positive/negative) -> References

## OpenAPI Minimum
openapi: 3.1.0 with info, paths, components/schemas, error responses

## Changelog Entry
## [1.2.0] - 2026-03-05
### Added / Changed / Deprecated / Removed / Fixed / Security

## Writing Rule of Thumb
Active voice, present tense, second person, one idea per sentence
```

## README

Complete README template with all essential sections for open-source and internal projects.

- **`docs-readme-structure`** -- Project name, quick start, installation, usage, API reference, configuration, contributing, license

## Architecture Decision Records

Structured format for capturing architectural decisions with context and consequences.

- **`docs-adr-template`** -- Status, context, decision, consequences (positive/negative), references

## API Documentation

OpenAPI 3.1 specification patterns for consistent, machine-readable API docs.

- **`docs-api-openapi`** -- Path structure, operation definitions, schema components, error responses (RFC 9457)

## Changelog

Keep a Changelog format for curated, human-readable release history.

- **`docs-changelog-format`** -- Added, Changed, Deprecated, Removed, Fixed, Security sections with semver

## Writing Style

Technical writing conventions for clear, scannable documentation.

- **`docs-writing-style`** -- Active voice, present tense, concise sentences, API doc checklist

## Related Skills

- `ork:api-design` -- API design patterns (complements OpenAPI documentation)
- `ork:architecture-decision-record` -- ADR workflow and lifecycle
- `ork:release-management` -- Release process including changelog updates

**Version:** 1.0.0 (March 2026)

Files in this skill

  • SKILL.md3.2 KB
  • rules/_sections.md1.2 KB
  • rules/_template.md338 B
  • rules/docs-adr-template.md2.6 KB
  • rules/docs-api-openapi.md3.5 KB
  • rules/docs-changelog-format.md2.5 KB
  • rules/docs-readme-structure.md2.4 KB
  • rules/docs-writing-style.md3.2 KB
  • test-cases.json3.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.