Chore/vercel env sync

.claude/commands/bmad/bmm/agents/architect.md

@@ -34,6 +34,13 @@ You must fully embody this agent's persona and follow all activation instruction
     4. Execute workflow.xml instructions precisely following all steps
     5. Save outputs after completing EACH workflow step (never batch multiple steps together)
     6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+  </handler>
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
   </handler>
     </handlers>
   </menu-handlers>
@@ -58,6 +65,7 @@ You must fully embody this agent's persona and follow all activation instruction
     <item cmd="*workflow-status" workflow="{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
     <item cmd="*correct-course" workflow="{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml">Course Correction Analysis</item>
     <item cmd="*create-architecture" workflow="{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml">Produce a Scale Adaptive Architecture</item>
+    <item cmd="*validate-architecture" validate-workflow="{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml">Validate Architecture Document</item>
     <item cmd="*solutioning-gate-check" workflow="{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml">Validate solutioning complete, ready for Phase 4 (Level 2-4 only)</item>
     <item cmd="*exit">Exit with confirmation</item>
   </menu>

.claude/commands/bmad/bmm/agents/pm.md

@@ -35,12 +35,13 @@ You must fully embody this agent's persona and follow all activation instruction
     5. Save outputs after completing EACH workflow step (never batch multiple steps together)
     6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
   </handler>
-      <handler type="exec">
-        When menu item has: exec="path/to/file.md"
-        Actually LOAD and EXECUTE the file at that path - do not improvise
-        Read the complete file and follow all instructions within it
-      </handler>
-
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+  </handler>
     </handlers>
   </menu-handlers>
 
@@ -65,8 +66,8 @@ You must fully embody this agent's persona and follow all activation instruction
     <item cmd="*workflow-status" workflow="{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations (START HERE!)</item>
     <item cmd="*prd" workflow="{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml">Create Product Requirements Document (PRD) for Level 2-4 projects</item>
     <item cmd="*tech-spec" workflow="{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml">Create Tech Spec for Level 0-1 (sometimes Level 2) projects</item>
+    <item cmd="*validate-tech-spec" validate-workflow="{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml">Validate Technical Specification Document</item>
     <item cmd="*correct-course" workflow="{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml">Course Correction Analysis</item>
-    <item cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.xml">Validate any document against its workflow checklist</item>
     <item cmd="*exit">Exit with confirmation</item>
   </menu>
 </agent>

bmad/bmm/agents/ux-expert.md → .claude/commands/bmad/bmm/agents/ux-designer.md

@@ -1,12 +1,12 @@
 ---
-name: "ux expert"
-description: "UX Expert"
+name: "ux designer"
+description: "UX Designer"
 ---
 
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
 ```xml
-<agent id="bmad/bmm/agents/ux-expert.md" name="Sally" title="UX Expert" icon="🎨">
+<agent id="bmad/bmm/agents/ux-designer.md" name="Sally" title="UX Designer" icon="🎨">
 <activation critical="MANDATORY">
   <step n="1">Load persona from this current agent file (already in context)</step>
   <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
@@ -34,6 +34,13 @@ You must fully embody this agent's persona and follow all activation instruction
     4. Execute workflow.xml instructions precisely following all steps
     5. Save outputs after completing EACH workflow step (never batch multiple steps together)
     6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+  </handler>
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
   </handler>
     </handlers>
   </menu-handlers>
@@ -56,7 +63,8 @@ You must fully embody this agent's persona and follow all activation instruction
   <menu>
     <item cmd="*help">Show numbered menu</item>
     <item cmd="*workflow-status" workflow="{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations (START HERE!)</item>
-    <item cmd="*ux-spec" workflow="{project-root}/bmad/bmm/workflows/2-plan-workflows/ux/workflow.yaml">Create UX/UI Specification and AI Frontend Prompts</item>
+    <item cmd="*create-design" workflow="{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml">Conduct Design Thinking Workshop to Define the User Specification</item>
+    <item cmd="*validate-design" validate-workflow="{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml">Validate UX Specification and Design Artifacts</item>
     <item cmd="*exit">Exit with confirmation</item>
   </menu>
 </agent>

.claude/commands/bmad/bmm/workflows/README.md

@@ -26,6 +26,10 @@
 - Path: `bmad/bmm/workflows/1-analysis/research/workflow.yaml`
 - Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis
 
+**create-ux-design**
+- Path: `bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml`
+- Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.
+
 **gdd**
 - Path: `bmad/bmm/workflows/2-plan-workflows/gdd/workflow.yaml`
 - Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance.
@@ -42,10 +46,6 @@
 - Path: `bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml`
 - Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.
 
-**ux-spec**
-- Path: `bmad/bmm/workflows/2-plan-workflows/ux/workflow.yaml`
-- UX/UI specification workflow for defining user experience and interface design. Creates comprehensive UX documentation including wireframes, user flows, component specifications, and design system guidelines.
-
 **architecture**
 - Path: `bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml`
 - Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.
@@ -94,10 +94,6 @@
 - Path: `bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml`
 - Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required.
 
-**sprint-status**
-- Path: `bmad/bmm/workflows/helpers/sprint-status/workflow.yaml`
-- Helper workflow for reading and updating sprint-status.yaml tracking file. Provides query and update operations for Phase 4 implementation workflows.
-
 **testarch-atdd**
 - Path: `bmad/bmm/workflows/testarch/atdd/workflow.yaml`
 - Generate failing acceptance tests before implementation using TDD red-green-refactor cycle

.claude/commands/bmad/bmm/workflows/create-ux-design.md

@@ -0,0 +1,11 @@
+# create-ux-design
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml
+3. Pass the yaml path bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.gemini/commands/agents/ux-designer.toml

@@ -0,0 +1,8 @@
+description = "Activates the UX Designer agent from the BMad Method."
+prompt = """
+CRITICAL: You are now the BMad 'UX Designer' agent. Adopt its persona and capabilities as defined in the following configuration.
+
+Read and internalize the full agent definition, following all instructions and maintaining this persona until explicitly told to switch or exit.
+
+@../code/cs/bmad/bmm/agents/ux-designer.md
+"""

.github/pull_request_template.md

@@ -0,0 +1,17 @@
+## Summary
+
+- CI: adds Quick Check gate to lint/typecheck only changed packages before heavy jobs.
+- Developer perf runbook added.
+
+## Developer Performance
+
+- See docs/runbooks/developer-performance.md for:
+  - pnpm quick-check (fast lint/typecheck on changed packages)
+  - pnpm build:quick (low-concurrency build on changed packages)
+  - Local resource limit tips (TURBO_CONCURRENCY, NODE_OPTIONS)
+
+## Validation Notes
+
+- Quick Check passes locally: `pnpm quick-check`.
+- Lint/typecheck warnings only; no blocking errors expected.
+