Skip to main content

Reference Folder Structure (Complex / Scalable)

This structure is the default recommendation for medium-high to complex vibe coding.

vibe-starterkit/
├── app/
├── bootstrap/
│   ├── new-project.sh
│   └── setup.sh
├── config/
├── database/
│   ├── migrations/
│   └── seeders/
├── docs/
│   ├── PRODUCT_REQUIREMENTS.md      (REQUIRED)
│   ├── PRODUCT_CHANGELOG.md         (REQUIRED)
│   ├── ARCH_DECISIONS.md            (REQUIRED)
│   ├── BUSINESS_FLOW.md             (REQUIRED)
│   ├── VIBE_CODING_FLOW.md          (recommended)
│   ├── STARTERKIT.md                (recommended)
│   ├── FEATURE_REQUEST_TEMPLATE.md  (recommended)
│   ├── api/openapi.yaml             (REQUIRED)
│   └── db/schema.dbml               (REQUIRED)
├── scripts/
│   ├── quality-gate.sh
│   ├── docs-guard.sh
│   ├── regenerate-docs.sh
│   ├── smoke-test.sh
│   ├── dev-up.sh
│   └── dev-down.sh
├── ai/
│   ├── agents/
│   │   ├── core/AGENT.md
│   │   ├── api/AGENT.md
│   │   ├── admin/AGENT.md
│   │   ├── data/AGENT.md
│   │   └── qa/AGENT.md
│   └── prompts/
│       ├── prd/
│       ├── implementation/
│       └── review/
└── (without docs portal in this repo)

Documentation repo (separate)​

vibe-starterkit-docs/
├── docs/
├── src/
├── static/
├── docusaurus.config.js
└── sidebars.js

Why this structure?​

  • easier team scaling
  • smaller per-module context
  • fewer cross-domain conflicts
  • easier auditing and maintenance