{"enrichment":{"faq":[{"a":"Documentation Patterns provides a standardized README template with all essential sections for your project. The template ensures consistent structure across your documentation, making it easier for contributors and users to find information. Use the template to include overview, installation, usage, contribution guidelines, and licensing sections in a clear, organized manner.","q":"How to write a good README with documentation-patterns?"},{"a":"Documentation Patterns includes structured ADR templates following industry best practices. ADRs document architectural decisions in a consistent format, capturing the decision context, alternatives considered, and consequences. This structured approach helps teams record and communicate important technical choices, making it easier for new team members to understand the reasoning behind your system design.","q":"What is the architecture decision record format in documentation-patterns?"},{"a":"Documentation Patterns provides OpenAPI 3.1 specification templates for comprehensive REST API documentation. These patterns help you structure endpoint definitions, request/response schemas, authentication methods, and error handling in a standardized format. The OpenAPI approach enables automatic documentation generation and API client creation from your specifications.","q":"How do I document REST APIs using documentation-patterns?"},{"a":"Documentation Patterns includes changelog templates following semantic versioning conventions and Keep a Changelog standards. The templates help you organize release notes by version, categorizing changes as Added, Changed, Deprecated, Removed, Fixed, or Security updates. This consistent format makes it easy for users to track project evolution and understand what changed between releases.","q":"What changelog format best practices does documentation-patterns recommend?"},{"a":"Documentation Patterns provides technical writing style guidelines to maintain consistency across all project documentation. These conventions cover tone, terminology, formatting, and structure, ensuring your README, API docs, ADRs, and changelogs follow a unified voice. Applying these patterns helps onboard contributors and improves documentation quality across your projects.","q":"How can documentation-patterns help establish writing style conventions?"},{"a":"Documentation Patterns offers comprehensive templates and standards for project documentation including README structure, ADR format, OpenAPI 3.1 specifications, changelog conventions, and technical writing style. Licensed under MIT, these patterns help teams establish consistent documentation practices, making it easier to maintain quality documentation as projects grow and teams expand.","q":"What documentation standards does documentation-patterns provide?"}],"shadow_tags":["template-library","structural-guidance","release-documentation","api-specification","decision-capture","style-standardization","project-onboarding","technical-communication"],"summary_rewrite":"Documentation Patterns offers structured templates for READMEs, Architecture Decision Records, OpenAPI 3.1 specifications, changelogs, and technical writing conventions. Use this skill when establishing documentation standards, onboarding contributors, recording architectural decisions, or maintaining consistent API and release documentation across your projects."},"files":[{"bytes":3350,"path":"src/skills/documentation-patterns/SKILL.md","sha256":"ba437fc31422f0699b8f0ec1863645e6e2d48d874cdb7f1fec0319f15da01bb9","url":"https://skillfed.io/files/yonatangross/orchestkit/documentation-patterns/61c13226/SKILL.md"}],"id":"yonatangross/orchestkit/documentation-patterns","links":{"html":"https://skillfed.io/yonatangross/orchestkit/documentation-patterns","md":"https://skillfed.io/yonatangross/orchestkit/documentation-patterns.md","repo":"https://github.com/yonatangross/orchestkit"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":20,"language":"TypeScript","last_updated":"2026-07-28","license":"MIT","name":"documentation-patterns","publisher":"yonatangross","stars":208},"relations":{"categories":["technical-writing","documentation","devops"],"similar":[{"id":"yonatangross/orchestkit/release-sync"},{"id":"yonatangross/orchestkit/upgrade-assessment"},{"id":"yonatangross/orchestkit/database-patterns"},{"id":"yonatangross/orchestkit/architecture-decision-record"},{"id":"yonatangross/orchestkit/release-checklist"},{"id":"yonatangross/orchestkit/release-management"},{"id":"yonatangross/orchestkit/api-design"},{"id":"yonatangross/orchestkit/feedback"},{"id":"yonatangross/orchestkit/testing-patterns"},{"id":"yonatangross/orchestkit/prd-to-goal"}]},"slug":{"owner":"yonatangross","repo":"orchestkit","skill":"documentation-patterns"},"version":"61c13226"}