docs

Update repository documentation with overviews, interface examples, Mermaid diagrams, and references.

56|2|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/matteing/opal --skill docs-matteing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/matteing/opal/tree/main/.claude/skills/docs
Command: npx skills add https://github.com/matteing/opal --skill docs-matteing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the repository's docs/ directory current and accurate so that explanations, interfaces, and architecture descriptions do not drift from the codebase as features are added, changed, or removed.

Core Features & Use Cases

  • Evergreen docs: Update or create explainer pages for major features and subsystems to reflect current behavior.
  • Style and organization: Enforce a consistent format with one-paragraph overviews, interface examples, how-it-works sections, Mermaid diagrams for architecture, and a references section.
  • Use cases: Update docs when a feature is added or modified, document new tools under docs/tools, and revise pages touched by pull requests that change documented behavior.

Quick Start

Use the docs skill to update or create the docs/ explainer for a changed or new feature, including a one-paragraph overview, interface examples, a how-it-works section, Mermaid diagrams, and references.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I keep project documentation accurate when adding new features?

To keep project documentation accurate when adding features, update the docs directory to reflect current behavior. This ensures architecture descriptions and interface examples do not drift from the codebase as the project evolves.

What is the best way to organize technical writing in a repository?

Organize technical writing in a repository by enforcing a consistent format with one-paragraph overviews, interface examples, how-it-works sections, Mermaid diagrams, and references. This prescribed file organization keeps developer documentation evergreen.

How do I generate Mermaid diagrams for architecture documentation?

Generate Mermaid diagrams for architecture documentation by creating or revising how-it-works sections within the docs directory. These diagrams visually explain subsystem behavior and ensure architecture descriptions match the codebase.

When do I need to update docs for a pull request?

You need to update docs for a pull request when the changes modify behavior described in existing documentation. Revising the touched pages ensures the explainer remains evergreen and accurately reflects the new codebase behavior.

Does this documentation style guide work for new developer tools?

Yes, this documentation style guide works for new developer tools by creating explainer pages under the docs/tools directory. It enforces a consistent format including overviews, interface examples, and references for each tool.