- Home
- Skills
- Vudovn
- Antigravity Kit
- Documentation Templates
documentation-templates_skill
- TypeScript
5.7k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill vudovn/antigravity-kit --skill documentation-templates- SKILL.md3.2 KB
Overview
This skill provides ready-to-use documentation templates and structure guidelines for project front pages, API docs, code comments, changelogs, architecture decisions, and AI-friendly docs. It helps teams produce clear, scannable, and machine-friendly documentation that speeds onboarding and supports automated agents. Use the templates as starting points and adapt them to your project conventions.
How this skill works
The skill supplies concise templates for common documentation artifacts: a project front page, per-endpoint API docs, JSDoc/TSDoc comment blocks, changelog entries, ADRs, and agent-focused manifests like llms.txt. It emphasizes hierarchical headings, examples-first content, JSON/YAML samples, and practices that make docs both human- and AI-consumable. You can copy templates into your docs folder and follow the structure principles to keep content consistent and up to date.
When to use it
- Creating or updating the project front page and quick start instructions
- Documenting HTTP endpoints with clear parameters, responses, and examples
- Writing JSDoc/TSDoc for public APIs and complex business logic
- Recording architectural decisions using ADRs before or after implementation
- Preparing docs for retrieval-augmented systems or AI crawlers (llms.txt)
Best practices
- Prioritize scannability: use headers, short lists, and tables for key info
- Start with concrete examples and minimal working steps before details
- Document why a decision exists, not just how it was implemented
- Keep changelogs concise and versioned under an Unreleased section
- Provide JSON/YAML examples and mermaid diagrams for RAG and agent indexing
Example use cases
- Front-page template with one-line objective and quick start to reduce onboarding time
- Per-endpoint API pages listing parameters, responses, and request/response examples
- JSDoc/TSDoc blocks for library functions including params, returns, throws, and examples
- ADR template to record trade-offs for major architecture changes
- llms.txt and core-files index to help AI agents locate key code and docs for automated analysis
FAQ
Use the templates as starting points: keep sections that add value, remove irrelevant ones, and align naming with your repo and CI/CD conventions.
What makes documentation AI-friendly?
Clear H1–H3 hierarchy, self-contained sections, structured examples (JSON/YAML), and a small manifest (llms.txt) pointing to core files improve agent indexing and retrieval.
When should I write an ADR?
Create an ADR whenever a decision affects architecture, APIs, or major trade-offs—ideally before implementation or immediately after to capture rationale.