mkdocs-documentation

star 0

MkDocs Material documentation management. This skill should be used when writing, formatting, or validating documentation in docs/. Covers admonitions, Mermaid diagrams, code blocks with annotations, content tabs, navigation setup, include-markdown for reusable content, _includes pattern for shared diagrams, and mkdocs testing. Always check project-specific docs at docs/dev/ai/skills/ and docs/dev/ai/agents/ for project-specific Claude skill and Claude agent documentation when available.

kettleofketchup By kettleofketchup schedule Updated 4/5/2026

name: mkdocs-documentation description: MkDocs Material documentation management. This skill should be used when writing, formatting, or validating documentation in docs/. Covers admonitions, Mermaid diagrams, code blocks with annotations, content tabs, navigation setup, include-markdown for reusable content, _includes pattern for shared diagrams, and mkdocs testing. Always check project-specific docs at docs/dev/ai/skills/ and docs/dev/ai/agents/ for project-specific Claude skill and Claude agent documentation when available.

MkDocs Material Documentation

Write and maintain documentation using MkDocs Material in the docs/ directory.

Project-Specific Claude Documentation

Always check first for project-specific Claude configurations:

  • docs/dev/ai/skills/SKILL-NAME.md - Project-specific Claude skill docs
  • docs/dev/ai/agents/AGENT-NAME.md - Project-specific Claude agent docs

These take precedence over general patterns.

Quick Reference

Task Reference
Callout boxes admonitions.md
Flowcharts, diagrams diagrams.md
Syntax highlighting code-blocks.md
Multi-option examples content-tabs.md
Links, nav structure navigation.md
Reusable content includes includes.md
Build, validate testing.md

Diagram Rules

REQUIRED SUB-SKILL: Use mermaidjs-v11 for all Mermaid diagram creation.

Diagrams with more than 15 nodes or lines must be split:

  1. Create a top-level overview showing high-level blocks only
  2. Create per-component deep-dives with internal details
  3. Store each diagram in docs/architecture/_includes/ as a separate .md file
  4. Reference from pages using {% include-markdown %} directives
  5. Add hide: true to _includes/.pages to exclude from navigation

See includes.md for the full pattern.

Common Patterns

Admonition with Code

!!! example "Usage"

    ```python
    from module import func
    func()
    ```

Tabbed Content

=== "pip"

    ```bash
    pip install package
    ```

=== "uv"

    ```bash
    uv add package
    ```

Workflow

  1. Write content — use references for formatting syntax
  2. Diagrams — invoke mermaidjs-v11 skill, split large diagrams into _includes/
  3. Previewuv run mkdocs serve for live reload
  4. Validateuv run mkdocs build --strict catches issues

Validation Commands

# Dev server with live reload
uv run mkdocs serve

# Strict build (CI validation)
uv run mkdocs build --strict

# Quick dirty reload during editing
uv run mkdocs serve --dirty

Dependencies

Managed via pyproject.toml + uv sync:

[project]
dependencies = [
    "mkdocs-material",
    "mkdocs-awesome-nav",
    "mkdocs-glightbox",
    "mkdocs-macros-plugin",
    "mkdocs-include-markdown-plugin",
]

Dockerfile uses uv from ghcr.io/astral-sh/uv:0.11.0.

Install via CLI
npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill mkdocs-documentation
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator
kettleofketchup
kettleofketchup Explore all skills →