Episode 2 — React Frontend Architecture NextJS / 2.11 — Routing and Application Structure

2.11.b — Routes & nested routes

Learning outcomes

Nest routes with parent Route + child routes.
Render child routes with <Outlet />.
Use index routes for sensible defaults.

Nested example

import { Outlet, Route, Routes } from "react-router-dom";

function DashboardLayout() {
  return (
    <div className="layout">
      <aside>Sidebar</aside>
      <main>
        <Outlet />
      </main>
    </div>
  );
}

export function AppRoutes() {
  return (
    <Routes>
      <Route path="/" element={<Home />} />

      <Route path="/dashboard" element={<DashboardLayout />}>
        <Route index element={<DashboardHome />} />
        <Route path="invoices" element={<Invoices />} />
        <Route path="settings" element={<Settings />} />
      </Route>
    </Routes>
  );
}

function Home() {
  return <h1>Home</h1>;
}
function DashboardHome() {
  return <p>Dashboard overview</p>;
}
function Invoices() {
  return <p>Invoices</p>;
}
function Settings() {
  return <p>Settings</p>;
}

/dashboard shows DashboardHome (index). /dashboard/invoices shows Invoices inside the layout.

Appendix — Scenario bank (basic → advanced)

Drill format: broken URL / UX → root cause → fix → interview phrase.

RR1-001 — Nested routes #1

Level: Beginner
Symptom: 404 on refresh at depth 13 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-002 — Nested routes #2

Level: Beginner+
Symptom: 404 on refresh at depth 26 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-003 — Nested routes #3

Level: Intermediate
Symptom: 404 on refresh at depth 39 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-004 — Nested routes #4

Level: Intermediate+
Symptom: 404 on refresh at depth 52 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-005 — Nested routes #5

Level: Advanced
Symptom: 404 on refresh at depth 65 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-006 — Nested routes #6

Level: Advanced+
Symptom: 404 on refresh at depth 78 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-007 — Nested routes #7

Level: Beginner
Symptom: 404 on refresh at depth 91 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-008 — Nested routes #8

Level: Beginner+
Symptom: 404 on refresh at depth 104 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-009 — Nested routes #9

Level: Intermediate
Symptom: 404 on refresh at depth 117 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-010 — Nested routes #10

Level: Intermediate+
Symptom: 404 on refresh at depth 130 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-011 — Nested routes #11

Level: Advanced
Symptom: 404 on refresh at depth 143 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-012 — Nested routes #12

Level: Advanced+
Symptom: 404 on refresh at depth 156 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-013 — Nested routes #13

Level: Beginner
Symptom: 404 on refresh at depth 169 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-014 — Nested routes #14

Level: Beginner+
Symptom: 404 on refresh at depth 182 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-015 — Nested routes #15

Level: Intermediate
Symptom: 404 on refresh at depth 195 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-016 — Nested routes #16

Level: Intermediate+
Symptom: 404 on refresh at depth 8 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-017 — Nested routes #17

Level: Advanced
Symptom: 404 on refresh at depth 21 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-018 — Nested routes #18

Level: Advanced+
Symptom: 404 on refresh at depth 34 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-019 — Nested routes #19

Level: Beginner
Symptom: 404 on refresh at depth 47 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-020 — Nested routes #20

Level: Beginner+
Symptom: 404 on refresh at depth 60 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-021 — Nested routes #21

Level: Intermediate
Symptom: 404 on refresh at depth 73 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-022 — Nested routes #22

Level: Intermediate+
Symptom: 404 on refresh at depth 86 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-023 — Nested routes #23

Level: Advanced
Symptom: 404 on refresh at depth 99 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-024 — Nested routes #24

Level: Advanced+
Symptom: 404 on refresh at depth 112 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-025 — Nested routes #25

Level: Beginner
Symptom: 404 on refresh at depth 125 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-026 — Nested routes #26

Level: Beginner+
Symptom: 404 on refresh at depth 138 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-027 — Nested routes #27

Level: Intermediate
Symptom: 404 on refresh at depth 151 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-028 — Nested routes #28

Level: Intermediate+
Symptom: 404 on refresh at depth 164 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-029 — Nested routes #29

Level: Advanced
Symptom: 404 on refresh at depth 177 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-030 — Nested routes #30

Level: Advanced+
Symptom: 404 on refresh at depth 190 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-031 — Nested routes #31

Level: Beginner
Symptom: 404 on refresh at depth 3 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-032 — Nested routes #32

Level: Beginner+
Symptom: 404 on refresh at depth 16 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-033 — Nested routes #33

