new

Scaffold Terrae components with registry entries, docs, examples, and changelog.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill accelerates the creation of Terrae components by generating the full scaffold, including code structure, registry entries, documentation, examples, and changelog, reducing manual setup time and errors.

Core Features & Use Cases

  • End-to-end scaffolding: source file, registry entry, docs page, examples, and changelog.
  • Standardized structure: enforces naming, file layout, and integration with the docs system.
  • On-demand guidance: provides prompts and rules to ensure consistency across components.

Quick Start

Provide a component name and follow the guided prompts to generate the full component scaffold, registry entry, examples, docs, and changelog.

Frequently Asked Questions about new

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

FAQPage Schema
How do I automate scaffolding for a new component from scratch?

Automating component scaffolding generates the full file structure, registry entry, docs page, examples, and changelog simultaneously to reduce manual setup time and errors.

What is included in end-to-end component creation for engineering teams?

End-to-end component creation includes generating the source file, registry entry, docs page, examples, changelog entry, and sidebar updates to ensure a consistent standardized structure.

How do I generate a registry entry and documentation for a new UI component?

Generating a registry entry and documentation applies guided prompts to automatically create the component file, docs page, and examples while enforcing naming and file layout consistency.

Does automated scaffolding work for individual component authors and larger engineering teams?

Automated scaffolding supports both individual component authors and engineering teams by enforcing a standardized structure, file layout, and integration with the docs system across all generated components.

What is the best way to ensure consistent structure across multiple new component files?

Ensuring consistent structure across multiple component files requires applying standardized scaffolding rules that automatically generate the source file, registry entry, and documentation with uniform naming conventions.

Can I generate a changelog entry and sidebar updates automatically when building a component?

Generating a changelog entry and sidebar updates happens automatically during the end-to-end scaffolding process to maintain documentation system integration without manual configuration.