Create Wireframe - Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/.faos/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow creates website or app wireframes in Excalidraw format.</critical>
<workflow>
<step n="0" goal="Contextual Analysis">
<action>Review user's request and extract: wireframe type, fidelity level, screen count, device type, save location</action>
<check if="ALL requirements clear"><action>Skip to Step 6</action></check>
</step>
<step n="1" goal="Assess Depth and Select Visual Pattern">
<action>Based on the user's request, determine the wireframe depth level per {{helpers}} Depth Assessment:</action>
<action>Present assessment:
- Simple/Conceptual (10-20 elements): Single screen, low fidelity, layout exploration
- Standard (20-40 elements): Few screens, medium fidelity, key interactions shown
- Comprehensive/Technical (40-80 elements): Multiple screens, high fidelity, full user flow
</action>
<action>State your assessment: "This looks like a [depth] wireframe because [reason]"</action>
<action>Select the best visual pattern from {{helpers}} Visual Pattern Library. For wireframes, common patterns are:
- pipeline: For multi-step user flows (onboarding, checkout)
- side-by-side: For responsive layouts showing desktop vs mobile
- tree: For site maps or navigation hierarchy
- cluster: For feature groupings within a single screen
</action>
<action>State: "I recommend the [pattern] pattern because it argues that [specific argument]"</action>
<action>Ask: "Does this depth and pattern match your intent? (yes/adjust)"</action>
<action>WAIT for confirmation</action>
<check if="user says adjust">
<action>Revise depth and/or pattern based on feedback</action>
<action>Confirm revised choices</action>
</check>
</step>
<step n="2" goal="Identify Wireframe Type" elicit="true">
<action>Ask: "What type of wireframe do you need?"</action>
<action>Present options:
1. Website (Desktop)
2. Mobile App (iOS/Android)
3. Web App (Responsive)
4. Tablet App
5. Multi-platform
</action>
<action>WAIT for selection</action>
</step>
<step n="3" goal="Gather Requirements" elicit="true">
<action>Ask fidelity level (Low/Medium/High)</action>
<action>Ask screen count (Single/Few 2-3/Multiple 4-6/Many 7+)</action>
<action>Ask device dimensions or use standard</action>
<action>Ask save location</action>
</step>
<step n="4" goal="Check Theme" elicit="true">
<action>Check for existing theme.json, ask to use if exists</action>
</step>
<step n="5" goal="Create Theme" elicit="true">
<action>Ask: "Choose a wireframe style:"</action>
<action>Present numbered options:
1. Classic Wireframe
- Background: #ffffff (white)
- Container: #f5f5f5 (light gray)
- Border: #9e9e9e (gray)
- Text: #424242 (dark gray)
2. High Contrast
- Background: #ffffff (white)
- Container: #eeeeee (light gray)
- Border: #212121 (black)
- Text: #000000 (black)
3. Blueprint Style
- Background: #1a237e (dark blue)
- Container: #3949ab (blue)
- Border: #7986cb (light blue)
- Text: #ffffff (white)
4. Custom - Define your own colors
</action>
<action>WAIT for selection</action>
<action>Create theme.json based on selection, including semantic color mapping per {{helpers}}</action>
<action>Confirm with user</action>
</step>
<step n="6" goal="Plan Wireframe Structure">
<action>List all screens and their purposes</action>
<action>Map navigation flow between screens</action>
<action>Identify key UI elements for each screen</action>
<action>Apply the selected visual pattern to the layout plan</action>
<action>Show planned structure, confirm with user</action>
</step>
<step n="7" goal="Load Resources">
<action>Load {{templates}} and extract `wireframe` section</action>
<action>Load visual_patterns from {{templates}} for the selected pattern</action>
<action>Load {{library}}</action>
<action>Load theme.json</action>
<action>Load {{helpers}}</action>
</step>
<step n="8" goal="Build Wireframe Elements">
<critical>Apply the design philosophy from {{helpers}}: This wireframe must ARGUE a point about the user experience, not just show rectangles. Follow the selected visual pattern for layout.</critical>
<critical>Use descriptive string IDs per {{helpers}} ID conventions (e.g., "hero_section_rect" not "rect_1")</critical>
<critical>Prefer free-floating text for screen titles, annotations, and interaction notes. Target less than 30% containerized text per {{helpers}} Text Strategy.</critical>
<substep>For Each Screen:
- Create container/frame with descriptive ID
- Add header section
- Add content areas
- Add navigation elements
- Add interactive elements (buttons, inputs)
- Add labels and annotations as free-floating text
</substep>
<substep>Build Order:
1. Screen containers
2. Layout sections (header, content, footer)
3. Navigation elements
4. Content blocks
5. Interactive elements
6. Labels and annotations (free-floating)
7. Flow indicators (if multi-screen)
</substep>
<substep>Fidelity Guidelines:
- Low: Basic shapes, minimal detail, placeholder text
- Medium: More defined elements, some styling, representative content
- High: Detailed elements, realistic sizing, actual content examples
</substep>
<substep>Apply semantic colors per {{helpers}}:
- Primary for main interactive elements (CTA buttons, key inputs)
- Secondary for supporting UI (headers, footers, navigation)
- Accent for highlighted or featured content areas
- Neutral for containers and boundaries
</substep>
<check if="planned element count exceeds 30">
<action>Switch to section-by-section generation per {{helpers}} Section-by-Section Generation Protocol</action>
<action>Identify logical sections (e.g., per screen, per region, or per breakpoint)</action>
<action>Generate each section separately, using namespaced seeds</action>
<action>After all sections: merge, validate cross-section arrows, verify boundElements</action>
</check>
<check if="depth is Comprehensive/Technical AND fidelity is High">
<action>Add evidence artifacts per {{helpers}} Evidence Artifacts guide</action>
<action>Embed real content examples or interaction details next to relevant components (max 3)</action>
</check>
</step>
<step n="9" goal="Optimize and Save">
<action>Strip unused elements and elements with isDeleted: true</action>
<action>Save to {{default_output_file}}</action>
</step>
<step n="10" goal="Validate JSON Syntax">
<critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
<action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('Valid JSON')"</action>
<check if="validation fails (exit code 1)">
<action>Read the error message carefully - it shows the syntax error and position</action>
<action>Open the file and navigate to the error location</action>
<action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
<action>Save the file</action>
<action>Re-run validation with the same command</action>
<action>Repeat until validation passes</action>
</check>
<action>Once validation passes, confirm with user</action>
</step>
<step n="11" goal="Visual Preview (Optional)" optional="true">
<action>Load {{render_validate}}</action>
<action>Run: python3 {{render_script}} {{default_output_file}}</action>
<check if="exit code is 2 (Playwright not installed)">
<action>Skip: "Playwright not available — skipping PNG preview. Wireframe is still valid."</action>
</check>
<check if="exit code is 0">
<action>View the generated PNG file</action>
<action>Audit against design vision: Does the wireframe ARGUE its point about the UX?</action>
<action>Check: overlapping text, misaligned elements, spacing issues, color rendering</action>
<check if="issues found">
<action>Fix the JSON</action>
<action>Re-render (max 3 cycles)</action>
</check>
<action>Ask: "Keep the PNG preview file? (yes/no)"</action>
</check>
</step>
<step n="12" goal="Validate Content">
<invoke-task>Validate against {{validation}}</invoke-task>
</step>
</workflow>
Quality Checklist
Create Wireframe - Validation Checklist
Design Quality
Generation Quality
Layout Structure
UI Elements
Fidelity
Annotations
Technical Quality
1---2name: excalidraw-wireframe3description: "Create website or app wireframes in Excalidraw format with proper layout, navigation, and component structure."4tags: [excalidraw, diagrams, wireframe, visualization]5metadata:6 source: https://skillmd.com/skills/frank-luongt/excalidraw-wireframe7---89# Create Wireframe - Workflow Instructions1011```xml12<critical>The workflow execution engine is governed by: {project_root}/.faos/core/tasks/workflow.xml</critical>13<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>14<critical>This workflow creates website or app wireframes in Excalidraw format.</critical>1516<workflow>1718 <step n="0" goal="Contextual Analysis">19 <action>Review user's request and extract: wireframe type, fidelity level, screen count, device type, save location</action>20 <check if="ALL requirements clear"><action>Skip to Step 6</action></check>21 </step>2223 <step n="1" goal="Assess Depth and Select Visual Pattern">24 <action>Based on the user's request, determine the wireframe depth level per {{helpers}} Depth Assessment:</action>25 <action>Present assessment:26 - Simple/Conceptual (10-20 elements): Single screen, low fidelity, layout exploration27 - Standard (20-40 elements): Few screens, medium fidelity, key interactions shown28 - Comprehensive/Technical (40-80 elements): Multiple screens, high fidelity, full user flow29 </action>30 <action>State your assessment: "This looks like a [depth] wireframe because [reason]"</action>31 <action>Select the best visual pattern from {{helpers}} Visual Pattern Library. For wireframes, common patterns are:32 - pipeline: For multi-step user flows (onboarding, checkout)33 - side-by-side: For responsive layouts showing desktop vs mobile34 - tree: For site maps or navigation hierarchy35 - cluster: For feature groupings within a single screen36 </action>37 <action>State: "I recommend the [pattern] pattern because it argues that [specific argument]"</action>38 <action>Ask: "Does this depth and pattern match your intent? (yes/adjust)"</action>39 <action>WAIT for confirmation</action>40 <check if="user says adjust">41 <action>Revise depth and/or pattern based on feedback</action>42 <action>Confirm revised choices</action>43 </check>44 </step>4546 <step n="2" goal="Identify Wireframe Type" elicit="true">47 <action>Ask: "What type of wireframe do you need?"</action>48 <action>Present options:49 1. Website (Desktop)50 2. Mobile App (iOS/Android)51 3. Web App (Responsive)52 4. Tablet App53 5. Multi-platform54 </action>55 <action>WAIT for selection</action>56 </step>5758 <step n="3" goal="Gather Requirements" elicit="true">59 <action>Ask fidelity level (Low/Medium/High)</action>60 <action>Ask screen count (Single/Few 2-3/Multiple 4-6/Many 7+)</action>61 <action>Ask device dimensions or use standard</action>62 <action>Ask save location</action>63 </step>6465 <step n="4" goal="Check Theme" elicit="true">66 <action>Check for existing theme.json, ask to use if exists</action>67 </step>6869 <step n="5" goal="Create Theme" elicit="true">70 <action>Ask: "Choose a wireframe style:"</action>71 <action>Present numbered options:72 1. Classic Wireframe73 - Background: #ffffff (white)74 - Container: #f5f5f5 (light gray)75 - Border: #9e9e9e (gray)76 - Text: #424242 (dark gray)7778 2. High Contrast79 - Background: #ffffff (white)80 - Container: #eeeeee (light gray)81 - Border: #212121 (black)82 - Text: #000000 (black)8384 3. Blueprint Style85 - Background: #1a237e (dark blue)86 - Container: #3949ab (blue)87 - Border: #7986cb (light blue)88 - Text: #ffffff (white)8990 4. Custom - Define your own colors91 </action>92 <action>WAIT for selection</action>93 <action>Create theme.json based on selection, including semantic color mapping per {{helpers}}</action>94 <action>Confirm with user</action>95 </step>9697 <step n="6" goal="Plan Wireframe Structure">98 <action>List all screens and their purposes</action>99 <action>Map navigation flow between screens</action>100 <action>Identify key UI elements for each screen</action>101 <action>Apply the selected visual pattern to the layout plan</action>102 <action>Show planned structure, confirm with user</action>103 </step>104105 <step n="7" goal="Load Resources">106 <action>Load {{templates}} and extract `wireframe` section</action>107 <action>Load visual_patterns from {{templates}} for the selected pattern</action>108 <action>Load {{library}}</action>109 <action>Load theme.json</action>110 <action>Load {{helpers}}</action>111 </step>112113 <step n="8" goal="Build Wireframe Elements">114 <critical>Apply the design philosophy from {{helpers}}: This wireframe must ARGUE a point about the user experience, not just show rectangles. Follow the selected visual pattern for layout.</critical>115 <critical>Use descriptive string IDs per {{helpers}} ID conventions (e.g., "hero_section_rect" not "rect_1")</critical>116 <critical>Prefer free-floating text for screen titles, annotations, and interaction notes. Target less than 30% containerized text per {{helpers}} Text Strategy.</critical>117118 <substep>For Each Screen:119 - Create container/frame with descriptive ID120 - Add header section121 - Add content areas122 - Add navigation elements123 - Add interactive elements (buttons, inputs)124 - Add labels and annotations as free-floating text125 </substep>126127 <substep>Build Order:128 1. Screen containers129 2. Layout sections (header, content, footer)130 3. Navigation elements131 4. Content blocks132 5. Interactive elements133 6. Labels and annotations (free-floating)134 7. Flow indicators (if multi-screen)135 </substep>136137 <substep>Fidelity Guidelines:138 - Low: Basic shapes, minimal detail, placeholder text139 - Medium: More defined elements, some styling, representative content140 - High: Detailed elements, realistic sizing, actual content examples141 </substep>142143 <substep>Apply semantic colors per {{helpers}}:144 - Primary for main interactive elements (CTA buttons, key inputs)145 - Secondary for supporting UI (headers, footers, navigation)146 - Accent for highlighted or featured content areas147 - Neutral for containers and boundaries148 </substep>149150 <check if="planned element count exceeds 30">151 <action>Switch to section-by-section generation per {{helpers}} Section-by-Section Generation Protocol</action>152 <action>Identify logical sections (e.g., per screen, per region, or per breakpoint)</action>153 <action>Generate each section separately, using namespaced seeds</action>154 <action>After all sections: merge, validate cross-section arrows, verify boundElements</action>155 </check>156157 <check if="depth is Comprehensive/Technical AND fidelity is High">158 <action>Add evidence artifacts per {{helpers}} Evidence Artifacts guide</action>159 <action>Embed real content examples or interaction details next to relevant components (max 3)</action>160 </check>161 </step>162163 <step n="9" goal="Optimize and Save">164 <action>Strip unused elements and elements with isDeleted: true</action>165 <action>Save to {{default_output_file}}</action>166 </step>167168 <step n="10" goal="Validate JSON Syntax">169 <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>170 <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('Valid JSON')"</action>171 <check if="validation fails (exit code 1)">172 <action>Read the error message carefully - it shows the syntax error and position</action>173 <action>Open the file and navigate to the error location</action>174 <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>175 <action>Save the file</action>176 <action>Re-run validation with the same command</action>177 <action>Repeat until validation passes</action>178 </check>179 <action>Once validation passes, confirm with user</action>180 </step>181182 <step n="11" goal="Visual Preview (Optional)" optional="true">183 <action>Load {{render_validate}}</action>184 <action>Run: python3 {{render_script}} {{default_output_file}}</action>185 <check if="exit code is 2 (Playwright not installed)">186 <action>Skip: "Playwright not available — skipping PNG preview. Wireframe is still valid."</action>187 </check>188 <check if="exit code is 0">189 <action>View the generated PNG file</action>190 <action>Audit against design vision: Does the wireframe ARGUE its point about the UX?</action>191 <action>Check: overlapping text, misaligned elements, spacing issues, color rendering</action>192 <check if="issues found">193 <action>Fix the JSON</action>194 <action>Re-render (max 3 cycles)</action>195 </check>196 <action>Ask: "Keep the PNG preview file? (yes/no)"</action>197 </check>198 </step>199200 <step n="12" goal="Validate Content">201 <invoke-task>Validate against {{validation}}</invoke-task>202 </step>203204</workflow>205```206207208## Quality Checklist209210# Create Wireframe - Validation Checklist211212## Design Quality213214- [ ] Wireframe makes a clear visual argument about the user experience215- [ ] Isomorphism Test: Layout structure communicates hierarchy without labels216- [ ] Education Test: Unfamiliar viewer understands the interface in 30 seconds217- [ ] Visual pattern applied consistently (pipeline/side-by-side/tree/cluster)218- [ ] Depth level matches user intent (Simple/Standard/Comprehensive)219- [ ] Free-floating text used for screen titles and annotations (target <30% containerized)220- [ ] Semantic colors encode element roles (primary for CTA, secondary for navigation)221- [ ] All IDs are descriptive strings (e.g., "hero_section_rect" not "rect_1")222223## Generation Quality224225- [ ] If >30 elements: section-by-section generation used with namespaced seeds226- [ ] Descriptive string IDs follow `{component}_{role}_{type}` pattern227- [ ] Cross-section arrows have valid startBinding and endBinding228- [ ] Evidence artifacts present for High fidelity Comprehensive depth only (max 3)229- [ ] Evidence artifacts use dark rectangle styling with monospace text230231## Layout Structure232233- [ ] Screen dimensions appropriate for device type234- [ ] Grid alignment (20px) maintained235- [ ] Consistent spacing between UI elements236- [ ] Proper hierarchy (header, content, footer)237238## UI Elements239240- [ ] All interactive elements clearly marked241- [ ] Buttons, inputs, and controls properly sized242- [ ] Text labels readable and appropriately sized243- [ ] Navigation elements clearly indicated244245## Fidelity246247- [ ] Matches requested fidelity level (low/medium/high)248- [ ] Appropriate level of detail249- [ ] Placeholder content used where needed250- [ ] No unnecessary decoration for low-fidelity251252## Annotations253254- [ ] Key interactions annotated255- [ ] Flow indicators present if multi-screen256- [ ] Important notes included257- [ ] Element purposes clear258259## Technical Quality260261- [ ] All elements properly grouped262- [ ] Text elements have containerId263- [ ] Snapped to grid264- [ ] No elements with `isDeleted: true`265- [ ] JSON is valid266- [ ] File saved to correct location267