documentation-templates

Provide README, API endpoint, and architecture documentation templates.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tridentsof/antigravity-dev-kit --skill documentation-templates-tridentsof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-templates
Source: https://github.com/tridentsof/antigravity-dev-kit/tree/main/skills/documentation-templates
Command: npx skills add https://github.com/tridentsof/antigravity-dev-kit --skill documentation-templates-tridentsof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides ready-to-use templates to standardize technical documentation across projects, reducing duplication and ensuring consistency.

Core Features & Use Cases

  • README Template: a starting point for project setup and quick onboarding.
  • API Endpoint Template: a ready format for documenting endpoints and responses.
  • Architecture Doc Template: a structured guide for system architecture and decisions.

Quick Start

Choose a template and customize it for your project documentation.

Frequently Asked Questions about documentation-templates

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

FAQPage Schema
How do I standardize technical documentation across multiple software projects?

API endpoint templates provide a ready-made markdown format for documenting endpoints and responses, allowing you to quickly fill in request parameters, response schemas, and authentication details without building the document structure from scratch.

What is the best way to write architecture docs for rapid project onboarding?

The best way to write architecture docs is using a structured template that guides system architecture decisions and design rationale, providing a consistent format that helps new team members understand structural choices and technical constraints quickly.

Can I customize these markdown documentation templates for an existing docs workflow?

The templates are designed for software teams needing rapid documentation and consistent project setup, making them suitable for any team looking to standardize technical docs, API references, and architecture decisions without requiring complex dependencies.

Why should I use a template for README and API documentation instead of writing from scratch?

You do not need any external dependencies to use these documentation templates; they are standalone markdown files with frontmatter-based metadata that can be integrated directly into any existing documentation workflow or repository.