react-component

Guide React component development with typed props and Tailwind styling conventions.

1|Updated Sep 1, 2025
One-click install
npx skills add https://github.com/LandonSchropp/agent-toolkit --skill react-component-landonschropp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-component
Source: https://github.com/LandonSchropp/agent-toolkit/tree/main/skills/react-component
Command: npx skills add https://github.com/LandonSchropp/agent-toolkit --skill react-component-landonschropp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers consistently write and edit React components by establishing a shared set of conventions for component structure, typing, prop documentation, and styling.

Core Features & Use Cases

  • Functional component pattern with named export
  • Props interfaces with JSDoc comments
  • Tailwind-based styling and clsx usage for dynamic classes
  • Real-world example patterns for common components

Quick Start

Start by creating a functional component with a named export and add a corresponding Props type and JSDoc comments for each prop.

Frequently Asked Questions about react-component

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

FAQPage Schema
How do I structure a React component with TypeScript and Tailwind?

Structure a React component by using a functional component pattern with a named export, explicit Props interface typing, and Tailwind classes for styling. Add per-prop JSDoc comments to document the component API.

What's the best way to type React component props with TypeScript?

Type React component props by defining an explicit Props interface with TypeScript. Attach JSDoc comments to each prop field to provide documentation and ensure a well-typed, consistent component structure.

How do I apply dynamic Tailwind classes in a React component?

Apply dynamic Tailwind classes in a React component by using the clsx utility. This approach allows you to conditionally merge class names based on component props while maintaining clean styling conventions.

Does this React coding standard enforce named exports for components?

Yes, this React coding standard enforces named exports for all functional components. It also mandates explicit Props typing, per-prop JSDoc comments, and Tailwind with clsx styling to ensure uniform structure.

Why add JSDoc comments to individual React component props?

Add JSDoc comments to individual React component props to document their purpose and expected values. This practice improves code readability, facilitates onboarding, and ensures consistent component structure during frontend development and code reviews.