Template

Files

Danijel Martinek 17d3488fb4 docs(guides): add TDD workflow + restructure adding-a-feature for TDD order

New: docs/guides/tdd-workflow.md — red-green-refactor cycle, AAA,
mocking decision tree, coverage targets, factory + contract usage.
Restructured: adding-a-feature.md interleaves tests with implementation;
TDD order is required, not optional. testing-strategy.md cross-links
the new guide. AGENTS.md and CLAUDE.md surface both.

Spec: §7

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-05 19:28:00 +02:00

2.7 KiB

Raw Blame History

Clean Architecture Monorepo Template

Quick Start

pnpm install          # Install all dependencies
pnpm dev              # Start all dev servers
pnpm build            # Build all packages
pnpm test             # Run all tests
pnpm turbo boundaries # Validate workspace dependency graph
docker compose up -d  # Start PostgreSQL

TDD

pnpm test --watch --filter @repo/<feature>   # watch one feature
pnpm test -- --coverage                      # full run with coverage
pnpm test:stories                            # Storybook smoke tests
pnpm test:e2e                                # Playwright e2e

See docs/guides/tdd-workflow.md for the full cycle.

Project Overview

Turborepo + pnpm monorepo organized by vertical features. Each feature (auth, blog, media, marketing-pages, navigation) owns its Clean Architecture layers. Core packages (core-shared, core-cms, core-api, core-trpc, core-ui) provide foundation. Two tooling packages (core-eslint, core-typescript) provide shared configs. Workspace boundaries are enforced by ESLint (lint-time) and Turborepo (build-graph time). Supports Next.js and TanStack Start as frontend frameworks, Payload CMS for content management, and comprehensive agent-optimized documentation.

Read First

AGENTS.md — Package map, boundary rules, per-package conventions
docs/architecture/overview.md — High-level architecture and package responsibilities
docs/architecture/vertical-feature-spec.md — Design spec with rationale and decision log
docs/guides/adding-a-feature.md — End-to-end new feature walkthrough

Key Conventions

Relative imports in src/ — Source files use relative paths (../repositories/...), not @/ alias
@/ alias in tests — Test files (*.test.ts) use @/ to import from src/
vitest.config.ts — Every package must define resolve.alias: { "@": path.resolve(__dirname, "./src") }
tsconfig.json rootDir — Set "rootDir": "." so TypeScript finds both src/ and test files
Payload repositories via constructor — Feature packages receive Payload config at constructor time, not as a direct dependency
App bootstrap — Each app calls bindProduction*() per feature at startup to wire Payload into InversifyJS containers

MCP Servers

Start Storybook before UI work: pnpm dev --filter @repo/storybook

Storybook MCP available at http://localhost:6006/mcp — use list-all-documentation to discover existing components before creating new ones.

Key Ports

Service	Port
Next.js	3000
Payload CMS	3001
TanStack Start	3002
PostgreSQL	5432
Storybook	6006

2.7 KiB Raw Blame History