Path fixes across 14 files:
- D-UX-Design/ → C-UX-Scenarios/ (page specs) or D-Design-System/ (tokens)
- 4-scenarios/ → C-UX-Scenarios/ (all step files and page creation flows)
New spacing & typography step in [P] Specify:
- step-08-spacing-typography.md defines section spacing objects and heading tokens
- Old step-08 renumbered to step-09, references updated to steps 1-8
[M] Design System extraction rules:
- Objects extract on 2nd use, spacing extracts immediately on 1st use
- Component extraction check before designing 2nd+ page
[S] Suggest step-15 alignment:
- Old [A]/[S]/[M] menu replaced with two-option transitions
- Matches the pattern used by [C] Conceptualize and workflow-suggest.md
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Spacing gets the same treatment as typography — named tokens, a baseline
(space-md), and optical adjustments using token math. But the real shift:
spacing between objects is now a first-class object with its own ID in
page specs, organized in a Patterns section in the design system.
Key additions:
- Spacing Scale: 9 tokens (space-3xs to space-3xl), bring-your-own supported
- Type Scale: 9 tokens (text-3xs to text-3xl), semantic/visual separation
- Optical adjustments: token math (space-lg - space-3xs) with annotations
- Spacing objects in page specs: ↕ `id` — token, including space-zero
- Patterns section: organized by spacing value, context added on violation
- Agent reflection behavior: observe and reflect, don't interrogate
- Design loop: pattern recognition emerges from real design decisions
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Design system template: spacing scale (9 tokens, space-3xs to space-3xl)
and type scale (9 tokens, text-3xs to text-3xl) with bring-your-own option.
Semantic heading level separated from visual text sizing — H1 can look
different on every page. Page spec template: spacing, typography, and
per-section padding/gap using token names. Design loop guide: 9 steps
(added APPROVE — user exports PNG as approval gate), spacing discipline,
export=approval pattern. Wireframe flow: agent draws, user reviews, user
exports PNG to confirm, then spec syncs.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The VTC (Value Trigger Chain) was a separate concept that extracted
specific nodes from the Trigger Map into a YAML file. This caused
agents to run trigger mapping during Phase 1 (Product Brief), forcing
users to repeat the work in Phase 2. Observed in Monday workshop.
Architectural fix:
- Phase 1 is casual business discovery, NOT trigger mapping
- Phase 2 is where the Trigger Map gets built (unchanged)
- When scenarios/content need strategic context, they reference
the Trigger Map directly — no separate VTC concept needed
Removed (19 files deleted):
- 1-project-brief/vtc-workshop/ (14 step files + workflow)
- step-04-create-vtc.md and step-11a-create-vtc.md from Phase 1
- step-03c-create-vtc.md from Phase 0 alignment
- vtc-template.yaml
Renamed:
- step-03-build-vtcs.md → step-03-build-strategic-context.md
- step-02-vtc-consistency.md → step-02-trigger-map-consistency.md
- step-01-load-vtc-context.md → step-01-load-trigger-map-context.md
- 07-create-vtc.md → 07-reference-trigger-map.md
Rewritten:
- Phase 4 scenario init: "create VTC" → lightweight "pick from Trigger Map"
- Phase 6 content: load context from Trigger Map, not from VTC
- Templates: "Trigger Map" section → "Business Context" (Phase 1 scope)
Zero VTC references remain in src/.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Suggest workflow: Component Extraction Check prompts user to extract
shared elements when starting the 2nd+ page in a scenario
- Dream workflow: Auto-extracts shared components and reports in summary
- Spec audit Level 3: Cross-Page Duplicate Detection compares sections
across all pages, flags exact/near duplicates with severity levels
- Fix Freya role name (Scenario Architect → Facilitator)
- Remove duplicate trigger-map reference in Eira guide
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Systematic cleanup of Value Trigger Chain (VTC) references in 60 files across
all phases. VTC is replaced with context-appropriate terms:
- "Trigger Map" when referencing the Phase 2 artifact
- "Strategic context" when referencing the extracted business/persona/forces data
- "Value Proposition" for customer-facing value descriptions
Remaining VTC references are only in VTC Workshop definition files (vtc-workshop/,
create-vtc steps) which will be addressed when those workflows are redesigned.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Mårten Angner