initial commit
This commit is contained in:
@@ -0,0 +1,113 @@
|
||||
---
|
||||
name: 'step-01-load-context'
|
||||
description: 'Load all inputs needed for wireframe generation from page specifications and design system'
|
||||
nextStepFile: './step-02-inventory.md'
|
||||
---
|
||||
|
||||
# Step 1: Load Context
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Load all inputs needed to generate wireframes — page specifications, design system layout rules, and any existing wireframe references — establishing the complete context for wireframe generation.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner loading wireframe generation context
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring systematic context loading, user brings project specifics
|
||||
- ✅ Maintain a thorough, organized tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on loading and summarizing wireframe context
|
||||
- 🚫 FORBIDDEN to generate wireframes or select styles in this step
|
||||
- 💬 Load page specs, design system layout tokens, and existing wireframes
|
||||
- 📋 Present a clear context summary before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document context summary
|
||||
- 📖 Check `{output_folder}/E-Assets/wireframes/` for existing assets
|
||||
- 🚫 FORBIDDEN to skip any context source
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Project configuration, page specifications, design system
|
||||
- Focus: Loading all inputs needed for wireframe generation
|
||||
- Limits: Do not start generating — just load context
|
||||
- Dependencies: Page specifications and design system must exist
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load Page Specifications
|
||||
|
||||
Read page specs from `{output_folder}/C-Scenarios/`: page structure and layout requirements, content zones and hierarchy, responsive breakpoints, navigation patterns.
|
||||
|
||||
### 2. Load Design System
|
||||
|
||||
Read layout tokens: grid system (columns, gutters, margins), spacing scale, breakpoint definitions, container widths.
|
||||
|
||||
### 3. Check Existing Wireframes
|
||||
|
||||
Scan `{output_folder}/E-Assets/wireframes/` for previously generated wireframes and approved reference wireframes.
|
||||
|
||||
### 4. Present Context Summary
|
||||
|
||||
```
|
||||
Wireframe Context:
|
||||
- Pages to wireframe: [list from specs]
|
||||
- Grid: [columns] / [gutter] / [margins]
|
||||
- Breakpoints: [list]
|
||||
- Existing wireframes: [count] found
|
||||
```
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save context summary, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
- User can chat or ask questions — always respond and then end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and context is summarized will you load {nextStepFile} to begin building the wireframe inventory.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Page specifications loaded
|
||||
- Design system layout tokens loaded
|
||||
- Existing wireframes checked
|
||||
- Context summary presented
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting wireframe generation without context
|
||||
- Not checking for existing wireframes
|
||||
- Skipping design system tokens
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,98 @@
|
||||
---
|
||||
name: 'step-02-inventory'
|
||||
description: 'Identify all pages needing wireframes and organize for batch generation'
|
||||
nextStepFile: './step-03-select-style.md'
|
||||
---
|
||||
|
||||
# Step 2: Asset Inventory
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Identify all pages and views that need wireframes, check what already exists, and let the user select the generation scope.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner organizing wireframe inventory
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring systematic inventory methodology, user brings scope decisions
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on cataloging pages for wireframe generation
|
||||
- 🚫 FORBIDDEN to generate wireframes in this step
|
||||
- 💬 Cross-reference with existing wireframes to avoid duplicates
|
||||
- 📋 Wait for user scope selection before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document inventory with existing/needed counts
|
||||
- 🚫 FORBIDDEN to proceed without user scope selection
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Wireframe context from Step 1
|
||||
- Focus: Building the generation-ready inventory
|
||||
- Limits: Do not generate — just catalog
|
||||
- Dependencies: Context from Step 1
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. List All Pages
|
||||
|
||||
From loaded page specs, create a list with page name, views (Desktop, Mobile), and priority.
|
||||
|
||||
### 2. Check What Exists
|
||||
|
||||
Cross-reference with `{output_folder}/E-Assets/wireframes/`: mark existing, identify outdated (spec changed after generation).
|
||||
|
||||
### 3. Present Inventory
|
||||
|
||||
Show total pages, already wireframed count, need wireframes count, need update count. Ask user to confirm scope: All, Select specific, or Missing only.
|
||||
|
||||
### 4. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save inventory and scope, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and scope is confirmed will you load {nextStepFile} to begin selecting wireframe style.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All pages cataloged with views and priority
|
||||
- Existing wireframes identified
|
||||
- User selected generation scope
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting generation without inventory
|
||||
- Not cross-referencing existing wireframes
|
||||
- Not waiting for user scope selection
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,105 @@
|
||||
---
|
||||
name: 'step-03-select-style'
|
||||
description: 'Choose wireframe fidelity level, design style influence, and annotation options'
|
||||
nextStepFile: './step-04-generate.md'
|
||||
---
|
||||
|
||||
# Step 3: Select Style
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Choose the visual approach for wireframe generation — fidelity level, design style influence, annotation preferences, and output dimensions.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner defining wireframe visual standards
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring wireframe design expertise, user brings aesthetic preferences
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on defining wireframe style parameters
|
||||
- 🚫 FORBIDDEN to generate wireframes in this step
|
||||
- 💬 Present clear fidelity options with descriptions
|
||||
- 📋 Confirm complete style configuration before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document complete wireframe style configuration
|
||||
- 📖 Load design style from `data/styles/design-styles/` for layout influence
|
||||
- 🚫 FORBIDDEN to proceed without confirmed style
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Wireframe inventory (Step 2), design system
|
||||
- Focus: Defining wireframe style parameters
|
||||
- Limits: Do not generate — just define style
|
||||
- Dependencies: Inventory and scope from Step 2
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Select Fidelity Level
|
||||
|
||||
Present: [L] Low-Fi (boxes and labels), [M] Mid-Fi (recognizable components, basic typography), [H] High-Fi (near-realistic with placeholder content).
|
||||
|
||||
### 2. Load Design Style Influence
|
||||
|
||||
Load selected design style from `data/styles/design-styles/` to extract layout principles and spacing feel.
|
||||
|
||||
### 3. Select Annotation Options
|
||||
|
||||
[Y] Yes (label content zones, note responsive behavior, mark interactions) or [N] No (clean wireframes only).
|
||||
|
||||
### 4. Confirm Style
|
||||
|
||||
Present: fidelity, design influence, annotations, dimensions (Desktop width, Mobile width).
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save style, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and style is confirmed will you load {nextStepFile} to begin generating wireframes.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Fidelity level selected
|
||||
- Design style influence loaded
|
||||
- Annotation preference set
|
||||
- Complete style confirmed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating without defined style
|
||||
- Not offering fidelity options
|
||||
- Skipping design style influence
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
name: 'step-04-generate'
|
||||
description: 'Craft optimized prompts and generate wireframes through MCP service or prompt export'
|
||||
nextStepFile: './step-05-review.md'
|
||||
---
|
||||
|
||||
# Step 4: Generate Wireframes
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Craft optimized prompts from context and style, generate wireframes through MCP service or export prompts for external tools, using approved results as references for batch consistency.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner executing wireframe generation
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring prompt crafting and generation expertise, user brings approval decisions
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Generate one wireframe at a time, getting approval before continuing
|
||||
- 🚫 FORBIDDEN to batch-generate without approval on first result
|
||||
- 💬 Use approved wireframes as reference for consistency
|
||||
- 📋 Track and display batch progress
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Track progress per page/view
|
||||
- 📖 Chain approved results as references for subsequent generations
|
||||
- 🚫 FORBIDDEN to skip per-page approval
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Inventory (Step 2), style configuration (Step 3)
|
||||
- Focus: Crafting prompts and executing generation
|
||||
- Limits: Generate only — full set review happens in Step 5
|
||||
- Dependencies: Confirmed style and scoped inventory
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Craft Prompt Template
|
||||
|
||||
Build base prompt from context + style: fidelity, grid description, content zones, style influence keywords, dimensions, grayscale palette, annotation preference.
|
||||
|
||||
### 2. Customize Per Page
|
||||
|
||||
Insert page-specific content zones, navigation state, and unique layout requirements.
|
||||
|
||||
### 3. Select Service
|
||||
|
||||
[G] Generate via MCP or [E] Export prompts for external tool.
|
||||
|
||||
### 4. Execute Generation
|
||||
|
||||
MCP path: send prompts sequentially, attach approved results as reference for consistency. Export path: save formatted prompts to `{output_folder}/E-Assets/wireframes/prompts/`.
|
||||
|
||||
### 5. Track Progress
|
||||
|
||||
Display completion status per page/view.
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save generated wireframes, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and all scoped wireframes are generated will you load {nextStepFile} to begin reviewing the set.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Prompts crafted from context and style
|
||||
- Wireframes generated with reference chaining
|
||||
- Progress tracked per page/view
|
||||
- Service selection respected
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Batch-generating without first-result approval
|
||||
- Not using references for consistency
|
||||
- Skipping progress tracking
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
112
_bmad/wds/workflows/6-asset-generation/steps-w/step-05-review.md
Normal file
112
_bmad/wds/workflows/6-asset-generation/steps-w/step-05-review.md
Normal file
@@ -0,0 +1,112 @@
|
||||
---
|
||||
name: 'step-05-review'
|
||||
description: 'Review generated wireframes as a set for consistency and iterate on flagged items'
|
||||
workflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 5: Review and Iterate
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Review all generated wireframes as a cohesive set, verify consistency across pages, iterate on any that need work, and save the final approved set.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner conducting quality review
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring visual consistency expertise, user brings final approval
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Review as a complete set, not individual wireframes in isolation
|
||||
- 🚫 FORBIDDEN to save without user approval
|
||||
- 💬 Present desktop and mobile side by side
|
||||
- 📋 Check grid alignment, navigation placement, typography hierarchy, spacing
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Save to `{output_folder}/E-Assets/wireframes/`
|
||||
- 📖 Check consistency: grid, navigation, typography, spacing, labels
|
||||
- 🚫 FORBIDDEN to skip consistency checks
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All generated wireframes, style configuration
|
||||
- Focus: Quality review and final approval
|
||||
- Limits: This is the final step — focus on quality and delivery
|
||||
- Dependencies: Generated wireframes from Step 4
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Present Full Set
|
||||
|
||||
Display all wireframes grouped by page, desktop and mobile side by side.
|
||||
|
||||
### 2. Consistency Check
|
||||
|
||||
Verify: grid alignment consistent, navigation placement consistent, typography hierarchy consistent, spacing uniform, content zones properly labeled (if annotations on).
|
||||
|
||||
### 3. User Review
|
||||
|
||||
Present: [A] Approve all, [R] Regenerate specific, [S] Style adjust and regenerate all, [E] Edit annotations.
|
||||
|
||||
### 4. Iterate
|
||||
|
||||
For flagged wireframes: gather feedback, adjust prompt, regenerate with approved wireframes as reference, re-review in context.
|
||||
|
||||
### 5. Save Approved Set
|
||||
|
||||
Save to `{output_folder}/E-Assets/wireframes/`: `{page-name}-desktop.png`, `{page-name}-mobile.png`, `wireframe-set-summary.md`.
|
||||
|
||||
### 6. Update Design Log
|
||||
|
||||
Record: wireframes generated count, style used (fidelity + design style), pages covered.
|
||||
|
||||
### 7. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF M: Save set, update design log, return to Activity Menu in {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
This is the final step of the Wireframes workflow. When M is selected and set is saved, return to the Activity Menu.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Full set presented for review
|
||||
- Consistency checks completed
|
||||
- User approved final set
|
||||
- Saved to correct output location
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Saving without user approval
|
||||
- Skipping consistency checks
|
||||
- Not updating design log
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user