doc-patterns

Define and enforce consistent documentation structures across project directories.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill doc-patterns-l3ocho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-patterns
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/doc-guardian/skills/doc-patterns
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill doc-patterns-l3ocho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patterns and conventions for documenting code and projects to ensure consistent, thorough documentation across repositories.

Core Features & Use Cases

  • Standard file inventories for README, CLAUDE.md, and docs
  • Guidance on typical sections for CLAUDE.md, API docs, and code comments
  • Templates and checks to audit documentation coverage and structure

Quick Start

Apply these patterns to the project's documentation to ensure consistent structure and content.

Frequently Asked Questions about doc-patterns

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

FAQPage Schema
How do I standardize documentation structure across multiple project modules?

To standardize documentation structure, apply consistent file inventories and section patterns for README.md, CLAUDE.md, and docs files across root and subdirectories. This enforces uniform coverage and structure for every module in the repository.

What sections should a CLAUDE.md file include for consistent project conventions?

A CLAUDE.md file should include standard section patterns that define project conventions, code documentation guidelines, and documentation workflows. Specifying these typical sections ensures comprehensive coverage and thorough documentation across the repository.

How do I audit existing documentation coverage for missing files and patterns?

Audit documentation coverage by applying standard file inventories to check root and subdirectories for required README.md, CLAUDE.md, and docs files. Templates and checks identify missing files and structural inconsistencies across modules.

Can I use these documentation patterns for both root and subdirectory level files?

Yes, these documentation patterns apply to both root and subdirectory levels. You can audit and draft documentation for multiple modules, ensuring standard file inventories and section patterns are enforced consistently throughout the entire project hierarchy.

What is the best way to enforce consistent code documentation conventions across a repository?

The best way to enforce consistent code documentation conventions is to specify standard section patterns for API docs and code comments. Applying proven templates and checks ensures thorough, uniform documentation structure across all modules.

Do I need any specific dependencies to apply these documentation templates?

No dependencies are required to apply these documentation templates. The patterns and conventions operate independently to define and enforce consistent documentation structures, allowing you to audit and draft project files without external tools.