react-component

Generate React server components with TypeScript and Tailwind by using a server-first approach that defaults to server components and applies Shadcn and Tailwind styling. It scaffolds composable UI widgets, forms, and dialogs with strict TypeScript types.

Use client components in React only when interactivity is required. Server components are the default for UI scaffolding, while client components handle interactive boundaries across pages, forms, and dialogs within your TypeScript project.

Yes, the React component generator supports Shadcn UI primitives alongside Tailwind styling. It builds composable components using these primitives, applying TypeScript-only code with arrow-function const declarations for accessible UI.

Avoid React.FC and any types by enforcing TypeScript-only components using arrow-function const declarations. The generator produces kebab-case filenames and strictly types all rendered text, ensuring no any types appear in your UI widgets.

The best way to scaffold accessible forms and dialogs in React is using a server-first composition pattern with server actions for data flows. This approach emphasizes accessibility and composability across server and client boundaries with Tailwind styling.

Your generated React component uses a kebab-case filename to enforce consistent TypeScript-only code standards across your project. This convention applies to all generated pages, forms, dialogs, and UI widgets, ensuring uniform composability.