Folder Structure
Place each module by its primary responsibility. Shape rules inside a file live in code-standards; React composition rules live in react.
Reference — general placement
- Keep frontend code under
frontend/srcand backend code underbackend/src. - Name files and folders in English.
- Put each module in the folder that matches its primary responsibility.
- Extract shared logic into an inward-facing module rather than duplicating across layers.
- Prefer a named responsibility folder over catch-alls like
utils,helpers, ormisc.
Branches
Match the task, then read the listed file in full before placing or moving code:
| When… | Read in full |
|---|---|
Creating or reviewing anything under frontend/src |
references/frontend.md |
Creating or reviewing anything under backend/src |
references/backend.md |
Reference — review gate
Before finishing, confirm every general placement rule holds and the branch file for each touched tree was applied in full.