documentation-standards

Enforce documentation standards for AWS Coworker components with Markdown conventions.

1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/jason-c-dev/aws-coworker-enterprise --skill documentation-standards-jason-c-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-standards
Source: https://github.com/jason-c-dev/aws-coworker-enterprise/tree/main/skills/core/documentation-standards
Command: npx skills add https://github.com/jason-c-dev/aws-coworker-enterprise --skill documentation-standards-jason-c-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation standards provide a unified approach to writing, structuring, and maintaining AWS Coworker documentation so teams can find information quickly and stay aligned.

Core Features & Use Cases

  • Establishes a consistent documentation structure across components (agents, skills, commands, guides).
  • Enforces Markdown and style guidelines to improve readability and maintainability.
  • Enables automated reviews, cross-reference guidance, and versioned documentation.

Quick Start

Review this repository's documentation standards and apply them to every new or updated document.

Frequently Asked Questions about documentation-standards

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

FAQPage Schema
How do I enforce consistent documentation standards across multiple components?

Apply unified documentation standards to agents, skills, commands, and guides to enforce consistent structure, formatting, and versioning across components. This improves clarity and maintainability by validating frontmatter, markdown conventions, and cross-references.

What are the best markdown style guidelines for repository-level documentation?

Markdown style guidelines for repository-level docs should enforce consistent formatting, frontmatter validity, and cross-reference accuracy. Setting these standards ensures readability and maintainability, enabling automated linting and reviews across all new and updated documents.

How do I automate documentation reviews for markdown formatting and frontmatter validity?

Automate documentation reviews by applying standards that support automated linting of markdown conventions and frontmatter validity. This process checks structure, formatting, and versioning across agents, skills, commands, and guides to maintain safety and accessibility guardrails.

Can I use these documentation standards for existing guides and agents, or only new ones?

Documentation standards apply to both new and updated documents across all components, including existing agents, skills, commands, and guides. Reviewing and applying these standards to current repository-level docs ensures ongoing clarity, consistent cross-references, and versioned maintainability.

Why do I need versioning and cross-reference guidance in documentation standards?

Versioning and cross-reference guidance in documentation standards ensure teams can find information quickly and stay aligned as components evolve. Enforcing these guidelines maintains structural integrity across agents, skills, and guides while supporting future extensibility and automated reviews.