React Routing and Rendering Strategy

When to use

Invoke when adding or restructuring routing in a standalone React SPA, when translating a frontend-architecture.md route map into a React Router topology, or when hardening route-level loading, error, and auth-gate behavior.

Do not use for: project scaffolding or the auth provider baseline (use react-app-scaffold-and-runtime), global/server state libraries and data-fetching conventions (use react-state-management-and-data-fetching), design-system or a11y of route UIs (use react-design-system-and-accessibility), perf budgeting and code-split topology (use react-performance-and-delivery-optimization), or SSR/SSG/ISR/RSC/server actions (meta-framework territory — use the nextjs stack).

Inputs

Required:

• An existing react app scaffold from react-app-scaffold-and-runtime (provides the auth provider/wrapper seam and error-boundary seam).
• Approved frontend-architecture.md with the route map and the rendering mode per route. For a standalone React SPA every route is CSR; if the architecture assigns SSR/SSG/streaming to any route, that route is out of scope here.

Optional: