Mira EngineeringPlaybooks

Generate only what the product needs.

Choose a situation, copy a validated command, then verify the standalone React application your team will own.

Choose a starting point

Copy a starting point that matches the product.

Run the command from the template repository. Replace the application name, generate the project, then install and verify the output.

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

Verify the generated baseline.

The generator writes files but does not install packages or run generated-project checks.

  1. Install with a supported runtimeUse a supported Node.js release and install the generated application with pnpm.
  2. Build and test what was selectedRun the build. Run tests when a testing option generated a test setup.
  3. Exercise the applicationCheck routes, environment validation, API configuration, and selected interface behavior in the browser.
  4. Review what is absentA disabled capability should leave no owned dependency, file, configuration, import, or test behind.

Generation is a starting point, not a runtime platform.

Post-generation capability installation is not supported. The application team owns provider integration, backend authorization enforcement, security, deployment, dependencies, and future changes. A successful build does not make every generated application production-ready.