npm - whiteport-design-studio - Versions diffs - 0.2.2 → 0.3.0 - Mend

whiteport-design-studio 0.2.2 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (582) hide show

package/src/workflows/_agent-dialogs/project-analysis/analysis-types/folder-based-analysis.md DELETED Viewed

@@ -1,135 +0,0 @@
-# Folder-Based Analysis
-**You were routed here because**: Docs folder exists with recognizable structure
-**This is**: FALLBACK PATH (20-30 seconds)
----
-## What to Do
-Scan folder structure to determine project status, then suggest creating outline.
----
-## 1. Detect Methodology
-**Check folder patterns**:
-**WDS v6** (numbered): 1-project-brief, 2-trigger-mapping, 4-ux-design
-**WPS2C v4** (letters): A-Product-Brief, B-Trigger-Map, C-UX-Scenarios
-**Load methodology instructions**:
-- WDS v6: `methodology-instructions/wds-v6-instructions.md`
-- WPS2C v4: `methodology-instructions/wps2c-v4-instructions.md`
----
-## 2. Analyze YOUR Phases Only
-**Focus on phases in YOUR domain**:
-- **Saga**: Phases 1-2 (or A-B in v4)
-- **Freya**: Phases 4-5, 7 (or C-D in v4)
-- **Idunn**: Phases 3, 6 (or C-Platform, E-PRD in v4)
-**For each phase in your domain**:
-1. Folder exists? (Yes/No)
-2. Files inside? (Count)
-3. Status? (✅ Complete | 🔄 In Progress | 📋 Not started)
-**Briefly check other phases**: Just folder exists + file count
----
-## 3. Present Status
-**Format**:
-```
-Current Project Status:
-[STATUS] Phase [N]: [Name] ([Status])
-   ├─ [X] files found
-   └─ [Key observation]
-[Other phases - brief]
-Phase [N]: [Name] - [X] files
-💡 Tip: Create project outline for instant future analysis!
-Saga WDS Analyst Agent can create this during Product Brief.
-This will make analysis <5s instead of 30s.
-```
----
-## 4. Suggest Next Actions
-**Load your domain file**:
-- Saga: `../agent-domains/saga-domain.md`
-- Freya: `../agent-domains/freya-domain.md`
-- Idunn: `../agent-domains/idunn-domain.md`
-**Present 2-4 options** (with outline suggestion):
-```
-💡 What would you like to work on?
-1. [Task in YOUR domain] - I can help with this
-2. [Another task in YOUR domain]
-3. Create project outline for faster future analysis
-4. [Task needing handoff] - [Other Agent] specializes in this
-```
----
-## Example Output (Freya)
-```
-🎨 Freya WDS Designer Agent
-Analyzing project folders...
-Detected: WPS2C v4 methodology (letter folders)
-Current Project Status:
-✅ Phase A: Product Brief (Complete)
-   └─ 1 product brief document found
-🔄 Phase C: Scenarios (In Progress)
-   ├─ 2 scenario folders found
-   ├─ Scenario 01: 9 specification files
-   └─ Scenario 02: Empty (not started)
-Other phases:
-Phase B: Trigger Map - 3 files
-Phase D: Design System - Empty folder
-💡 Tip: Create project outline for instant analysis!
-Saga WDS Analyst Agent can create this during Product Brief.
-💡 What would you like to work on?
-1. Continue Scenario 01 - I can help design more pages
-2. Start Scenario 02
-3. Create project outline for faster future analysis
-4. Define technical requirements - Idunn WDS PM Agent specializes in this
-Which would you like to focus on?
-```
----
-## After User Responds
-**If task in YOUR domain**: Continue in same conversation
-**If task in ANOTHER domain**: Use `../05-agent-handoff-guide.md`
-**If "create outline"**: Hand over to Saga WDS Analyst Agent
----
-**Total time: 20-30 seconds**
-**Suggest**: Creating outline to make this <5s next time

package/src/workflows/_agent-dialogs/project-analysis/analysis-types/new-project-response.md DELETED Viewed

@@ -1,235 +0,0 @@
-# New Project Analysis
-**You were routed here because**: No docs folder exists at all
-**Analysis type**: Complete project scan
----
-## What to Do
-No docs/ folder means either brand new project or non-WDS project. Perform complete analysis of what exists, then **route to Phase 0 for proper project setup**.
----
-## 1. Scan Attached Repos
-**Check ALL repos attached to IDE** (exclude WDS, BMAD, WPS2C):
-For each project repo:
-- **Project name**: Extract from package.json, folder name, or README
-- **Tech stack**: Check package.json dependencies, frameworks
-- **Folder structure**: Check for app/, src/, components/, etc.
-- **Implementation status**: Any code implemented?
-- **Other docs**: Non-WDS documentation? (README, Wiki, etc.)
----
-## 2. Determine Project Type
-**Scenario A**: Completely empty repo (GREENFIELD)
-- Just .git/ and maybe README
-- Brand new project
-- No existing code
-**Scenario B**: Code exists, no WDS docs (BROWNFIELD)
-- Has app/, src/, components/
-- Active development without WDS methodology
-**Scenario C**: Non-WDS documentation exists
-- Has docs/ but different structure
-- Using different methodology
----
-## 3. Present Analysis & Route to Phase 0
-**Format**:
-```
-[Your Agent Icon] [Your Agent Name]
-Complete Project Analysis:
-📁 Project: [Name]
-🔧 Tech Stack: [List or "Not yet defined"]
-📂 Structure: [Describe what exists]
-WDS Documentation Status:
-└─ No docs/ folder found
-└─ No .wds-project-outline.yaml found
----
-[SCENARIO A - Empty Project / Greenfield]:
-Project Status: Brand new repository
-├─ Configuration: [package.json, tsconfig, etc. exist?]
-├─ README: [Exists? Contains what?]
-└─ Status: Ready for WDS setup
-🚀 **This is a GREENFIELD project!**
-Before we dive into design work, let's set up your project properly.
-This takes 3-5 minutes and ensures you follow the right workflow.
-→ **Starting Phase 0: Project Setup**
----
-[SCENARIO B - Code Without Docs / Brownfield]:
-Project Status: BROWNFIELD - Existing product, no WDS documentation
-├─ Implementation: [X] files in [app/src/] directory
-├─ Tech Stack: [List detected technologies]
-└─ Status: Active codebase detected
-Implementation found:
-├─ [Feature/file 1]
-├─ [Feature/file 2]
-└─ [Feature/file 3]
-⚠️ **This is a BROWNFIELD project!**
-You have existing code. Phase 0 will confirm the right approach
-(Phase 8 for improvements, not Phase 1-7 for new builds).
-→ **Starting Phase 0: Project Setup**
----
-[SCENARIO C - Different Methodology]:
-Project Status: Uses non-WDS documentation structure
-├─ Documentation: [Describe what exists]
-├─ Methodology: [Try to identify: Agile, Scrum, custom]
-└─ Status: Migration or custom setup needed
-Existing Documentation:
-├─ [File/folder 1]
-├─ [File/folder 2]
-└─ [File/folder 3]
-💡 You have existing methodology. Phase 0 will help you decide:
-- Migrate to WDS v6
-- Continue current approach (I'll adapt)
-- Set up custom WDS hybrid
-→ **Starting Phase 0: Project Setup**
-```
----
-## 4. Execute Phase 0
-**CRITICAL**: After presenting the analysis, immediately load and execute Phase 0.
-**Load**: `{project-root}/_bmad/wds/workflows/0-project-setup/steps/step-01-welcome.md`
-**Why Phase 0 first**:
-- Confirms greenfield vs brownfield (user validates your detection)
-- Configures project complexity, tech stack, brief level
-- Generates `.wds-project-outline.yaml` (enables fast path next time)
-- Routes to correct phase (1-7 for greenfield, 8 for brownfield)
-**DO NOT** skip Phase 0 and jump to Phase 1 or Phase 8 directly.
-Phase 0 takes 3-5 minutes and prevents hours of wrong-path work.
----
-## 5. Phase 0 Flow Summary
-```
-Phase 0: Project Setup
-    │
-    ├─→ Step 0.1: Welcome & Orientation
-    │       ├─→ Introduce WDS briefly
-    │       └─→ Confirm: "Greenfield or Brownfield?"
-    │           ├─→ [A] Greenfield (your Scenario A detection)
-    │           ├─→ [B] Brownfield (your Scenario B detection)
-    │           └─→ [C] Not sure (let user override)
-    │
-    └─→ Step 0.2: Configuration & Structure
-            ├─→ Project name
-            ├─→ Product complexity (landing/website/app)
-            ├─→ Tech stack (optional)
-            ├─→ Component library (optional)
-            ├─→ Brief level (complete/simplified)
-            ├─→ Strategic analysis (full/VTC/skip)
-            ├─→ Create folder structure
-            └─→ Generate .wds-project-outline.yaml
-                    │
-                    ├─→ Greenfield → Phase 1: Project Brief
-                    └─→ Brownfield → Phase 8: Product Evolution
-```
----
-## 6. Example: Saga Detecting New Project
-```
-📚 Saga - WDS Analyst
-Complete Project Analysis:
-📁 Project: kalla-fordonservice (from folder name)
-🔧 Tech Stack: Not yet defined
-📂 Structure: Empty repository
-WDS Documentation Status:
-└─ No docs/ folder found
-└─ No .wds-project-outline.yaml found
-Project Status: Brand new repository
-├─ Configuration: None
-├─ README: None
-└─ Status: Ready for WDS setup
-🚀 **This is a GREENFIELD project!**
-Before we dive into design work, let's set up your project properly.
-This takes 3-5 minutes and ensures you follow the right workflow.
----
-**Phase 0: Project Setup**
-Welcome to Whiteport Design Studio (WDS)!
-WDS is a design methodology that helps you create great digital products
-through structured workflows.
-**What type of project is this?**
-[A] NEW Product (Greenfield)
-    You're building something from scratch.
-    → Leads to Phase 1: Project Brief
-[B] EXISTING Product (Brownfield)
-    You're improving something that exists.
-    → Leads to Phase 8: Product Evolution
-[C] NOT SURE
-    → We'll analyze together
-Your choice (A, B, or C):
-```
----
-## After Phase 0 Completes
-Once `.wds-project-outline.yaml` is generated:
-- Future agent activations use **fast path** (<5 seconds)
-- Project configuration is preserved
-- Correct workflow is pre-determined
-**Activation complete** - User is now in Phase 1 or Phase 8.
----
-**Total time: 3-5 minutes** (Phase 0 setup)
-**Future activations: <5 seconds** (outline exists)

