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

2.11.f — Folder structure for scalable projects

<< 2.11 Overview

Learning outcomes

  1. Compare type-based vs feature-based structures.
  2. Place pages/, components/, hooks/, services/, utils/ with clear rules.
  3. Prevent import cycles and junk-drawer folders.

Starter convention (medium apps)

src/
  app/                 # providers, router, global styles
  pages/               # route-level screens (thin)
  components/          # shared UI primitives + patterns
  features/            # optional: domain vertical slices (billing, auth, ...)
    billing/
      api.ts
      components/
      hooks/
  hooks/               # truly shared hooks
  services/            # api clients, mappers, non-UI orchestration
  utils/               # small pure helpers (prefer specific filenames)

Rule of thumb

Start type-based (components/, pages/). When a feature folder grows painful to navigate, peel that domain into features/<name>/ with its own components and hooks.

services/ vs components/

  • components/ render UI.
  • services/ talk to APIs, map DTOs, orchestrate retries—no JSX ideally.

utils/ hygiene

If a helper is only used by one feature, colocate it. utils/ is for widely reused, stable, tiny pure functions.

Appendix — Scenario bank (basic → advanced)

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

RR5-001 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-002 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-003 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-004 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-005 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-006 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-007 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-008 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-009 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-010 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-011 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-012 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-013 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-014 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-015 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-016 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-017 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-018 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-019 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-020 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-021 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-022 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-023 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-024 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-025 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-026 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-027 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-028 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-029 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-030 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-031 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-032 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-033 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-034 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-035 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-036 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-037 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-038 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-039 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-040 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-041 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-042 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-043 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-044 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-045 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-046 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-047 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-048 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-049 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-050 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-051 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-052 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-053 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-054 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-055 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-056 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-057 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-058 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-059 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-060 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-061 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-062 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-063 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-064 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-065 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-066 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-067 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-068 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-069 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-070 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-071 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-072 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-073 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-074 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-075 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-076 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-077 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-078 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-079 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-080 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-081 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-082 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-083 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-084 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-085 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-086 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-087 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-088 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-089 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-090 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-091 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-092 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-093 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-094 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-095 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-096 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-097 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-098 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-099 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-100 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-101 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-102 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-103 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-104 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-105 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-106 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-107 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-108 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-109 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-110 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-111 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-112 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-113 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-114 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-115 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-116 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-117 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-118 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-119 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-120 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-121 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-122 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-123 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-124 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-125 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-126 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-127 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-128 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-129 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-130 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-131 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-132 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-133 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-134 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-135 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-136 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-137 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-138 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-139 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-140 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-141 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-142 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-143 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-144 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-145 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-146 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-147 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-148 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-149 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-150 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-151 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-152 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-153 — Folder structure #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: pages/ contains business rules that belong in domain modules.
  • Primary remediation: Extract domain logic to services or domain/ with tests.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-154 — Folder structure #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: Barrel index.ts re-exports everything slowing dev server.
  • Primary remediation: Split utils into named modules (format/date.ts) and delete unused.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-155 — Folder structure #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: Circular imports between services and components.
  • Primary remediation: Colocate feature hooks beside feature UI; keep hooks/ for truly shared hooks.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-156 — Folder structure #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: components/ becomes junk drawer of 900 unrelated files.
  • Primary remediation: Move to feature folders (features/billing/...) when size demands; migrate incrementally.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-157 — Folder structure #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: hooks/ only generic; feature hooks misplaced causing grep pain.
  • Primary remediation: Enforce dependency direction: UI → hooks → services → api client.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

RR5-158 — Folder structure #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: utils/ becomes second node_modules of one-off helpers.
  • Primary remediation: Limit barrels; deep import within feature ok; lint circular deps.
  • Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
  • Interview one-liner: Folder structure is for humans: optimize for discoverability and ownership, not Instagrammable diagrams.

<< 2.11 Overview