2.3 KiB
Step 2: Set Up Scenario Structure
Progress: Step 2 of 5 - Next: Page Design
YOUR TASK
Route to the appropriate initialization workshop based on project structure.
CRITICAL: READ PROJECT STRUCTURE
Read `wds-workflow-status.yaml` and extract: - `project_structure.scenarios` (single | multiple) - `project_structure.pages` (single | multiple)Determine project structure type:
- pages == "single" → SEPARATE_PAGES (individual pages/variants)
- scenarios == "single" AND pages == "multiple" → SINGLE_FLOW (one scenario, multiple pages)
- scenarios == "multiple" → MULTIPLE_FLOWS (multiple scenarios)
Store structure_type in memory for this session.
ROUTING LOGIC
Separate Pages (No Scenarios)
**Project Structure:** Separate pages or variantsYou're creating individual pages (like landing pages, dashboards, or page variants). Let's define the first page.
Skip scenario-init (no scenarios needed)
Load and execute: step-02-substeps/page-init/step-01-page-context.md
Single User Flow (One Scenario)
**Project Structure:** Single user flow (multiple pages)You're creating one continuous user journey across multiple pages. Let's first define the scenario, then the first page.
Load and execute: step-02-substeps/scenario-init/step-01-core-feature.md
(After scenario-init completes, it will automatically route to page-init)
Multiple User Flows (Multiple Scenarios)
**Project Structure:** Multiple user flows (scenarios)You're creating multiple distinct user journeys, each with their own pages. Let's define the first scenario, then its first page.
Load and execute: step-02-substeps/scenario-init/step-01-core-feature.md
(After scenario-init completes, it will automatically route to page-init)
CRITICAL RULES
- 🛑 NEVER skip the routing logic
- 📖 ALWAYS read the full substep file before executing
- 🚫 NEVER execute multiple flows
- ⚠️ ONLY ONE FLOW executes based on project structure type