documentation-templates

Provide standardized templates for READMEs, API references, and changelogs.

1|Updated Dec 21, 2024
One-click install
npx skills add https://github.com/SergeiGolos/wod-wiki --skill documentation-templates-sergeigolos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-templates
Source: https://github.com/SergeiGolos/wod-wiki/tree/main/.agent/skills/documentation-templates
Command: npx skills add https://github.com/SergeiGolos/wod-wiki --skill documentation-templates-sergeigolos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides standardized templates and guidelines for various documentation types, ensuring consistency, clarity, and maintainability across projects.

Core Features & Use Cases

  • README Structure: Offers a prioritized section guide and a template for effective project overviews.
  • API Documentation: Provides a per-endpoint template for clear API descriptions.
  • Code Commenting: Outlines best practices for JSDoc/TSDoc comments, distinguishing between necessary and unnecessary annotations.
  • Changelog & ADRs: Includes templates for "Keep a Changelog" and Architecture Decision Records.
  • AI-Friendly Docs: Offers guidance on creating documentation optimized for AI consumption (e.g., llms.txt, RAG-ready formats).
  • Use Case: A new developer joins a project and needs to understand how to document new features, write API endpoints, and contribute effectively. This Skill provides them with the exact templates and guidelines to follow.

Quick Start

Use the documentation-templates skill to generate a README structure for a new project.

Frequently Asked Questions about documentation-templates

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

FAQPage Schema
What is the best way to structure a README for a new software project?

Standardized README templates provide a prioritized section guide for effective project overviews, ensuring scannable and progressively detailed documentation. This structure helps new developers quickly understand and contribute to the project.

How do I write API documentation that is clear and easy to scan?

To write clear API documentation, use a per-endpoint template that provides structured and consistent API descriptions. This ensures your API documentation remains scannable and progressively detailed for developers integrating with your service.

What format should I use for changelogs and Architecture Decision Records?

For changelogs and Architecture Decision Records, use the "Keep a Changelog" format and standard ADR templates. These standardized documentation templates ensure consistency, clarity, and maintainability across your project's history and architectural choices.

How do I create AI-friendly documentation for RAG indexing and LLM consumption?

To create AI-friendly documentation for RAG indexing, use formats like `llms.txt` and follow guidelines optimized for LLM consumption. This ensures your documentation is structured effectively for AI models to parse and retrieve context.

What are the best practices for writing JSDoc and TSDoc code comments?

Best practices for JSDoc and TSDoc code comments involve distinguishing between necessary and unnecessary annotations. Using standardized code commenting guidelines ensures your comments add value without cluttering the codebase.