Level: Intermediate
Symptom: 404 on refresh at depth 29 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-034 — Nested routes #34

Level: Intermediate+
Symptom: 404 on refresh at depth 42 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-035 — Nested routes #35

Level: Advanced
Symptom: 404 on refresh at depth 55 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-036 — Nested routes #36

Level: Advanced+
Symptom: 404 on refresh at depth 68 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-037 — Nested routes #37

Level: Beginner
Symptom: 404 on refresh at depth 81 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-038 — Nested routes #38

Level: Beginner+
Symptom: 404 on refresh at depth 94 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-039 — Nested routes #39

Level: Intermediate
Symptom: 404 on refresh at depth 107 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-040 — Nested routes #40

Level: Intermediate+
Symptom: 404 on refresh at depth 120 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-041 — Nested routes #41

Level: Advanced
Symptom: 404 on refresh at depth 133 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-042 — Nested routes #42

Level: Advanced+
Symptom: 404 on refresh at depth 146 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-043 — Nested routes #43

Level: Beginner
Symptom: 404 on refresh at depth 159 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-044 — Nested routes #44

Level: Beginner+
Symptom: 404 on refresh at depth 172 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-045 — Nested routes #45

Level: Intermediate
Symptom: 404 on refresh at depth 185 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-046 — Nested routes #46

Level: Intermediate+
Symptom: 404 on refresh at depth 198 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-047 — Nested routes #47

Level: Advanced
Symptom: 404 on refresh at depth 11 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-048 — Nested routes #48

Level: Advanced+
Symptom: 404 on refresh at depth 24 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-049 — Nested routes #49

Level: Beginner
Symptom: 404 on refresh at depth 37 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-050 — Nested routes #50

Level: Beginner+
Symptom: 404 on refresh at depth 50 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-051 — Nested routes #51

Level: Intermediate
Symptom: 404 on refresh at depth 63 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-052 — Nested routes #52

Level: Intermediate+
Symptom: 404 on refresh at depth 76 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-053 — Nested routes #53

Level: Advanced
Symptom: 404 on refresh at depth 89 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-054 — Nested routes #54

Level: Advanced+
Symptom: 404 on refresh at depth 102 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-055 — Nested routes #55

Level: Beginner
Symptom: 404 on refresh at depth 115 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-056 — Nested routes #56

Level: Beginner+
Symptom: 404 on refresh at depth 128 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-057 — Nested routes #57

Level: Intermediate
Symptom: 404 on refresh at depth 141 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-058 — Nested routes #58

Level: Intermediate+
Symptom: 404 on refresh at depth 154 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-059 — Nested routes #59

Level: Advanced
Symptom: 404 on refresh at depth 167 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-060 — Nested routes #60

Level: Advanced+
Symptom: 404 on refresh at depth 180 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-061 — Nested routes #61

Level: Beginner
Symptom: 404 on refresh at depth 193 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-062 — Nested routes #62

Level: Beginner+
Symptom: 404 on refresh at depth 6 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-063 — Nested routes #63

Level: Intermediate
Symptom: 404 on refresh at depth 19 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-064 — Nested routes #64

Level: Intermediate+
Symptom: 404 on refresh at depth 32 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-065 — Nested routes #65

Level: Advanced
Symptom: 404 on refresh at depth 45 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-066 — Nested routes #66

Level: Advanced+
Symptom: 404 on refresh at depth 58 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-067 — Nested routes #67

Level: Beginner
Symptom: 404 on refresh at depth 71 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-068 — Nested routes #68

Level: Beginner+
Symptom: 404 on refresh at depth 84 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-069 — Nested routes #69

Level: Intermediate
Symptom: 404 on refresh at depth 97 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-070 — Nested routes #70

Level: Intermediate+
Symptom: 404 on refresh at depth 110 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-071 — Nested routes #71

Level: Advanced
Symptom: 404 on refresh at depth 123 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-072 — Nested routes #72

Level: Advanced+
Symptom: 404 on refresh at depth 136 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-073 — Nested routes #73

Level: Beginner
Symptom: 404 on refresh at depth 149 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-074 — Nested routes #74

Level: Beginner+
Symptom: 404 on refresh at depth 162 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-075 — Nested routes #75

Level: Intermediate
Symptom: 404 on refresh at depth 175 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-076 — Nested routes #76

Level: Intermediate+
Symptom: 404 on refresh at depth 188 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-077 — Nested routes #77

Level: Advanced
Symptom: 404 on refresh at depth 1 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-078 — Nested routes #78

