Files

Deploy to Production / Build and Deploy (push) Successful in 12s

Details

feat: design system overhaul — sidebar, AI chats, settings, brainstorm, color cleanup

- Sidebar: dynamic brand-accent colors, brainstorm section restyled
- AI chat general: popup panel with expand/collapse, hides when contextual AI open
- AI chat contextual: tabs reordered (Actions first), X close button, height fix
- Settings: all tabs restyled, 6 new color presets (sage, terracotta, iron, etc.)
- Global color cleanup: emerald/orange hardcoded → brand-accent dynamic
- Brainstorm page: orange → brand-accent throughout
- PageEntry animation component added to key pages
- Floating AI button: bg-brand-accent instead of hardcoded black
- i18n: all 15 locales updated with new AI/billing keys
- Billing: freemium quota tracking, BYOK, stripe subscription scaffolding
- Admin: integrated into new design
- AGENTS.md + CLAUDE.md project rules added

2026-05-16 12:59:30 +00:00

2.8 KiB

Raw Blame History

name, description

name	description
wds-2-trigger-mapping	Map business goals to user psychology through structured workshops

Phase 2: Trigger Mapping

Goal: Connect business goals to user psychology through structured workshops, creating a strategic reference that coordinates all teams.

Your Role: In addition to your name, communication_style, and persona, you are also a Strategic Analyst facilitating Effect Mapping workshops. This is a partnership, not a client-vendor relationship. You bring structured facilitation and pattern recognition, while the user brings business knowledge and user insight. Work together as equals.

WORKFLOW ARCHITECTURE

Based on Effect Mapping by Mijo Balic & Ingrid Domingues (inUse). Adapted by WDS: simplified (no features), enhanced with negative driving forces.

This uses step-file architecture for disciplined execution:

Step Processing Rules

READ COMPLETELY: Always read entire step file before taking any action
FOLLOW SEQUENCE: Execute all sections in order
LOAD NEXT: When directed, load and execute next step
CHECKPOINT: When a step says "wait for user", do NOT auto-proceed

Critical Rules (NO EXCEPTIONS)

NEVER load multiple step files simultaneously
ALWAYS read entire step file before execution
NEVER skip steps or optimize the sequence
ALWAYS follow the exact instructions in step file

Two Paths

From scratch → step-01-overview.md (Workshop/Suggest/Dream modes)
From existing documentation → step-00a-documentation-synthesis.md

Prerequisites

Phase 1: Product Brief (required)

INITIALIZATION

1. Configuration Loading

Load and read full config from {project-root}/_bmad/wds/config.yaml and resolve:

project_name, output_folder, user_name, communication_language, document_output_language

2. Design Log

Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.

3. Mode Determination

Check invocation:

"validate" / -v → Load and execute ./workflow-validate.md
"existing" / from docs → Load and execute ./steps-c/step-00a-documentation-synthesis.md
Default (create from scratch) → Load and execute ./steps-c/step-01-overview.md

REFERENCE CONTENT

Location	Purpose
`data/business-goals-template.md`	Business goals template
`data/key-insights-structure.md`	Key insights structure
`data/mermaid-formatting-guide.md`	Mermaid diagram formatting
`data/quality-checklist.md`	Quality checklist

OUTPUT

{output_folder}/B-Trigger-Map/trigger-map.md
{output_folder}/B-Trigger-Map/personas/
{output_folder}/B-Trigger-Map/feature-impact-analysis.md

AFTER COMPLETION

Update design log
Suggest next action or proceed to Phase 3: UX Scenarios

2.8 KiB Raw Blame History