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
151 lines
5.2 KiB
Markdown
151 lines
5.2 KiB
Markdown
---
|
|
name: 'step-08-page-context'
|
|
description: 'Route user to appropriate page creation workflow based on their context'
|
|
|
|
# File References
|
|
nextStepFile: './step-09-page-name.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-suggest.md'
|
|
---
|
|
|
|
# Step 8: Page Init - Entry Point
|
|
|
|
## STEP GOAL:
|
|
|
|
Route user to appropriate page creation workflow based on what they have — a sketch, a concept description, or a question about creating a page.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
|
|
- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
|
|
- 📖 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 understanding what the user has and routing appropriately
|
|
- 🚫 FORBIDDEN to assume the user's approach without asking
|
|
- 💬 Approach: Natural routing based on conversation context
|
|
- 📋 The page is the conceptual entity; visualization is how we represent it
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Understand from conversation context what the user has available
|
|
- 💾 Route to the appropriate page creation workflow
|
|
- 📖 Reference page creation flows in data/ for detailed workflows
|
|
- 🚫 FORBIDDEN to skip the routing decision
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: Scenario data, conversation history
|
|
- Focus: Routing to the correct page creation approach
|
|
- Limits: Do not start page creation here — route to the correct flow
|
|
- Dependencies: Scenario structure must exist
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Route to Page Creation
|
|
|
|
**Purpose:** Route user to appropriate page creation workflow
|
|
|
|
<action>
|
|
**Understand from conversation context:**
|
|
|
|
Check what user has said:
|
|
- Did they mention having a sketch/wireframe/visualization?
|
|
- Did they upload an image file?
|
|
- Are they describing a page concept without visual?
|
|
- Are they asking about creating/defining a page?
|
|
|
|
**Route based on understanding:**
|
|
|
|
IF user has sketch/visualization ready:
|
|
-> Load and execute: `../data/page-creation-flows/workshop-page-process.md`
|
|
- Intelligent context detection
|
|
- New page: Full analysis
|
|
- Updated page: Change detection & incremental update
|
|
|
|
IF user is describing concept without visualization:
|
|
-> Load and execute: `../data/page-creation-flows/workshop-page-creation.md`
|
|
- Define page purpose and concept
|
|
- Choose visualization method naturally
|
|
- Create conceptual specification
|
|
|
|
IF unclear what user wants:
|
|
-> Ask natural clarifying question based on context
|
|
Example: "Do you have a sketch or wireframe I should look at, or should we define the page concept together?"
|
|
</action>
|
|
|
|
### 2. Philosophy
|
|
|
|
**The page is the conceptual entity.**
|
|
|
|
It has:
|
|
- A purpose (what it accomplishes)
|
|
- A user (who it serves)
|
|
- Sections (what areas exist)
|
|
- Objects (what interactions happen)
|
|
- A place in the flow (navigation)
|
|
|
|
**Visualization is how we represent the page.**
|
|
|
|
Methods include:
|
|
- Sketch (hand-drawn or digital)
|
|
- Wireframe (tool-based)
|
|
- ASCII layout (text-based)
|
|
- Verbal description (discussion)
|
|
- Reference (based on existing page)
|
|
|
|
**Page first. Visualization second.**
|
|
|
|
### 3. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Page Name | [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](#3-present-menu-options)
|
|
|
|
#### EXECUTION RULES:
|
|
|
|
- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
|
|
- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
|
|
- 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 routing decision has been made will you proceed to the next step or return as directed.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- User's available materials understood from context
|
|
- Appropriate page creation workflow selected
|
|
- Routing executed based on actual user situation
|
|
- Page-first philosophy maintained
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Assuming user approach without understanding context
|
|
- Skipping the routing decision
|
|
- Starting page creation without understanding what user has
|
|
- Forcing a specific visualization method
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|