home / skills / yuniorglez / gemini-elite-core / docs-pro

docs-pro skill

/skills/docs-pro

This skill manages the lifecycle of technical documentation with AI-driven syncing, style enforcement, and modular content for rapid, accurate DaC updates.

npx playbooks add skill yuniorglez/gemini-elite-core --skill docs-pro

Review the files below or copy the command above to add this skill to your agents.

Files (8)
SKILL.md
4.4 KB
---
name: docs-pro
id: docs-pro
version: 1.1.0
description: "Senior Technical Writer & Docs Architect. Expert in AI-driven documentation synchronization, style guide enforcement, and 2026 Markdown standards."
---

# 📚 Skill: docs-pro (v1.1.0)

## Executive Summary
`docs-pro` is a comprehensive skill for managing the lifecycle of technical documentation. It bridges the gap between raw implementation and user-facing clarity. In 2026, we treat **Documentation as Code (DaC)**, using AI to ensure that every new feature, configuration, and API change is accurately reflected in our docs within minutes of a commit.

---

## đź“‹ Table of Contents
1. [Core Capabilities](#core-capabilities)
2. [The "Do Not" List (Anti-Patterns)](#the-do-not-list-anti-patterns)
3. [Quick Start: The Sync Audit](#quick-start-the-sync-audit)
4. [Standard Production Patterns](#standard-production-patterns)
5. [Documentation Quality Standards](#documentation-quality-standards)
6. [AI-Driven Documentation Workflow](#ai-driven-documentation-workflow)
7. [Reference Library](#reference-library)

---

## 🚀 Core Capabilities
- **Automated Sync Audit**: Scanning codebases for undocumented exports, settings, and flags.
- **Style Enforcement**: Ensuring all documentation follows the 2026 Squaads AI Style Guide.
- **Modular Content Architecture**: Managing reusable snippets and modular pages for scalability.
- **Multimodal Documentation**: Integrating diagrams (Mermaid), code examples, and interactive elements.

---

## đźš« The "Do Not" List (Anti-Patterns)

| Anti-Pattern | Why it fails in 2026 | Modern Alternative |
| :--- | :--- | :--- |
| **"Click Here" Links** | Bad for accessibility and AI context. | Use **Descriptive Anchor Text**. |
| **Outdated Defaults** | Leads to user frustration and support tickets. | Use **Docs Sync Audit** to verify defaults. |
| **Manual Reference Docs** | Impossible to maintain at scale. | Generate API refs from **Code Docstrings**. |
| **Wall of Text** | Low information retention. | Use **Bullet Points, Tables, and Diagrams**. |
| **Mixing Languages** | Makes maintenance and translation hard. | Keep English as the **Source of Truth** in `docs/`. |

---

## ⚡ Quick Start: The Sync Audit

Perform a basic check to see what's missing in your documentation:

```bash
# 1. Analyze changes in current branch vs main
git diff main...HEAD -- src/

# 2. Search for common undocumented patterns
rg "export (const|function|class)" src/ --type ts

# 3. Compare findings with docs/ structure
ls -R docs/
```

---

## đź›  Standard Production Patterns

### Pattern A: The Feature Release Doc
When implementing a new feature, follow this checklist:
1.  **Overview**: What does it do?
2.  **Configuration**: List all environment variables and settings.
3.  **Examples**: Provide "Quick Start" and "Advanced" code blocks.
4.  **Troubleshooting**: Common errors and their fixes.

### Pattern B: The API Reference Update
Instead of editing `docs/ref/*.md` directly:
1.  Update the JSDoc/TSDoc comments in the source code.
2.  Run the doc generator (e.g., `make build-docs`).
3.  Verify the output matches the **Markdown Standard**.

---

## 📏 Documentation Quality Standards

We adhere to strict standards to ensure high utility for both humans and AI agents.

- **Clarity**: Active voice, present tense, and direct address.
- **Accuracy**: Code examples must be tested and valid.
- **Discoverability**: Every page must be listed in `mkdocs.yml` with a descriptive title.

*See [References: Style Guide](./references/style-guide.md) for more.*

---

## 🤖 AI-Driven Documentation Workflow

1.  **Inventory**: AI scans the codebase to build a feature list.
2.  **Gap Analysis**: AI compares the inventory to existing `.md` files.
3.  **Drafting**: AI proposes new content based on implementation logic.
4.  **Review**: Human-in-the-loop verification of tone and accuracy.

*See [References: AI Collaboration](./references/ai-collaboration.md) for more.*

---

## đź“– Reference Library

Detailed deep-dives into documentation excellence:

- [**2026 Style Guide**](./references/style-guide.md): Voice, tone, and structural rules.
- [**Markdown Standards**](./references/markdown-standard.md): Frontmatter, code blocks, and AI-friendly syntax.
- [**AI Collaboration Guide**](./references/ai-collaboration.md): How agents and humans work together on docs.
- [**Coverage Checklist**](./references/doc-coverage-checklist.md): The master list for doc audits.

---

*Updated: January 22, 2026 - 17:05*

Overview

This skill is a Senior Technical Writer & Docs Architect agent that automates Documentation as Code workflows. It enforces 2026 Markdown and style standards, runs sync audits to find undocumented code, and produces modular, AI-assisted drafts ready for human review.

How this skill works

The skill scans repositories to inventory exports, configuration flags, and public APIs, then compares that inventory to the docs directory to surface gaps. It can generate draft pages or snippets following the 2026 Squaads AI Style Guide, manage reusable content modules, and validate generated Markdown against the agreed standard.

When to use it

  • On feature branches before release to ensure docs are updated
  • During continuous integration to run automated sync audits
  • When converting monolithic docs into modular, reusable content
  • To produce or refresh API reference pages from code docstrings
  • For enforcing style and discoverability rules across the docs site

Best practices

  • Treat English docs/ as the single source of truth and keep translations downstream
  • Run the sync audit as part of your CI pipeline for each merge to main
  • Edit source docstrings or code comments, then regenerate API reference rather than hand-editing ref files
  • Keep examples tested and minimal—provide both Quick Start and Advanced snippets
  • Use modular snippets and include them via your documentation toolchain to avoid duplication

Example use cases

  • Feature release workflow: run a sync audit, generate a Feature Release Doc checklist, and produce Quick Start + Troubleshooting sections
  • API reference generation: update JSDoc/TSDoc in source, run the doc generator, and validate output against Markdown standards
  • Docs modernization: break a large page into modular components, migrate diagrams to Mermaid, and enforce style rules
  • CI integration: fail builds on missing docs for exported symbols or mismatched defaults
  • AI-assisted drafting: have the agent draft missing pages and hand them off for a human tone and accuracy review

FAQ

What does the sync audit check for?

It detects undocumented exports, config flags, environment variables, and files referenced in code that lack corresponding documentation pages.

How do I keep generated references accurate?

Update code docstrings (JSDoc/TSDoc), run the doc generator, and include a validation step to compare generator output to the Markdown standard before merging.