Modern QA2026Step 4 — Decide the initial directory naming — tiles
Log inJoin
28 / 139 · 13 Browser Automation with Playwright · Quick Start Preparation: Turn Discovery into a Scaffolding-Ready Package← prev⊞ allnext →☰ Read as one page

2.8Step 4 — Decide the initial directory naming

Before Claude Code scaffolds, be explicit about the major top-level areas.

A strong default is:

src/
  core/
  ui/
    pages/
    components/
    flows/
    assertions/
  api/
    clients/
    builders/
    helpers/
    schemas/
    assertions/
  shared/
    data/
    factories/
    utils/
    state/
  fixtures/

tests/
  ui/
    smoke/
    regression/
    accessibility/
  api/
    smoke/
    regression/
    contract/
  hybrid/
  setup/

docs/
  architecture/
  standards/
  runbooks/
  specs/
  plans/
  agents/
  decisions/

scripts/
artifacts/
.github/workflows/

This structure is opinionated but practical. It keeps reusable code in src/, specs in tests/, and durable repo memory in docs/.