initial commit
This commit is contained in:
@@ -0,0 +1,114 @@
|
||||
---
|
||||
name: 'step-01-load-context'
|
||||
description: 'Load icon requirements from page specifications, design system, and existing icon references'
|
||||
nextStepFile: './step-02-inventory.md'
|
||||
---
|
||||
|
||||
# Step 1: Load Context
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Load all icon requirements from page specifications, design system icon tokens, and any existing icon assets — establishing the complete context needed for icon 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 icon 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 asset context loading, user brings project specifics
|
||||
- ✅ Maintain a thorough, organized tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on loading and summarizing icon context
|
||||
- 🚫 FORBIDDEN to generate icons or select styles in this step
|
||||
- 💬 Identify every icon reference across all page specs
|
||||
- 📋 Present a clear context summary before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document context summary with counts and categories
|
||||
- 📖 Check `{output_folder}/E-Assets/icons/` 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 icon generation
|
||||
- Limits: Do not start generating or styling — just load context
|
||||
- Dependencies: Page specifications and design system must exist
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load Icon Requirements
|
||||
|
||||
From page specs, identify every icon reference: navigation icons (menu, close, search, user, cart), action icons (edit, delete, save, share, download), status icons (success, warning, error, info), category/feature icons, social media icons, decorative icons.
|
||||
|
||||
### 2. Load Design System Icon Tokens
|
||||
|
||||
Read icon-related tokens: sizes (sm 16px, md 24px, lg 32px, xl 48px), stroke width (for outline style), color mode (monochrome or multicolor), container type (none, circle, rounded square).
|
||||
|
||||
### 3. Check Existing Icons
|
||||
|
||||
Scan `{output_folder}/E-Assets/icons/` for previously generated icons and check for external icon library references in the design system.
|
||||
|
||||
### 4. Present Context Summary
|
||||
|
||||
```
|
||||
Icon Context:
|
||||
- Total icons identified: [count]
|
||||
- Categories: [navigation, action, status, feature, social, decorative]
|
||||
- Existing icons: [count]
|
||||
- Icon size standard: [primary size]
|
||||
- Style direction: [outline/filled/duotone from design system]
|
||||
```
|
||||
|
||||
### 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 icon inventory.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All icon references identified from page specs
|
||||
- Design system icon tokens loaded
|
||||
- Existing icons checked
|
||||
- Context summary presented with clear counts
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting icon generation without full context
|
||||
- Missing icon categories from page specs
|
||||
- Not checking for existing assets
|
||||
- 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,114 @@
|
||||
---
|
||||
name: 'step-02-inventory'
|
||||
description: 'Build a complete icon inventory organized by category, usage, and batch opportunity'
|
||||
nextStepFile: './step-03-select-style.md'
|
||||
---
|
||||
|
||||
# Step 2: Asset Inventory
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Build a complete, deduplicated icon inventory organized by category and usage, identifying batch opportunities and letting 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 icon 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
|
||||
- ✅ Maintain an organized, catalog-focused tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on cataloging and organizing icons for generation
|
||||
- 🚫 FORBIDDEN to generate icons or select styles in this step
|
||||
- 💬 Deduplicate icons used across multiple pages
|
||||
- 📋 Present generation scope options and wait for user selection
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document complete icon catalog with batch groups
|
||||
- 📖 Merge cross-page duplicates and note size variants
|
||||
- 🚫 FORBIDDEN to proceed without user scope selection
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Icon context from Step 1
|
||||
- Focus: Organizing icons into a generation-ready inventory
|
||||
- Limits: Do not generate or style — just catalog and organize
|
||||
- Dependencies: Context summary from Step 1
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Build Icon Catalog
|
||||
|
||||
Create a table: icon name, category, used on (pages), sizes needed.
|
||||
|
||||
### 2. Deduplicate
|
||||
|
||||
Merge icons used across multiple pages, note all size variations needed, identify similar icons that could share a base (arrow variants, etc.).
|
||||
|
||||
### 3. Estimate Batch Size
|
||||
|
||||
Count unique icons, size variants, total assets. Identify similar icon groups for batch generation (arrows, social, CRUD actions).
|
||||
|
||||
### 4. Present Inventory with Scope Options
|
||||
|
||||
```
|
||||
[A] All icons — Generate complete icon set
|
||||
[C] Category — Select specific categories
|
||||
[S] Select individual — Pick specific icons
|
||||
[P] Priority only — Navigation + action icons first
|
||||
```
|
||||
|
||||
Wait for user selection.
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save inventory and scope selection, 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 scope is confirmed will you load {nextStepFile} to begin selecting icon style.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Complete icon catalog built with all categories
|
||||
- Duplicates merged, size variants noted
|
||||
- Batch groups identified
|
||||
- User selected generation scope
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting generation without inventory
|
||||
- Missing icons from page specs
|
||||
- Not deduplicating cross-page icons
|
||||
- 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,114 @@
|
||||
---
|
||||
name: 'step-03-select-style'
|
||||
description: 'Define the icon style including outline weight, fill treatment, grid, and color mode'
|
||||
nextStepFile: './step-04-generate.md'
|
||||
---
|
||||
|
||||
# Step 3: Select Style
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Define the complete icon style — outline weight, fill treatment, grid alignment, and color mode — ensuring visual consistency rules are established before generation begins.
|
||||
|
||||
## 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 icon 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 icon design system expertise, user brings aesthetic preferences
|
||||
- ✅ Maintain a design-focused, precise tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on defining icon style parameters
|
||||
- 🚫 FORBIDDEN to generate any icons in this step
|
||||
- 💬 Present clear options for each style dimension
|
||||
- 📋 Confirm complete style configuration before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document complete icon style configuration
|
||||
- 📖 Align style choices with design system tokens
|
||||
- 🚫 FORBIDDEN to proceed without confirmed style
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Icon inventory (Step 2), design system tokens
|
||||
- Focus: Defining visual style rules for icon generation
|
||||
- Limits: Do not generate — just define the style
|
||||
- Dependencies: Icon inventory and scope from Step 2
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Select Icon Style
|
||||
|
||||
Present options: [O] Outline, [F] Filled, [D] Duotone, [G] Glyph. Wait for selection.
|
||||
|
||||
### 2. Configure Style Parameters
|
||||
|
||||
Based on selection, configure detailed parameters:
|
||||
- Outline: stroke width, line cap, line join, corner radius
|
||||
- Filled: fill style, corner radius
|
||||
- Duotone: primary color, secondary opacity
|
||||
|
||||
### 3. Define Grid and Alignment
|
||||
|
||||
Canvas size (e.g., 24x24 with 2px padding = 20x20 live area), pixel grid alignment, optical sizing rules.
|
||||
|
||||
### 4. Select Color Treatment
|
||||
|
||||
Present options: [M] Monochrome (currentColor), [B] Brand colors (category distinction), [F] Fixed color (specific hex per icon).
|
||||
|
||||
### 5. Confirm Style
|
||||
|
||||
Present complete configuration summary: style, parameters, grid, color, output format (SVG primary, PNG fallback).
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save style configuration, 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'
|
||||
- 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 the style is confirmed will you load {nextStepFile} to begin generating icons.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Icon style selected and parameters configured
|
||||
- Grid and alignment rules defined
|
||||
- Color treatment selected
|
||||
- Complete style summary confirmed by user
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating icons without defined style
|
||||
- Not configuring detailed parameters for selected style
|
||||
- Skipping grid alignment definition
|
||||
- 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,118 @@
|
||||
---
|
||||
name: 'step-04-generate'
|
||||
description: 'Batch-generate icons with consistent style across the entire set'
|
||||
nextStepFile: './step-05-review.md'
|
||||
---
|
||||
|
||||
# Step 4: Generate Icons
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Batch-generate icons with consistent style across the entire set, processing related icons in groups for maximum visual consistency and using approved results as references for subsequent icons.
|
||||
|
||||
## 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 icon 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 batch generation expertise, user brings approval decisions
|
||||
- ✅ Maintain an efficient, production-focused tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Generate icons in groups for consistency (navigation, action, status, feature, social)
|
||||
- 🚫 FORBIDDEN to skip group-by-group approval
|
||||
- 💬 Get approval on first icon of each group before batch-generating the rest
|
||||
- 📋 Track progress and display completion status
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Track generation progress per group
|
||||
- 📖 Use approved icons as references for subsequent generations
|
||||
- 🚫 FORBIDDEN to batch-generate without approval of first icon in group
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Icon inventory (Step 2), style configuration (Step 3)
|
||||
- Focus: Crafting prompts and executing icon generation
|
||||
- Limits: Generate only — review as a complete set happens in next step
|
||||
- Dependencies: Confirmed style and scoped inventory
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Build Icon Prompt Template
|
||||
|
||||
Construct base prompt using style configuration: style type, stroke/fill details, canvas size, padding, color mode, background transparency.
|
||||
|
||||
### 2. Generate by Group
|
||||
|
||||
Process related icons together for consistency:
|
||||
1. Navigation set (menu, close, search, arrows, chevrons)
|
||||
2. Action set (edit, delete, save, share, copy, download, upload)
|
||||
3. Status set (success/check, warning, error/x, info)
|
||||
4. Feature set (page-specific icons)
|
||||
5. Social set (platform icons)
|
||||
|
||||
For each group: generate first icon, get approval, use as reference for rest of group.
|
||||
|
||||
### 3. Select Service
|
||||
|
||||
Present options: [G] Generate via MCP (best for custom icons), [E] Export prompts (for external generation), [L] Library match (search open-source icon libraries).
|
||||
|
||||
### 4. Optimize SVG Output
|
||||
|
||||
For each generated icon: clean SVG markup, ensure viewBox is correct, set stroke/fill to currentColor for monochrome, validate pixel alignment.
|
||||
|
||||
### 5. Track Progress
|
||||
|
||||
Display generation progress per group with completion counts.
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save generated icons, 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'
|
||||
- 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 all scoped icons are generated will you load {nextStepFile} to begin reviewing the complete set.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Icons generated in consistent groups
|
||||
- First icon of each group approved before batch generation
|
||||
- SVG optimization applied to all icons
|
||||
- Progress tracked and displayed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Batch-generating without first-icon approval
|
||||
- Not using approved icons as references
|
||||
- Skipping SVG optimization
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
124
_bmad/wds/workflows/6-asset-generation/steps-i/step-05-review.md
Normal file
124
_bmad/wds/workflows/6-asset-generation/steps-i/step-05-review.md
Normal file
@@ -0,0 +1,124 @@
|
||||
---
|
||||
name: 'step-05-review'
|
||||
description: 'Review the complete icon set for visual consistency, clarity, and completeness'
|
||||
workflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 5: Review and Iterate
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Review the complete icon set for visual consistency, metaphor clarity, and completeness — iterating on any icons that need adjustment and saving the final approved set with size variants.
|
||||
|
||||
## 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
|
||||
- ✅ Maintain a quality-focused, thorough tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Review as a complete set, not individual icons in isolation
|
||||
- 🚫 FORBIDDEN to skip consistency or metaphor clarity checks
|
||||
- 💬 Present icons in grid format at multiple sizes and backgrounds
|
||||
- 📋 Generate size variants only after approval
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Save approved set to `{output_folder}/E-Assets/icons/`
|
||||
- 📖 Check consistency across: stroke weight, visual weight, corner radius, detail level, padding
|
||||
- 🚫 FORBIDDEN to save without user approval
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All generated icons from Step 4, style configuration
|
||||
- Focus: Reviewing the complete set for quality and consistency
|
||||
- Limits: This is the final step — focus on quality assurance and delivery
|
||||
- Dependencies: Generated icons from Step 4
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Present Full Icon Set
|
||||
|
||||
Display all icons in a grid: organized by category, shown at multiple sizes (sm, md, lg), on dark and light backgrounds.
|
||||
|
||||
### 2. Consistency Check
|
||||
|
||||
Verify across the full set: uniform stroke weight, balanced visual weight, consistent corner radius, consistent detail level, uniform padding/live area, recognizable at smallest size.
|
||||
|
||||
### 3. Metaphor Clarity Check
|
||||
|
||||
For each icon: clearly communicates intended meaning, no ambiguity with similar icons, culturally appropriate metaphors.
|
||||
|
||||
### 4. User Review
|
||||
|
||||
Present options: [A] Approve all, [R] Regenerate specific icons, [W] Weight adjust globally, [S] Size test at minimum size, [C] Context preview in UI mockup.
|
||||
|
||||
### 5. Iterate on Flagged Icons
|
||||
|
||||
For icons marked for regeneration: capture feedback, adjust prompt, use closest approved match as reference, re-review in set context.
|
||||
|
||||
### 6. Generate Size Variants
|
||||
|
||||
For approved icons: SVG (scalable, primary format), PNG at 1x, 2x, 3x for each defined size.
|
||||
|
||||
### 7. Save Approved Set
|
||||
|
||||
Save to `{output_folder}/E-Assets/icons/`: `svg/` folder, `png/` folder organized by size, `icon-set-summary.md` catalog.
|
||||
|
||||
### 8. Update Design Log
|
||||
|
||||
Record: icons generated count, style used, categories covered, consistency pass/issues.
|
||||
|
||||
### 9. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF M: Save final set, update design log, return to Activity Menu in {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#9-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- User can chat or ask questions — always respond and then end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
This is the final step of the Icons workflow. When M is selected and the icon set is saved, return to the Activity Menu.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Full icon set presented for review
|
||||
- Consistency and metaphor clarity checks completed
|
||||
- User approved the final set
|
||||
- Size variants generated
|
||||
- Set saved to correct output location
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Saving icons without user approval
|
||||
- Skipping consistency or clarity checks
|
||||
- Not generating size variants
|
||||
- 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