bi-agents/_bmad/wds/workflows/4-ux-design/steps-s/step-09-page-name.md

name, description, nextStepFile, workflowFile, activityWorkflowFile

name	description	nextStepFile	workflowFile	activityWorkflowFile
step-09-page-name	Capture the page name and generate a URL-friendly slug	./step-10-page-purpose.md	../workflow.md	../workflow-suggest.md

Step 9: Page Name

STEP GOAL:

Capture the page name from the user and generate a URL-friendly slug for folder and file naming.

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 getting a clear, descriptive page name
• 🚫 FORBIDDEN to generate the page name without user input
• 💬 Approach: Provide examples, let user choose
• 📋 Generate slug automatically from the name

EXECUTION PROTOCOLS:

• 🎯 Ask for page name with examples
• 💾 Store page_name and generate page_slug
• 📖 Reference scenario context for naming consistency
• 🚫 FORBIDDEN to proceed without a confirmed name

CONTEXT BOUNDARIES:

• Available context: Scenario data, pages_list
• Focus: Naming this specific page
• Limits: Just the name and slug — purpose is the next step
• Dependencies: Page context routing complete

Sequence of Instructions (Do not deviate, skip, or optimize)

1. Get Page Name

What's the name of this page?

Examples:

• Start Page / Home
• About
• Contact
• Dashboard
• User Profile
• Checkout
• Confirmation

Page name:

Store page_name Generate page_slug from page_name (lowercase, hyphenated) page_name, page_slug

2. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Page Purpose | [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

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 page_name and page_slug have been captured will you proceed to the next step or return as directed.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Page name provided by user
• page_slug generated automatically (lowercase, hyphenated)
• Both values stored for subsequent steps

❌ SYSTEM FAILURE:

• Generating the page name without user input
• Not generating the page_slug
• Proceeding without storing both values

Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.