Level: Advanced+
Symptom: 404 on refresh at depth 14 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-079 — Nested routes #79

Level: Beginner
Symptom: 404 on refresh at depth 27 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-080 — Nested routes #80

Level: Beginner+
Symptom: 404 on refresh at depth 40 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-081 — Nested routes #81

Level: Intermediate
Symptom: 404 on refresh at depth 53 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-082 — Nested routes #82

Level: Intermediate+
Symptom: 404 on refresh at depth 66 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-083 — Nested routes #83

Level: Advanced
Symptom: 404 on refresh at depth 79 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-084 — Nested routes #84

Level: Advanced+
Symptom: 404 on refresh at depth 92 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-085 — Nested routes #85

Level: Beginner
Symptom: 404 on refresh at depth 105 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-086 — Nested routes #86

Level: Beginner+
Symptom: 404 on refresh at depth 118 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-087 — Nested routes #87

Level: Intermediate
Symptom: 404 on refresh at depth 131 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-088 — Nested routes #88

Level: Intermediate+
Symptom: 404 on refresh at depth 144 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-089 — Nested routes #89

Level: Advanced
Symptom: 404 on refresh at depth 157 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-090 — Nested routes #90

Level: Advanced+
Symptom: 404 on refresh at depth 170 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-091 — Nested routes #91

Level: Beginner
Symptom: 404 on refresh at depth 183 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-092 — Nested routes #92

Level: Beginner+
Symptom: 404 on refresh at depth 196 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-093 — Nested routes #93

Level: Intermediate
Symptom: 404 on refresh at depth 9 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-094 — Nested routes #94

Level: Intermediate+
Symptom: 404 on refresh at depth 22 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-095 — Nested routes #95

Level: Advanced
Symptom: 404 on refresh at depth 35 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-096 — Nested routes #96

Level: Advanced+
Symptom: 404 on refresh at depth 48 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-097 — Nested routes #97

Level: Beginner
Symptom: 404 on refresh at depth 61 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-098 — Nested routes #98

Level: Beginner+
Symptom: 404 on refresh at depth 74 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-099 — Nested routes #99

Level: Intermediate
Symptom: 404 on refresh at depth 87 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-100 — Nested routes #100

Level: Intermediate+
Symptom: 404 on refresh at depth 100 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-101 — Nested routes #101

Level: Advanced
Symptom: 404 on refresh at depth 113 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-102 — Nested routes #102

Level: Advanced+
Symptom: 404 on refresh at depth 126 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-103 — Nested routes #103

Level: Beginner
Symptom: 404 on refresh at depth 139 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-104 — Nested routes #104

Level: Beginner+
Symptom: 404 on refresh at depth 152 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-105 — Nested routes #105

Level: Intermediate
Symptom: 404 on refresh at depth 165 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-106 — Nested routes #106

Level: Intermediate+
Symptom: 404 on refresh at depth 178 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-107 — Nested routes #107

Level: Advanced
Symptom: 404 on refresh at depth 191 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-108 — Nested routes #108

Level: Advanced+
Symptom: 404 on refresh at depth 4 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-109 — Nested routes #109

Level: Beginner
Symptom: 404 on refresh at depth 17 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-110 — Nested routes #110

Level: Beginner+
Symptom: 404 on refresh at depth 30 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-111 — Nested routes #111

Level: Intermediate
Symptom: 404 on refresh at depth 43 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-112 — Nested routes #112

Level: Intermediate+
Symptom: 404 on refresh at depth 56 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-113 — Nested routes #113

Level: Advanced
Symptom: 404 on refresh at depth 69 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-114 — Nested routes #114

Level: Advanced+
Symptom: 404 on refresh at depth 82 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-115 — Nested routes #115

Level: Beginner
Symptom: 404 on refresh at depth 95 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-116 — Nested routes #116

Level: Beginner+
Symptom: 404 on refresh at depth 108 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-117 — Nested routes #117

Level: Intermediate
Symptom: 404 on refresh at depth 121 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-118 — Nested routes #118

Level: Intermediate+
Symptom: 404 on refresh at depth 134 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-119 — Nested routes #119

Level: Advanced
Symptom: 404 on refresh at depth 147 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-120 — Nested routes #120

Level: Advanced+
Symptom: 404 on refresh at depth 160 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-121 — Nested routes #121

Level: Beginner
Symptom: 404 on refresh at depth 173 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-122 — Nested routes #122

Level: Beginner+
Symptom: 404 on refresh at depth 186 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-123 — Nested routes #123

