docs

Generate Terrae component documentation pages with installation, examples, props, and use cases.

243|5|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/alamenai/terrae --skill docs-alamenai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/alamenai/terrae/tree/main/.claude/skills/docs
Command: npx skills add https://github.com/alamenai/terrae --skill docs-alamenai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and maintain accurate Terrae component documentation with consistent structure and examples, reducing manual effort.

Core Features & Use Cases

  • Generate component documentation pages following the standard layout (title, installation, examples, props, use cases).
  • Create or update weeklog entries or README files using a unified, reviewable structure.
  • Validate documentation against reference patterns and ensure visual and code example consistency.

Quick Start

Provide a complete docs page for a given Terrae component following the reference structure.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I generate component documentation for Terrae projects?

Generate Terrae component documentation by producing pages with installation instructions, code examples, props tables, and use cases. The content follows a standard reference layout to ensure consistency across README files and weeklog entries.

What is the standard structure for Terrae component documentation?

Terrae component documentation structure includes a title, installation steps, examples, props tables, and use cases. This layout satisfies Markdown patterns and visual sections while ensuring code example consistency for review.

Can I use this to update existing README files with new component props?

You can update existing README files by applying a unified, reviewable structure for new component props. The process validates documentation against reference patterns to ensure visual and code example consistency.

How do I validate Terrae documentation against reference patterns?

Validate Terrae documentation by checking generated content against reference patterns to ensure visual and code example consistency. The process includes validation steps and requires a final user review before completing.

Does generating Terrae documentation require any external dependencies?

Generating Terrae documentation requires no external dependencies. It operates independently to guide structure and content from the reference pattern directly into Markdown formats and prop tables.