Documentation System

Apply documentation standards and templates to codebase docs folders.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/hhopkins95/ai-systems --skill documentation-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Documentation System
Source: https://github.com/hhopkins95/ai-systems/tree/main/plugins/smart-docs-authoring/skills/documentation-system
Command: npx skills add https://github.com/hhopkins95/ai-systems --skill documentation-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides standards and templates for documenting codebases, enabling consistent, AI-navigable documentation and easier maintenance across system, packages, and guides.

Core Features & Use Cases

  • Folder structure under docs/ with system/, packages/, guides/ and index.md entries
  • Templates for system docs, package docs, guides, and index docs
  • Maintenance guidance to keep docs aligned with code changes
  • Guidance on where to place new docs and how to cross-link

Quick Start

Choose a doc type (system, package, or guide) and create your first document using the appropriate template from references/templates/, then add an index.md for navigation.

Frequently Asked Questions about Documentation System

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

FAQPage Schema
How do I structure documentation for AI tools to navigate my codebase?

Documentation structured with opening descriptions, sections, diagrams, code examples, and cross-references enables AI navigation. The Documentation System provides templates for system, package, and guide docs organized under a docs/ folder hierarchy with index.md entries for consistent, scalable documentation suitable for both human readers and AI processing.

What's the best way to standardize docs across system, package, and guide folders?

Apply the Documentation System templates to standardize writing, reviewing, and maintaining content across docs/system/, docs/packages/, and docs/guides/. Each folder uses role-specific templates with structured sections, maintenance workflows, and cross-linking guidance to ensure consistent quality and easier updates as code changes.

How do I keep documentation aligned with code changes?

The Documentation System includes maintenance guidance and workflows that govern how to update and review docs when code changes. Regular alignment prevents documentation drift and keeps references, examples, and cross-links current across system, package, and guide documentation.

Can I use templates to create consistent package and system documentation?

Yes. The Documentation System provides ready-to-use templates in references/templates/ for system docs, package docs, guides, and index docs. Start by selecting your doc type, using the appropriate template, and adding an index.md for navigation to establish consistency from the first document.

Do I need a specific folder structure for codebase documentation?

The Documentation System requires a docs/ folder with three subfolders—system/, packages/, and guides/—plus index.md entries at each level. This hierarchical structure enables logical organization, cross-referencing, and AI-friendly navigation of your documentation.

What makes documentation AI-navigable versus human-readable only?

AI-navigable documentation uses consistent structure, clear opening descriptions, semantic section headers, inline code examples, and explicit cross-references. The Documentation System applies these patterns systematically across your docs/ folders so AI systems can parse intent and relationships alongside human comprehension.