Files
sar/.claude/skills/wds-4-ux-design/data/page-creation-flows/workshop-page-process.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

5.0 KiB
Raw Blame History

Page Process Workshop

Purpose: Intelligent sketch analysis with context detection - handles both new and updated sketches


CONTEXT

This workflow activates when: User has a sketch/visualization ready to analyze.

Intelligence: Detects if this is a new page or update to existing specification.

Behavior:

  • New page → Full analysis
  • Updated page → Change detection, incremental update
  • Partial completion → Specify ready sections, mark TBD

STEP 1: CONTEXT DETECTION

**Determine page context:**
  1. Read current page specification (if exists)
  2. Check for existing sketch versions
  3. Identify project structure (scenarios, pages)
  4. Store context information
**This is the first sketch for this page!**

Let me analyze what you've drawn and create the initial specification.

Route to: ../../steps-k/step-01-sketch-analysis.md (existing workflow)

**I see we already have specifications for this page.**

Let me compare this sketch to what we have...

Proceed to STEP 2: Change Detection


STEP 2: CHANGE DETECTION (For Existing Pages)

**Compare new sketch to existing specifications:**
  1. Load existing specification document
  2. Identify which sections are already specified
  3. Analyze new sketch for:
    • Unchanged sections
    • Modified sections
    • New sections added
    • Removed sections
    • TBD sections now complete
    • Complete sections now TBD
  4. Calculate confidence for each comparison

Comparison Results:

See: page-process-templates.md for output templates

Display:

  • Unchanged sections ()
  • Modified sections (✏️)
  • New sections added ()
  • TBD sections now complete ()
  • Sections removed (⚠️)

STEP 3: UPDATE STRATEGY

How would you like to proceed?

[A] Update all changed/new/completed sections [B] Pick specific sections to update [C] Show me detailed comparison first [D] Actually, this is the same - cancel

Choice:

Store user_choice


STEP 4A: UPDATE ALL (If user chose A)

Updating all changed sections:

I'll process all modified, new, and completed sections while preserving unchanged sections.

Ready to analyze sections?

For each section in (modified_sections + new_sections + completed_sections): Run 4b-sketch-analysis.md workflow for that section only Update specification document Preserve unchanged sections End

STEP 4B: SELECTIVE UPDATE (If user chose B)

Which sections should I update?

[List numbered sections with change type]

Enter numbers separated by commas (e.g., 1,3,5):

Parse selected_sections For each selected section: Run 4b-sketch-analysis.md workflow for that section Update specification document End

STEP 4C: DETAILED COMPARISON (If user chose C)

Detailed Section-by-Section Comparison:

See: page-process-templates.md for comparison template

Display for each modified section:

  • Current specification summary
  • New sketch interpretation
  • Detected changes
  • Confidence level

After reviewing, what would you like to do?

[A] Update all [B] Pick specific sections [C] Cancel

Return to STEP 3 with user's choice


STEP 5: COMPLETION

Page specification updated!

Summary:

  • sections updated
  • sections added
  • sections preserved (unchanged)
  • sections removed

Updated file: {{page_spec_path}} Sketch saved to: {{sketch_path}}

Would you like to: [A] Generate HTML prototype [B] Add another page [C] Update another section [D] Done with this page

Choice:


ROUTING

Based on user choice: - [A] → Load prototype generation workflow - [B] → Return to page-init/step-01-page-context.md - [C] → Return to STEP 3 (pick sections) - [D] → Return to main UX design menu

KEY FEATURES

Intelligent Context Detection

  • Automatically knows if new or update
  • Compares sketches to existing specs
  • Identifies unchanged sections

Incremental Updates

  • Only updates what changed
  • Preserves existing work
  • No data loss

Flexible Control

  • Update all or select specific
  • See detailed comparison
  • Cancel anytime

INTEGRATION

This workshop uses:

  • 4b-sketch-analysis.md - For actual section analysis
  • guides/SKETCH-TEXT-ANALYSIS-GUIDE.md - For reading text markers
  • page-specification.template.md - For document structure
  • object-types/*.md - For component specifications

Created: December 28, 2025 For: Iterative page specification workflow Status: Ready to test with WDS Presentation page