forge-docs

Generate MkDocs documentation structures and templates for material-theme sites.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/martimramos/claude-forge --skill forge-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-docs
Source: https://github.com/martimramos/claude-forge/tree/main/skills/docs
Command: npx skills add https://github.com/martimramos/claude-forge --skill forge-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes project documentation by providing a complete MkDocs-based structure and templates, reducing confusion and ensuring consistency across repos.

Core Features & Use Cases

  • MkDocs structure: A recommended folder layout with index.md, getting-started.md, architecture/decisions/, guides/, and reference/.
  • mkdocs.yml template: A ready-to-use configuration optimized for the mkdocs-material theme.
  • ADR guidance: Architecture Decision Records support with ADR patterns and example files.
  • Templates: README, architecture decisions, and reference templates to accelerate documentation.
  • Use Case: Apply to new projects or renovate existing repos to align with standardized docs.

Quick Start

Create a docs/ folder with index.md, getting-started.md, architecture/decisions/ADR-0001.md, guides/ installation.md, configuration.md, deployment.md, and reference/ api.md, cli.md. Add a mkdocs.yml configured for the material theme and run the following: mkdocs serve to preview locally or mkdocs build to generate a static site.

Frequently Asked Questions about forge-docs

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

FAQPage Schema
How do I standardize project documentation across multiple repositories?

MkDocs documentation standardization involves applying a predefined folder layout with index.md, getting-started.md, architecture/decisions/, guides/, and reference/ directories to ensure consistent project docs across multiple repositories.

What is the recommended folder structure for an MkDocs material theme site?

The recommended MkDocs folder structure includes a docs directory containing index.md, getting-started.md, architecture/decisions/ for ADRs, guides/ for tutorials, and reference/ for API and CLI documentation.

How do I set up Architecture Decision Records using markdown templates?

Architecture Decision Records setup uses provided markdown templates placed in the architecture/decisions/ directory, starting with example files like ADR-0001.md to document architectural choices consistently across projects.

Can I use a templated mkdocs.yml configuration for the material theme without manual setup?

Yes, you can use a ready-to-use mkdocs.yml template optimized for the mkdocs-material theme, allowing teams to adopt standardized documentation configuration with minimal manual setup.

What is the best way to organize a docs folder for consistent project documentation?

The best way to organize a docs folder for consistent project documentation is adopting a standardized MkDocs skeleton with separate directories for architecture decisions, guides, and reference materials alongside templated configuration files.