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
140 lines
5.0 KiB
Markdown
140 lines
5.0 KiB
Markdown
---
|
|
name: 'step-09-design-system-consistency'
|
|
description: 'Verify components are used correctly and consistently across all page specifications'
|
|
|
|
# File References
|
|
nextStepFile: './step-10-final-validation.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-validate.md'
|
|
---
|
|
|
|
# Step 9: Validate Design System Consistency
|
|
|
|
## STEP GOAL:
|
|
|
|
Verify components are used correctly and consistently across all page specifications.
|
|
|
|
## 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 cross-page component consistency and design system alignment
|
|
- 🚫 FORBIDDEN to skip shared component validation (header, footer, nav)
|
|
- 💬 Approach: Audit component usage across all pages, check naming and state consistency
|
|
- 📋 Design system is the single source of truth for component definitions
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Audit component usage, naming, and consistency across all page specifications
|
|
- 💾 Update specifications if consistency fixes are approved by user
|
|
- 📖 Reference design system registry for component definitions
|
|
- 🚫 FORBIDDEN to skip design system completeness check
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: All page specifications, design system components
|
|
- Focus: Cross-page component consistency only
|
|
- Limits: Do not validate individual page structure (covered by earlier steps)
|
|
- Dependencies: Design system must exist with component definitions
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Component Usage
|
|
|
|
- [ ] All components reference design system definitions
|
|
- [ ] No inline component definitions that should be in design system
|
|
- [ ] Component variants used appropriately (not mixing similar components)
|
|
|
|
### 2. Naming Consistency
|
|
|
|
- [ ] Component names match design system registry
|
|
- [ ] No duplicate component names with different definitions
|
|
- [ ] Naming follows established conventions
|
|
|
|
### 3. Cross-Page Consistency
|
|
|
|
- [ ] Shared components (header, footer, nav) identical across pages
|
|
- [ ] Similar patterns use the same components (not ad-hoc alternatives)
|
|
- [ ] State definitions consistent for same components across pages
|
|
|
|
### 4. Design System Completeness
|
|
|
|
- [ ] All referenced components exist in design system
|
|
- [ ] No orphaned components (defined but never used)
|
|
- [ ] Component documentation sufficient for implementation
|
|
|
|
### 5. Generate Design System Consistency Report
|
|
|
|
```
|
|
## Design System Consistency Report
|
|
|
|
**Components in system:** [N]
|
|
**Components referenced:** [N]
|
|
**Consistency issues:** [N]
|
|
**Missing from system:** [N]
|
|
|
|
[List any inconsistencies or gaps]
|
|
```
|
|
|
|
### 6. Resolve Issues
|
|
|
|
If issues found, present to user and ask if they want you to fix the consistency issues.
|
|
|
|
### 7. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Final Validation | [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](#7-present-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 the design system consistency validation is complete will you proceed to the next step or return as directed.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Component usage audited across all page specifications
|
|
- Naming consistency verified against design system registry
|
|
- Shared components validated for cross-page consistency
|
|
- Design system completeness checked (no orphaned or missing components)
|
|
- Design System Consistency Report generated
|
|
- Issues resolved with user approval
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Not checking all page specifications
|
|
- Skipping shared component validation
|
|
- Not verifying naming against design system registry
|
|
- Not checking design system completeness
|
|
- Auto-fixing consistency issues without user approval
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|