new-component

Scaffolding a React component following project conventions requires generating a skeleton that enforces import order, groups imports by source, defines internal non-exported interfaces, and applies prop typing.

Generating a TypeScript React component with tRPC integration involves creating a functional component skeleton that includes tRPC data fetching patterns, applies type safety, and ensures internal interfaces are not exported globally.

The best way to structure React component imports and types is to group imports by source, enforce a specific import order, and keep internal interfaces unexported to maintain clean module boundaries and ensure maintainability.

Yes, you can use cn() for Tailwind styling when creating React components, as it provides a ready-to-use skeleton that applies Tailwind-friendly class naming conventions directly within the generated component output.

Yes, this React component generator supports functional components and prop typing by applying documented conventions and naming rules to common component scenarios, producing a ready-to-use skeleton with strict type definitions.

You should not export internal interfaces from your React components to satisfy documented project conventions, ensuring strict module boundaries, preventing external access to internal types, and maintaining consistent code architecture.