add-frontend-feature

Scaffold a React feature by automating the creation of TypeScript interfaces, API endpoints, query and mutation hooks, UI components, and routes end-to-end. This enforces a consistent project structure and replaces repetitive boilerplate when connecting UI modules to backend services.

The best way to add frontend UI modules is through end-to-end scaffolding that generates types, API integration, and UI components simultaneously. This structured workflow ensures consistency and best practices by integrating with the existing architecture for data fetching and error handling.

Yes, automatic frontend feature scaffolding requires a modern React/TypeScript frontend with a 3-layer architecture and support for hooks, routing, and UI components. The scaffolding workflow enforces a standard project structure across types, lib, hooks, components, and routes directories.

Yes, this scaffolding workflow supports creating features that connect frontend UI with backend services via REST or GraphQL. It generates the necessary API endpoints, query and mutation hooks, and TypeScript interfaces to handle client-side data fetching and error handling for both protocols.

Scaffolding a TypeScript React feature requires a 3-layer architecture to properly separate and generate types, API integration logic, and UI components. This structural prerequisite allows the workflow to automatically inject query and mutation hooks, routes, and interfaces into the correct existing project layers.

You should not use automated frontend feature scaffolding if your project lacks a modern React/TypeScript setup with a 3-layer architecture, hooks, and routing. The workflow is designed to enforce a specific standard project structure, making it unsuitable for legacy codebases or non-standard frontend architectures.