documentation-templates

Standardize project documentation templates for README, API, code comments, ADRs, and architecture docs.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/thgterto/Gerenciador-de-estoque --skill documentation-templates-thgterto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-templates
Source: https://github.com/thgterto/Gerenciador-de-estoque/tree/main/.agent/skills/documentation-templates
Command: npx skills add https://github.com/thgterto/Gerenciador-de-estoque --skill documentation-templates-thgterto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation templates and guidelines provide standardized structures for AI-friendly and consistent project documentation.

Core Features & Use Cases

  • Ready-to-use templates for README, API docs, code comments, ADRs, and architecture docs.
  • Clear structure guidelines and examples to accelerate documentation workflows.
  • AI-friendly documentation practices and scalable templates for teams.

Quick Start

Adapt these templates to drafts of your project docs to achieve consistent, AI-friendly output.

Frequently Asked Questions about documentation-templates

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

FAQPage Schema
How do I standardize project documentation across different teams?

Standardize project documentation by adopting ready-made templates that provide clear structures, required sections, and examples for READMEs, API docs, and ADRs, ensuring consistent output and fast adoption across diverse teams.

What is an AI-friendly documentation template?

An AI-friendly documentation template is a standardized structure with clear sections and best practices that supports automated indexing, making project docs easier for automated tools to parse and understand.

Can I use these templates for architecture decisions and code comments?

Yes, you can use these templates for architecture decisions and code comments. The guidelines cover README files, API references, code comments, ADRs, and architecture docs across diverse projects.

What's the best way to write architecture decision records?

The best way to write architecture decision records is using standardized ADR templates with clear sections and examples, which accelerates documentation workflows and ensures consistent architectural logging.

Do I need any specific tools to generate API documentation with these templates?

No specific tools are required to generate API documentation with these templates. They provide structural guidelines and examples that you can adapt directly to your project docs without dependencies.