Level: Intermediate
Symptom: 404 on refresh at depth 199 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-124 — Nested routes #124

Level: Intermediate+
Symptom: 404 on refresh at depth 12 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-125 — Nested routes #125

Level: Advanced
Symptom: 404 on refresh at depth 25 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-126 — Nested routes #126

Level: Advanced+
Symptom: 404 on refresh at depth 38 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-127 — Nested routes #127

Level: Beginner
Symptom: 404 on refresh at depth 51 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-128 — Nested routes #128

Level: Beginner+
Symptom: 404 on refresh at depth 64 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-129 — Nested routes #129

Level: Intermediate
Symptom: 404 on refresh at depth 77 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-130 — Nested routes #130

Level: Intermediate+
Symptom: 404 on refresh at depth 90 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-131 — Nested routes #131

Level: Advanced
Symptom: 404 on refresh at depth 103 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-132 — Nested routes #132

Level: Advanced+
Symptom: 404 on refresh at depth 116 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-133 — Nested routes #133

Level: Beginner
Symptom: 404 on refresh at depth 129 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-134 — Nested routes #134

Level: Beginner+
Symptom: 404 on refresh at depth 142 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-135 — Nested routes #135

Level: Intermediate
Symptom: 404 on refresh at depth 155 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-136 — Nested routes #136

Level: Intermediate+
Symptom: 404 on refresh at depth 168 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-137 — Nested routes #137

Level: Advanced
Symptom: 404 on refresh at depth 181 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-138 — Nested routes #138

Level: Advanced+
Symptom: 404 on refresh at depth 194 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-139 — Nested routes #139

Level: Beginner
Symptom: 404 on refresh at depth 7 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-140 — Nested routes #140

Level: Beginner+
Symptom: 404 on refresh at depth 20 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-141 — Nested routes #141

Level: Intermediate
Symptom: 404 on refresh at depth 33 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-142 — Nested routes #142

Level: Intermediate+
Symptom: 404 on refresh at depth 46 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-143 — Nested routes #143

Level: Advanced
Symptom: 404 on refresh at depth 59 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-144 — Nested routes #144

Level: Advanced+
Symptom: 404 on refresh at depth 72 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-145 — Nested routes #145

Level: Beginner
Symptom: 404 on refresh at depth 85 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-146 — Nested routes #146

Level: Beginner+
Symptom: 404 on refresh at depth 98 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-147 — Nested routes #147

Level: Intermediate
Symptom: 404 on refresh at depth 111 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-148 — Nested routes #148

Level: Intermediate+
Symptom: 404 on refresh at depth 124 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-149 — Nested routes #149

Level: Advanced
Symptom: 404 on refresh at depth 137 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-150 — Nested routes #150

Level: Advanced+
Symptom: 404 on refresh at depth 150 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-151 — Nested routes #151

Level: Beginner
Symptom: 404 on refresh at depth 163 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-152 — Nested routes #152

Level: Beginner+
Symptom: 404 on refresh at depth 176 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-153 — Nested routes #153

Level: Intermediate
Symptom: 404 on refresh at depth 189 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Duplicate route paths in different branches matching wrong winner.
Primary remediation: Audit route definitions; use route config array for large apps.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-154 — Nested routes #154

Level: Intermediate+
Symptom: 404 on refresh at depth 2 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Index route missing causing parent path to show blank.
Primary remediation: Order specific routes before splats; follow RR matching rules.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-155 — Nested routes #155

Level: Advanced
Symptom: 404 on refresh at depth 15 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Relative to paths resolve unexpectedly after moving route tree.
Primary remediation: Wrap lazy components with Suspense at layout or route level.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-156 — Nested routes #156

Level: Advanced+
Symptom: 404 on refresh at depth 28 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Forgot <Outlet /> so child routes render nowhere.
Primary remediation: Place Outlet where children should render; visualize route tree on paper.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-157 — Nested routes #157

Level: Beginner
Symptom: 404 on refresh at depth 41 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Lazy routes without Suspense boundary around Outlet subtree.
Primary remediation: Prefer absolute paths for nav when tree moves often; document team rule.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

RR1-158 — Nested routes #158

Level: Beginner+
Symptom: 404 on refresh at depth 54 or wrong active nav highlight.
Structure symptom: duplicated layout or import cycles after refactor.
Root cause class: Route element swapped order causing unreachable routes.
Primary remediation: Add index route or redirect from parent to default child.
Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
Interview one-liner: Nested routes should mirror your UI composition: layout owns chrome, children own pages.

<< 2.11 Overview