The Perfect Project Folder Structure for Codex

The perfect folder is not the fanciest one. It is the one that helps Codex understand the project quickly, follow the rules, find the work, verify changes, and preserve decisions across sessions.

The goal is less noise: fewer repeated explanations, fewer stale assumptions, and a folder that can carry the work.

The simple structure

project-name/
  AGENTS.md
  README.md
  TASKS.md
  DECISIONS.md
  PROMPTS.md
  docs/
  screenshots/
  src/
  tests/
  scripts/

Not every project needs every file on day one. But Codex needs stable anchors: what this is, how to work here, what is current, what was decided, and what visual or product evidence matters.

What each file does

• AGENTS.md tells agents how to behave in the repo.
• README.md explains the project to humans.
• TASKS.md keeps the current work visible.
• DECISIONS.md prevents old choices from being relitigated.
• PROMPTS.md stores repeatable requests before they become skills.
• docs/ and screenshots/ preserve product context and visual direction.

The V8V method

V8V treats folder structure as part of the workflow. Skills make work reusable. Project folders make context reusable. Together, they let builders move faster without turning every session into a reset.

For a V8V content project, the folder should preserve catalog facts: 28 bundles, 93 verified skills, Complete Collection as the full-library offer, the current product names, and the quiet brand voice.

The bottom line

Codex works best when the project can explain itself. A strong folder structure gives the agent rules, context, decisions, tasks, prompts, and evidence. That means less time correcting assumptions and more time building.