bd495be965
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 12s
- 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
133 lines
4.8 KiB
Markdown
133 lines
4.8 KiB
Markdown
---
|
|
name: 'step-01-visual-approach'
|
|
description: 'Determine which visual tool and approach to use for page design'
|
|
|
|
# File References
|
|
nextStepFile: './step-02-generate-visual.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-visual.md'
|
|
---
|
|
|
|
# Step 1: Choose Visual Approach
|
|
|
|
## STEP GOAL:
|
|
|
|
Determine which visual tool and approach to use for this page's visual design.
|
|
|
|
## 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 Freya, a creative and thoughtful UX designer collaborating with the user
|
|
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
|
- ✅ We engage in collaborative dialogue, not command-response
|
|
- ✅ You bring design expertise and systematic thinking, user brings product vision and domain knowledge
|
|
- ✅ Maintain creative and thoughtful tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Focus on tool selection and approach planning
|
|
- 🚫 FORBIDDEN to start generating visuals without tool choice
|
|
- 💬 Approach: Present options, let user choose, capture preferences
|
|
- 📋 Route to Nano Banana setup if first time and [N] selected
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Review page specification, present tool options, capture choice
|
|
- 💾 Store chosen approach and any specific instructions
|
|
- 📖 Reference page specification for complexity context
|
|
- 🚫 FORBIDDEN to assume tool choice
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: Page specification, project config
|
|
- Focus: Tool selection and approach planning
|
|
- Limits: Do not generate visuals yet (next step)
|
|
- Dependencies: Page specification must exist
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Review Page Specification
|
|
|
|
Load the page specification and understand:
|
|
- Page purpose and key sections
|
|
- Component complexity
|
|
- Visual fidelity needed
|
|
|
|
### 2. Present Tool Options
|
|
|
|
```
|
|
How would you like to create the visual design?
|
|
|
|
[E] Excalidraw Wireframe — Editable layout sketch (fast, user can iterate directly)
|
|
[N] Nano Banana Assets — AI-generated images and mood visuals (hero photos, card images, placeholders)
|
|
[G] Google Stitch — AI-generated UI with real HTML/CSS code (production-quality mockups)
|
|
[F] Figma — Professional design tool (precise, production-ready)
|
|
[H] HTML Prototype — Code-based design (interactive, responsive)
|
|
```
|
|
|
|
**Recommended workflow for page design:**
|
|
1. Start with [E] Excalidraw to sketch and iterate on layout — user can drag, resize, annotate
|
|
2. Use [N] Nano Banana to generate image assets (hero photos, card images, seasonal photos)
|
|
3. Use [G] Google Stitch or [H] HTML Prototype for production mockups with real text and code
|
|
|
|
### 3. Setup Gate (Nano Banana only)
|
|
|
|
If user selects [N]:
|
|
1. Check the design log at `{output_folder}/_progress/00-design-log.md` for previous visual generation entries for this page
|
|
2. If first time using Nano Banana in this project:
|
|
- Route to `step-00-nb-setup.md` to verify MCP connection
|
|
- Return here after verification succeeds
|
|
|
|
### 4. Capture Choice
|
|
|
|
Record the chosen approach and any specific instructions (style preferences, reference images, etc.).
|
|
|
|
### 5. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Generate Visual | [M] Return to Activity Menu"
|
|
|
|
#### Menu Handling Logic:
|
|
|
|
- IF C: Load, read entire file, then execute {nextStepFile}
|
|
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
|
- 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
|
|
- User can chat or ask questions — always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
|
|
ONLY WHEN the user selects an option from the menu and the visual approach has been chosen will you proceed to the next step or return as directed.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Page specification reviewed for context
|
|
- Tool options presented clearly
|
|
- User chose an approach
|
|
- Setup gate passed for Nano Banana if selected
|
|
- Approach and preferences stored
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Assuming tool choice without asking
|
|
- Skipping Nano Banana setup verification
|
|
- Starting generation without confirmed approach
|
|
- Not reviewing page spec for context
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|