bi-agents/_bmad/wds/workflows/4-ux-design/steps-p/step-01-page-basics.md

name, description, nextStepFile, workflowFile, activityWorkflowFile

name	description	nextStepFile	workflowFile	activityWorkflowFile
step-01-page-basics	Capture fundamental page information including title, route, goals, and SEO data	./step-02-layout-sections.md	../workflow.md	../workflow-specify.md

Step 1: Page Basics

STEP GOAL:

Capture fundamental page information including title, URL/route, user goal, entry/exit points, and SEO data for public pages.

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 capturing page basics — title, route, goals, entry/exit points, SEO
• 🚫 FORBIDDEN to define layout sections or components yet
• 💬 Approach: Structured information gathering with examples
• 📋 Reference project brief SEO strategy for keyword data

EXECUTION PROTOCOLS:

• 🎯 Gather all page basics through structured questions
• 💾 Store page_basics (title, route, goal, entry/exit points, SEO data)
• 📖 Reference project brief for SEO keywords
• 🚫 FORBIDDEN to skip SEO fields for public pages

CONTEXT BOUNDARIES:

• Available context: Scenario data, page definition from Suggest activity
• Focus: Fundamental page information only
• Limits: Do not define layout or components (next steps)
• Dependencies: Page must exist in scenario structure

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

1. Gather Page Basics

Let's start with the page basics.

Page basics:

• Page name/title:
• URL/route (if applicable):
• Main user goal (in one sentence):
• Where users come from (entry points):
• Where users go next (exit points):

SEO (for public pages): Check the project brief's SEO Strategy for this page's target keywords.

• Primary keyword:
• Secondary keywords:
• URL slug (from keyword map):

Store page_basics:

• page_title
• url_route
• user_goal
• entry_points
• exit_points
• primary_keyword (if public page)
• secondary_keywords (if public page)
• url_slug (if public page)

Page basics captured!

Next: We'll define the layout sections.

2. Present MENU OPTIONS

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

• 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 all page basics have been captured will you proceed to the next step or return as directed.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Page title, route, and user goal captured
• Entry and exit points defined
• SEO data captured for public pages
• All page_basics stored

❌ SYSTEM FAILURE:

• Generating page basics without user input
• Skipping SEO fields for public pages
• Proceeding to layout without capturing basics
• Not storing page_basics

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