package/src/workflows/_agent-dialogs/project-analysis/analysis-types/outline-based-analysis.md DELETED Viewed

@@ -1,238 +0,0 @@
-# Outline-Based Analysis
-**You were routed here because**: Project outline exists
-**This is**: FAST PATH (<5 seconds)
----
-## What to Do
-Read `.wds-project-outline.yaml` and present status based on its contents.
----
-## 1. Read the Outline
-Location: `docs/.wds-project-outline.yaml` OR `.wds-project-outline.yaml`
-**Extract**:
-```yaml
-methodology:
-  type: "wds-v6" | "wps2c-v4" | "custom"
-phases:
-  phase_1_project_brief:
-    active: true/false
-    status: "not_started" | "in_progress" | "complete"
-    intent: "[User's goals]"
-  phase_4_ux_design:
-    active: true
-    status: "in_progress"
-    scenarios:
-      - id: "01-scenario"
-        status: "complete"
-        pages_specified: 9
-        pages_implemented: 5
-```
----
-## 2. Check for Agent Dialog Files (Context Loading)
-**Look for conversation history:**
-1. **Find dialog folder:**
-   - From outline, get `root_folder` (e.g., "docs", "design-process")
-   - Check: `{{root_folder}}/progress/dialog/progress-tracker.md`
-2. **If dialog files exist:**
-   - **Read `dialog/progress-tracker.md`**: Shows which PB steps are complete, current status
-   - **Read `dialog/00-context.md`**: Working relationship context (stakes, involvement level, recommendation style)
-   - **Read `dialog/decisions.md`**: Key decisions made during discovery
-   - **Read relevant step dialogs** (02-vision.md, 07-positioning.md, etc.) if needed for deeper context
-3. **What you learn from dialogs:**
-   - **Progress:** Which steps completed, which in progress
-   - **Context:** User's role, stakes, how directive to be
-   - **Decisions:** Why choices were made, what was explored
-   - **Tone:** How user prefers to work (collaborative, autonomous, etc.)
-   - **Conversation history:** Actual exchanges, what user said vs what agent synthesized
-4. **If no dialog files:**
-   - Fresh start, no prior conversation context
-   - You'll learn about the project from outline and artifacts only
-**Why this matters:** Dialog files let you continue seamlessly rather than asking questions that were already answered. If user discussed positioning rationale in detail 3 weeks ago, you don't re-ask - you already know.
-**Time**: Add 3-5 seconds if dialogs exist (read 3-4 files)
----
-## 3. Fast Validation (Tier 1)
-**Purpose**: Quick reality check to catch obvious outline drift
-**Why keep it silent**: Users care about their project progress, not technical file validation. Only surface validation if there's a problem worth discussing.
-**What to check** (internally):
-1. **Phase folders exist** - Does the outlined structure match reality?
-2. **Artifacts roughly match** - Are the claimed files actually there?
-3. **Major discrepancies** - Anything significantly wrong?
-**When to mention validation**:
-- ✅ Major issue found: "I noticed the outline mentions X, but I can't find it. Shall we update the outline or recreate the missing work?"
-- ✅ Everything matches: Don't mention validation at all, just present status
-**Time**: Add 2-3 seconds (total: 10-13 seconds with dialogs)
----
-## 4. Present Status
-**Purpose**: Show the project work - all active phases, what's been done, what needs doing.
-**Show ALL active phases** from the outline (not filtered by agent):
-**Suggested presentation format**:
-```
-Current Project Status:
-[STATUS] Phase [N]: [Name] ([Status])
-   ├─ Intent: "[User's exact words from outline]"
-   ├─ [What's been created - describe the work]
-   └─ [What's the progress]
-[For skipped phases:]
-⏭️  Phase [N]: [Name] (Skipped)
-   └─ Reason: [skip_reason from outline]
-```
-**Status Icons** (suggested):
-- ✅ Complete
-- 🔄 In Progress
-- 📋 Ready to start
-- ⏭️ Skipped
-**Talk about the work**: Focus on what's been designed/created, creative progress, user experiences - not files or folders.
----
-## 5. Show Work Details
-**If Phase 4 (UX Design) has scenarios**, show scenario progress:
-```
-Scenario Progress:
-├─ Scenario 01: [Name] ([Status])
-│   └─ [Brief description of what's been designed]
-├─ Scenario 02: [Name] ([Status])
-│   └─ [Brief description]
-└─ Scenario 03: [Name] ([Status])
-    └─ [Brief description]
-```
-**For other phases**, show relevant work details from the outline.
----
-## 6. Ask What User Wants to Work On
-**Present all possible work** (not filtered by agent domain):
-```
-💡 What would you like to work on?
-[List all active work across all phases:]
-1. [Task from any phase]
-2. [Another task from any phase]
-3. [Task from different phase]
-4. [Alternative task]
-Tell me what you would like to work on!
-```
-**After user selects**, route to appropriate work-type file based on selection.
----
-## 7. Route Based on User Selection
-**Determine work type** from user's selection:
-**Strategy & Research work** → `../work-types/strategy-work.md`
-**Design & UX work** → `../work-types/design-work.md`
-**Technical & Platform work** → `../work-types/technical-work.md`
-**Testing & Validation work** → `../work-types/testing-work.md`
-The work-type file will recommend the appropriate agent if needed.
----
-## Example Output (Suggested - Agent Agnostic)
-**This is a suggested way to present ALL project work, not filtered by agent**:
-```
-Current Project Status:
-✅ Phase 1: Product Brief (Complete)
-   └─ Vision and strategy established
-✅ Phase 2: Trigger Map (Complete)
-   └─ Users and journeys mapped
-✅ Phase 3: Platform Requirements (Complete)
-   └─ Tech stack and architecture defined
-🔄 Phase 4: UX Design (In Progress)
-   ├─ Intent: "Create 2-3 landing pages for developer handoff"
-   ├─ Scenario 01 (Customer Onboarding): Complete
-   │   └─ Welcoming flow for first-time users designed
-   ├─ Scenario 02 (Family Invitation): Ready to start
-   │   └─ Invitation experience needs design
-   └─ Scenario 03 (Calendar Booking): Specified with prototype
-       └─ Swedish week-based calendar ready for implementation
-⏭️  Phase 5: Design System (Skipped)
-   └─ Reason: Using shadcn/ui component library
-📋 Phase 7: Testing (Ready to start)
-   └─ Validation of Swedish week calendar and mobile UX
-💡 What would you like to work on?
-1. Design the family invitation experience (Scenario 02)
-2. Refine the onboarding flow (Scenario 01)
-3. Build interactive prototype for calendar
-4. Validate implementation against design specs
-5. Test Swedish week calendar logic
-6. Review Product Brief or Trigger Map
-Tell me what you would like to work on!
-```
-**Note**: This presents ALL work, letting the user choose. The work-type routing will then determine which agent is best suited.
----
-## After User Selects
-**Route to work-type file** based on what they chose:
-- Strategy/research work → `../work-types/strategy-work.md`
-- Design/UX work → `../work-types/design-work.md`
-- Technical/platform work → `../work-types/technical-work.md`
-- Testing/validation work → `../work-types/testing-work.md`
-**Before starting work**, perform Tier 2 validation:
-→ See: `../validation/deep-validation-before-work.md`
----
-**Total time: 7-8 seconds** (with Tier 1 validation)