Julian/sar

Files

julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts

- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-27 14:34:20 +00:00

3.0 KiB

Raw Blame History

name, description

name	description
wds-0-project-setup	Project onboarding - determine project type, complexity, tech stack, and route to correct phase

Phase 0: Project Setup

The starting point for every WDS project.

Purpose

Phase 0 ensures you start on the right path. Before diving into design work, we need to understand:

What is WDS? - So you know what you're getting
What type of project? - New product vs existing product
How complex? - Landing page vs web application
What tech? - Framework and component library choices
What's the right workflow? - Route to the correct phase with right config

Why This Matters

The #1 mistake: Starting Phase 1 with an existing codebase.

Phase 1-7 = Building something NEW (Greenfield)
Phase 8 = Improving something EXISTING (Brownfield, Product Evolution)

Wrong path = wasted work. Phase 0 prevents this.

The Flow

Phase 0: Project Setup
    │
    ├─→ Step 01: Welcome
    │       ├─→ "What is WDS?" (quick intro)
    │       └─→ "Greenfield or Brownfield?"
    │
    └─→ Step 02: Configuration
            ├─→ Project name
            ├─→ Product complexity (landing/website/app)
            ├─→ Tech stack (optional)
            ├─→ Component library (optional)
            ├─→ Brief level (complete/simplified)
            ├─→ Strategic analysis (full/simplified/skip)
            ├─→ Create folder structure
            └─→ Generate project outline
                    │
                    ├─→ Greenfield → Phase 1 (→ Phase 2 if full analysis)
                    └─→ Brownfield → Phase 8

Steps

Step	Name	Purpose
01	Welcome & Orientation	Introduce WDS, determine greenfield vs brownfield
02	Configuration & Structure	Configure project, create folders, generate outline

Entry Point

Start here: steps/step-01-welcome.md

When to Use Phase 0

First time using WDS
Starting a new project
Joining an existing project
Unsure which workflow to use

When to Skip Phase 0

Project outline already exists (.wds-project-outline.yaml)
You know exactly which phase you need
Continuing work on established WDS project

Phase 0 takes 3-5 minutes. It saves hours of wrong-path work.

Configuration Options

Option	Values	Impact
Project Type	greenfield / brownfield	Determines Phase 1-7 (greenfield) vs Phase 8 (brownfield)
Complexity	simple / standard / complex	Which phases are enabled
Tech Stack	react / vue / wordpress / etc.	Delivery format guidance
Component Library	shadcn / tailwind / custom	Skip or enable Phase 5
Brief Level	complete / simplified	Depth of Phase 1
Strategic Analysis	full / simplified / skip	Full Trigger Map or simplified in brief

3.0 KiB Raw Blame History