bd495be965
- 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
2.5 KiB
Execution Principles
Document Before Acting
Every decision, action, and problem must be documented in the dialog file BEFORE acting on it.
This ensures full traceability, clean handoff, and the dialog document is always the source of truth.
Sketch Fidelity
Implement code as close to the provided sketches as possible.
Sketches are intentional design decisions, not loose suggestions:
| Element | Approach |
|---|---|
| Text sizes | Match relative sizes (headings vs body vs labels) |
| Proportions | Preserve ratios between elements |
| Spacing | Maintain visual rhythm and whitespace |
| Layout | Follow the arrangement precisely |
| Component style | Match the visual pattern (pills, cards, buttons) |
When in doubt: ask the designer. If constraints make exact matching impossible, document the deviation and explain why.
Sub-Steps During Execution
While working on a step, add discovered tasks as sub-steps:
| # | Section | Status | Notes |
|---|---------|--------|-------|
| 14 | Book It Button | Done | Complete |
| 14a | Fix button alignment | Done | Added during 14 |
| 14b | Add loading state | Done | Added during 14 |
| 15 | Cancel Button | In Progress | |
Sub-steps use letter suffixes (14a, 14b) to maintain parent position.
Dynamic Planning After Step Completion
After completing each step, review and adjust the plan:
- Review remaining steps — still accurate?
- Shuffle if needed — reorder based on learnings
- Add new steps — if implementation revealed new requirements
- Remove steps — if no longer needed
- Update the dialog file
Numbering rules: Completed steps = fixed numbering. Future steps = dynamic numbering.
Plan-then-Execute Pattern
Separate planning from execution into distinct sessions.
Context windows are finite. Long sessions accumulate noise. The solution:
Planning Session:
- Explore codebase and requirements
- Discuss approach with designer
- Write plan to dialog file
- End with clear handoff
Execution Session:
- Start fresh (new conversation)
- Read product brief for context
- Read page specification for requirements
- Read dialog document for plan and progress
- Execute steps one by one
When to split: After complex exploration, when plan is complete, when session is getting long, before major implementation.
Handoff Always References Dialog
Any handoff — to a new session, agent, or human — MUST reference the dialog document. Never hand off verbally. Always point to the dialog.