docs-as-code

# Docs-as-Code Skill

## When to Use This Skill

Use this skill when:

- **Docs As Code tasks** - Working on documentation pipeline automation and docs-as-code workflows
- **Planning or design** - Need guidance on Docs As Code approaches
- **Best practices** - Want to follow established patterns and standards

## Overview

Implement documentation-as-code workflows with automated pipelines, version control, and CI/CD integration.

## MANDATORY: Documentation-First Approach

Before implementing docs-as-code:

1. **Invoke `docs-management` skill** for documentation patterns
2. **Verify tooling versions** via MCP servers (context7 for docusaurus/mkdocs)
3. **Base guidance on current best practices**

## Docs-as-Code Philosophy

```text
Docs-as-Code Principles:

┌─────────────────────────────────────────────────────────────────────────────┐
│  1. Version Control                                                          │
│     - Docs live alongside code in the same repository                        │
│     - Changes tracked with meaningful commit messages                        │
│     - Branch-based workflow for documentation updates                        │
├─────────────────────────────────────────────────────────────────────────────┤
│  2. Review Process                                                           │
│     - Pull requests for documentation changes                                │
│     - Technical review by subject matter experts                             │
│     - Style review by technical writers                                      │
├─────────────────────────────────────────────────────────────────────────────┤
│  3. Automated Testing                                                        │
│     - Linting for style and grammar                                          │
│     - Link validation                                                        │
│     - Build verification                                                     │
├───────────────────