Create Component

Create React components with TypeScript props interfaces and 4-state handling.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Tvshreyas/DISTILL --skill create-component-tvshreyas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create Component
Source: https://github.com/Tvshreyas/DISTILL/tree/main/.agent/skills/create-component
Command: npx skills add https://github.com/Tvshreyas/DISTILL --skill create-component-tvshreyas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating UI components consistently across a project by following Distill's conventions and state handling rules.

Core Features & Use Cases

  • Enforces server/client component decisions and proper file placement (components/ vs. route co-location)
  • Ensures 4-state handling: loading, empty, error, and success
  • Maintains styling guidelines with Tailwind v4 and no custom CSS
  • Validates TypeScript usage with exported props interfaces and no any types
  • Provides a clear Quick Start for rapid component creation

Quick Start

Create a new React component following Distill's conventions and place it under the appropriate components/ directory with proper props typing.

Frequently Asked Questions about Create Component

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

FAQPage Schema
How do I create React components with TypeScript that enforce loading, empty, error, and success states?

To create React components with TypeScript and proper state handling, this Skill automates component generation by enforcing 4-state handling (loading, empty, error, success) and validating TypeScript usage with exported props interfaces.

Does this Skill work with Next.js server and client component patterns?

Yes, this Skill works with Next.js server and client component patterns by enforcing proper server/client component decisions and applying correct file placement rules within the components/ directory or route co-locations.

What's the best way to build Tailwind v4 UI components without custom CSS?

The best way to build Tailwind v4 UI components without custom CSS is to use this Skill, which maintains strict styling guidelines by enforcing Tailwind utility classes and rejecting any custom CSS during component scaffolding.

How do I generate a Next.js component without using any types in TypeScript?

To generate a Next.js component without using any types in TypeScript, this Skill validates type safety during creation by requiring an exported props interface and explicitly prohibiting the use of any types.

Can I use this to create a React component that follows strict project co-location conventions?

Yes, you can use this to create a React component that follows strict project conventions, as it automates file placement decisions between the dedicated components/ directory and route co-located directories.

What are the limitations of using automated scaffolding for React UI components?

The limitations of using automated scaffolding for React UI components include strict dependency on Next.js, TypeScript, and Tailwind v4 environments, meaning it cannot be applied to projects using different frameworks or styling systems.