create-component

Scaffold Preact components with standardized folder layouts and index exports.

7|3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/agentconfig/agentconfig.org --skill create-component-agentconfig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-component
Source: https://github.com/agentconfig/agentconfig.org/tree/main/.github/skills/create-component
Command: npx skills add https://github.com/agentconfig/agentconfig.org --skill create-component-agentconfig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Creating UI components in a consistent, scalable manner is time-consuming and error-prone. This skill provides a standardized workflow and file structure for adding Preact components that align with project conventions.

Core Features & Use Cases

  • Enforces a standardized folder layout under site/src/components/{ComponentName}/ with index.ts and {ComponentName}.tsx
  • Supplies a reusable template (assets/component-template.tsx) and detailed guidelines for TypeScript, styling (Tailwind), and accessibility
  • Use case: Rapidly scaffold new UI components for pages, sections, or interactive widgets with consistent exports and typings

Quick Start

Create a new folder in site/src/components/{ComponentName}, copy the template from assets/component-template.tsx, rename and customize, then export it via index.ts and import it where needed.

Frequently Asked Questions about create-component

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

FAQPage Schema
How do I scaffold a new Preact component with TypeScript and Tailwind?

Create a folder under site/src/components/{ComponentName}, copy the reusable template, customize it with TypeScript and Tailwind, then export via index.ts. This enforces consistent typings and standardized folder layout.

What is the standard folder layout for Preact UI components?

The standard folder layout for Preact UI components places files under site/src/components/{ComponentName}/, containing an index.ts for exports and a {ComponentName}.tsx file for the component logic. This ensures scalable and consistent imports.

Does this component scaffolding approach work with existing App.tsx files?

Yes, this component scaffolding approach works with existing App.tsx files by providing integration guidance. After scaffolding and exporting via index.ts, you import the new component directly into App.tsx or parent components where needed.

Can I use this to create interactive widgets and page sections?

Yes, you can use this to create interactive widgets and page sections. The scaffolding workflow applies to adding UI components, sections, or interactive elements across a project while maintaining consistent typings and styling.

What's the best way to enforce consistent export conventions for UI components?

The best way to enforce consistent export conventions is using a standardized folder layout with an index.ts barrel file. This skill supplies a reusable template and guidelines to ensure all UI components follow identical export and typing patterns.

Do I need any external dependencies to scaffold components this way?

No external dependencies are required to scaffold components this way. The skill relies on a built-in template and established project conventions for Preact, TypeScript, and Tailwind to structurally generate the necessary files.