documentation-patterns

Provide structured patterns for organizing technical documentation.

8|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill documentation-patterns-bradtaylorsf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-patterns
Source: https://github.com/bradtaylorsf/alphaagent-team/tree/main/plugins/aai-docs/skills/documentation-patterns
Command: npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill documentation-patterns-bradtaylorsf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating clear, organized, and user-friendly documentation by providing established patterns and guidelines for structuring various types of documentation.

Core Features & Use Cases

  • Documentation Structure: Offers examples for project and API documentation layouts.
  • Writing Patterns: Introduces techniques like the Inverted Pyramid and Progressive Disclosure for clarity.
  • Formatting Guidelines: Specifies best practices for code blocks, tables, callouts, and links.
  • Use Case: A new developer joins a project and needs to understand how to document their code. This Skill provides them with a clear template and best practices for creating effective READMEs, API docs, and guides.

Quick Start

Use the documentation-patterns skill to generate a README.md file for a new project.

Frequently Asked Questions about documentation-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best patterns for organizing technical documentation?

Effective documentation organization relies on structured patterns like the inverted pyramid and progressive disclosure to arrange content. These writing patterns help structure reference, conceptual, and procedural documentation for maximum clarity and user comprehension.

How do I structure API documentation for a new project?

Structure API documentation by separating content into reference, conceptual, and procedural types. Utilizing established documentation patterns ensures your API docs include properly formatted code blocks, tables, and links for developer readability.

How do I write a README using progressive disclosure?

Write a README using progressive disclosure by presenting essential information first, then revealing deeper details as needed. This documentation pattern, combined with the inverted pyramid approach, prioritizes critical setup instructions before moving to complex configurations.

What is the difference between conceptual and procedural documentation?

Conceptual documentation explains how a system works and its underlying architecture, while procedural documentation provides step-by-step instructions for completing specific tasks. Effective documentation patterns utilize both alongside reference materials for complete project coverage.

What are the formatting best practices for markdown documentation?

Formatting best practices for markdown documentation include using well-structured code blocks, clear tables, and descriptive links. Applying these formatting guidelines alongside structural patterns ensures your technical documentation remains readable and user-friendly.