File and folder structure follows framework conventions

Misorganized directory structure forces every contributor to build a mental map from scratch. When components live in the root, API logic lives inside component files, and the src/ wrapper is applied inconsistently, adding a feature means hunting across the entire tree. ISO 25010 maintainability.analysability degrades directly: the time to locate where a change belongs rises sharply. New contributors — or future you — lose hours before writing a single line. Framework conventions exist precisely to make projects predictable.

Adopt your framework's conventional layout and migrate incrementally — one directory at a time, verifying the build passes after each move. For Next.js App Router:

src/
  app/          ← routes and page components
  components/   ← shared UI components
  lib/          ← utilities, helpers, third-party wrappers
  hooks/        ← custom React hooks
  types/        ← TypeScript type definitions

Use your IDE's "Move file" refactor to update imports automatically. Commit each directory move separately so the diff stays reviewable.