react-vite

To structure a React + Vite frontend in a pnpm monorepo, you apply architecture guidelines for routing and component organization while establishing clear frontend-backend boundaries. This ensures scalable workflows and coordinated project bootstrapping.

A design subagent works with React and Vite by handling frontend polish during initial builds. You delegate presentation-first refinements to the subagent, allowing structured development to focus on logic and API surface planning.

Yes, you can use this approach for logic-heavy frontend projects, CRUD dashboards, and presentation-first apps. It provides classification guidance to determine frontend ownership and plan API surfaces for backend work based on project type.

The best way to plan API surfaces for backend work in a monorepo is using classification guidance to determine frontend ownership. This separates presentation logic from backend dependencies, establishing clear boundaries for scalable workflows.

You need a design subagent for frontend development during first-build orchestration and when refining frontend details. It delegates visual and presentation work, ensuring the React + Vite architecture remains structured and scalable.

Yes, this React + Vite workflow requires specific routing and component organization rules. It ensures compliance with architectural guidelines to maintain clear frontend-backend boundaries and scalable monorepo development.