Files
sar/_bmad/wds/data/wds-glossary.md
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

4.5 KiB
Raw Blame History

WDS Glossary

Locked terminology for all WDS agents. One definition per term — no synonyms, no aliases. Agents load this file once at activation. Do not redefine these terms locally.


Phases

Phase Name Owner
0 Alignment & Signoff Saga
1 Product Brief Saga
2 Trigger Mapping Saga
3 UX Scenarios Freya
4 UX Design Freya
5 Agentic Development Mimir
6 Asset Generation Freya
7 Design System Freya
8 Product Evolution Mimir

Output Folder Structure

{output_folder}/
├── A-Product-Brief/       Phase 1 — strategic foundation
├── B-Trigger-Map/         Phase 2 — user research & personas
├── C-UX-Scenarios/        Phase 3 — journey flows
├── D-UX-Design/           Phase 4 — page specifications & design assets
└── E-Development/         Phase 5 — technical requirements, work orders, code

Progress files (machine-local, not committed):

progress/
├── [agent].md             Session state per agent
└── project-index.md       Living artifact index, updated on wrap

Artifacts

Strategy (Phase 1)

  • Product BriefA-Product-Brief/product-brief.md. Strategic foundation: vision, goals, constraints, target users. Required before any design work.
  • Content LanguageA-Product-Brief/content-language.md. Tone, vocabulary, brand voice.
  • Visual DirectionA-Product-Brief/visual-direction.md. Aesthetic references, colour, typography intent.

Research (Phase 2)

  • Trigger MapB-Trigger-Map/00-trigger-map.md. User psychology mapped to business goals. Required before UX Scenarios.
  • Business GoalsB-Trigger-Map/01-business-goals.md. Measurable outcomes, KPIs.
  • PersonaB-Trigger-Map/NN-persona-[firstname]-the-[archetype].md. Alliterative names required (e.g. Harriet the Hairdresser).
  • Feature ImpactB-Trigger-Map/feature-impact.md. Feature × persona × trigger mapping.

Design (Phases 34)

  • UX ScenariosC-UX-Scenarios/00-ux-scenarios.md. User journey flows derived from Trigger Map.
  • Page SpecD-UX-Design/[page-name].md. Per-page specification: layout, content, interactions, acceptance criteria.
  • Design Tokens — Extracted progressively during Phase 4, not upfront.

Development (Phase 5)

  • Tech AuditE-Development/000-tech-audit.md. Living architecture document. Required before any PRD on an existing codebase.
  • Master PRDE-Development/000-PRD.md. Platform requirements, written once, updated as project evolves.
  • Feature PRDE-Development/NNN-[feature].xml. One per Work Order.
  • Change OrderE-Development/NNN-NN-[slug].xml. Feedback/change against a parent PRD.
  • Work OrderE-Development/WO-NNN-[slug].md. Task written by Freya for Mimir. Contains: objective, scope, files, acceptance criteria.
  • Mimir Brief — Narrative handoff document from Freya to Mimir when handing off design work.

Progress (machine-local)

  • Design Log_progress/00-design-log.md. Project-wide progress, updated each session.
  • Project Outline_progress/wds-project-outline.yaml. Phase status, project metadata.
  • Session Stateprogress/[agent].md. Agent-specific session state. Loaded by /start, written by /wrap.
  • Project Indexprogress/project-index.md. Living index of all artifacts, updated by /wrap.

Patterns

  • Design Loop — Freya's per-page cycle: discuss → spec → wireframe → approve → iterate → update spec → implement → browser review → extract tokens.
  • Dream Up Mode — Three modes for artifact generation: Dialog (collaborative), Suggest (agent proposes), Dream (agent generates fully). Selected at session start.
  • Brownfield — Project with an existing codebase. Triggers gap-map assessment before new work begins.
  • Greenfield — Project with no existing codebase. Follows standard phase progression.
  • Gap Map — Freya's cross-reference of what is designed vs what is built vs what has a Work Order.

Model Selection

Task type Model
Any code, build, deploy, implement Opus
High-stakes / production / compliance Opus
Long or complex multi-step tasks Opus
Strategy, spec, dialog, UX, analysis Sonnet
Simple, low-stakes, short Haiku

Default: lightest model that fits. Prefix Next actions with MODEL:[Haiku|Sonnet|Opus].