# Folder Structure

> Folder structure for frontend and backend module placement. Use when creating files, deciding where a module belongs, or reviewing misplaced responsibilities across views, components, services, routes, data, or gateway. Don't use for coding style inside a file (use code-standards), React patterns (use react), or test conventions (use tests).

- Skill: `pedronauck/folder-structure` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add pedronauck/folder-structure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pedronauck/folder-structure/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: pedronauck (https://skillmd.com/u/pedronauck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pedronauck/folder-structure

---


# 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/src` and backend code under `backend/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`, or `misc`.

## 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.