React + Vite baseline
Use for a local interface without routing, remote API access, application layout, runtime guards, or generated tests.
npm run generate -- focused-app --router=false--apiClient=false--layout=none--errorBoundary=false--loadingState=false--envValidation=false--testing=none Forms + server data + table
Use for a server-backed product with validated input, list and detail pages, and cached remote data.
npm run generate -- product-app --uiLibrary=shadcn--forms=true--query=true--table=true--apiModels=true--pageTemplates=true--testing=component MUI + data visualization
Use for an application shell with remote data, reusable tables, charts, and component-level UI checks.
npm run generate -- operations-dashboard --uiLibrary=mui--layout=app-shell--query=true--table=true--charts=true--testing=component OIDC + guarded routes
Use when the frontend needs an identity and route-guard baseline. Provider setup and backend enforcement remain application-owned.
npm run generate -- customer-portal --authentication=oidc--authorization=route--router=true--layout=app-shell--testing=e2e SignalR + notifications
Use when the browser consumes live server events and must surface state changes to the user.
npm run generate -- live-console --realtime=signalr--notifications=true--query=true--testing=component Forms + localization + files
Use for a multilingual workflow that validates user input and submits files.
npm run generate -- intake-portal --localization=true--forms=true--fileUpload=true--testing=component