Documentation
Overview
This library contains 6 documentation-focused skills for building comprehensive documentation systems. Each skill provides patterns for generating, transforming, and publishing technical content across multiple formats and platforms.
Quick Start
# Browse available skills
ls skills/documentation/
# Read a skill
cat skills/documentation/mkdocs/SKILL.md
# Skills are documentation - integrate patterns into your build pipelines
Overview
Brief description of the topic.
Repo Markdown Save-and-Open Workflow
When a user asks to save an answer or evidence packet in a repository Markdown file:
- Locate or clone the target repository; if a previous partial clone is corrupt, create a clean shallow clone in a clearly named local repo directory.
- Save the Markdown near the source evidence when there is an obvious domain folder; use a descriptive filename rather than a temporary session name.
- Include relative links to source documents when possible, plus enough quoted evidence for the file to stand alone.
- Verify with
wc -landgit status --short -- <file>so the user knows the exact path and tracked/untracked state. - Open the file with VS Code using
code -g "$FILE:1"when available; fall back tocodium -gor report the saved path if no editor CLI exists.
Prerequisites
- Requirement 1
- Requirement 2
Version History
- 1.0.0 (2026-01-17): Initial release with 6 documentation skills
These skills enable documentation-as-code workflows, ensuring technical content stays synchronized with codebases and deployments.
Sub-Skills
- MkDocs Setup (+3)
- 1. Docs as Code (+1)
- Examples
- Common Issue 1
Sub-Skills
- Available Skills
- Static Site Generators (+2)
- Skill Selection Guide
- Project Structure (+3)
- Agenda
- Docusaurus Setup
- Integration with Workspace-Hub
- Step 1 (+1)
- 3. Automated API Documentation (+2)
- Testing Documentation
- Contributing
- Related Resources