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
1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| workflow-discuss | Creative dialog for page design — discuss what each page needs, then visualize and specify. |
[C] Discuss — Creative Dialog for Page Design
Goal: Lead a focused creative dialog for each page — what does it need, can we simplify it, then visualize and specify.
When to use: The default design activity. Start here for any page that needs design thinking before building.
INITIALIZATION
Read design log at {output_folder}/_progress/00-design-log.md before starting.
Entry
Load scenario context (Trigger Map, scenario overview) from {output_folder}/C-UX-Scenarios/.
Steps
Execute steps in ./steps-c/:
| Step | File | Purpose |
|---|---|---|
| 01 | step-01-exploration.md | Open-ended design exploration |
Reference data:
./data/guides/DESIGN-LOOP-GUIDE.md— the 8-step design loop (discuss → wireframe → iterate → spec sync → implement → refine)./data/scenario-init/— scenario initialization guides./data/page-creation-flows/— page creation flow options
AFTER COMPLETION
Step 01's two-option transitions handle all navigation. The design log is updated at every transition within the step itself. There is no separate "after completion" — the step loops through pages until the user stops or all pages are designed.