Files
sar/.claude/skills/wds-4-ux-design/data/modular-architecture/02-workflows/storyboards-guide.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

1.4 KiB

Storyboard Integration

Using visual storyboards for complex components


Core Concepts (01-)

What Are Storyboards?

Visual documentation of state transitions and flows

When to Use Storyboards

Complexity indicators that require visual documentation

Storyboard Types

State transitions, interaction flows, multi-component sync


Storage & Organization (02-)

File Structure

Where to store storyboards in the three-tier architecture

Naming Conventions

How to name storyboard files


Creation Guidelines

How to Create Storyboards

Hand-drawn, digital, or annotated screenshots

Annotation Best Practices

Numbering, labels, and visual indicators


Integration

Referencing in Feature Files

How to link storyboards from specifications

Referencing in Component Files

Visual state references


Examples

TaskFlow Task States

6-state walk booking storyboard

Search Flow

Multi-step interaction storyboard


Benefits

Why Storyboards Work

Developer clarity, QA testing, design consistency