documentation-engineer

Automate API documentation creation and maintenance with OpenAPI integration.

68|6|Updated Apr 16, 2020
One-click install
npx skills add https://github.com/zenobi-us/dotfiles --skill documentation-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-engineer
Source: https://github.com/zenobi-us/dotfiles/tree/main/ai/files/skills/experts/developer-experience/documentation-engineer
Command: npx skills add https://github.com/zenobi-us/dotfiles --skill documentation-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps create, maintain, and evolve developer-facing documentation systems—API docs, tutorials, and reference material—while keeping content in sync with code, improving discoverability and usability.

Core Features & Use Cases

  • API documentation automation and OpenAPI integration
  • Documentation architecture design and cross-referencing
  • Tutorial creation, code examples, and interactive playgrounds
  • Multi-version docs, localization, and analytics
  • Use Case: You need a single source of truth for API docs synchronized with code changes.

Quick Start

Generate an OpenAPI spec from codebase and scaffold a MkDocs/Docusaurus-based docs site with search and versioning.

Frequently Asked Questions about documentation-engineer

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

FAQPage Schema
How do I automate API documentation from OpenAPI specs?

API documentation automation extracts your OpenAPI specification and generates complete reference docs with examples, versioning, and search. This keeps docs synchronized with code changes and eliminates manual API documentation maintenance across updates.

Can I use Docusaurus or MkDocs to build developer documentation?

Both Docusaurus and MkDocs are supported frameworks for building scalable developer documentation. They provide markdown-based workflows, built-in search, versioning, and mobile-responsive output ideal for API docs, tutorials, and multi-version content.

How do I ensure API documentation stays in sync with code changes?

Documentation-as-code workflows treat docs as versioned artifacts alongside source code. By linking OpenAPI specs and code examples directly to your codebase, updates trigger automated doc regeneration, ensuring 100% API coverage and tested working examples.

What's the best way to structure multi-version documentation?

Multi-version docs organize content by release, enabling users to access relevant docs for their implementation version. Frameworks like MkDocs and Docusaurus support version switching, branching strategies, and persistent URLs across major releases.

Do I need to manually write code examples for API documentation?

Code examples can be generated and validated automatically from your codebase or OpenAPI definitions. Automated extraction and testing ensures examples remain functional and current, reducing manual authoring overhead while maintaining accuracy.

How can I add search and localization to developer docs?

Full-text search and localization are core features of modern doc platforms. Implement search indexing for discoverability and configure language-specific content delivery to support global developer audiences across regions.