Gather design context for this project, then persist it for all future sessions.
Step 1: Explore the Codebase
Before asking questions, thoroughly scan the project to discover what you can:
- README and docs: Project purpose, target audience, any stated goals
- Package.json / config files: Tech stack, dependencies, existing design libraries
- Existing components: Current design patterns, spacing, typography in use
- Brand assets: Logos, favicons, color values already defined
- Design tokens / CSS variables: Existing color palettes, font stacks, spacing scales
- Any style guides or brand documentation
Note what you've learned and what remains unclear.
Step 2: Ask UX-Focused Questions
{{ask_instruction}} Focus only on what you couldn't infer from the codebase:
Users & Purpose
- Who uses this? What's their context when using it?
- What job are they trying to get done?
- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)
Brand & Personality
- How would you describe the brand personality in 3 words?
- Any reference sites or apps that capture the right feel? What specifically about them?
- What should this explicitly NOT look like? Any anti-references?
Aesthetic Preferences
- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
- Light mode, dark mode, or both?
- Any colors that must be used or avoided?
Accessibility & Inclusion
- Specific accessibility requirements? (WCAG level, known user needs)
- Considerations for reduced motion, color blindness, or other accommodations?
Skip questions where the answer is already clear from the codebase exploration.
Step 3: Write Design Context
Synthesize your findings and the user's answers into a ## Design Context section:
## Design Context
### Users
[Who they are, their context, the job to be done]
### Brand Personality
[Voice, tone, 3-word personality, emotional goals]
### Aesthetic Direction
[Visual tone, references, anti-references, theme]
### Design Principles
[3-5 principles derived from the conversation that should guide all design decisions]
Write this section to {{config_file}} in the project root. If the file exists, append or update the Design Context section.
Confirm completion and summarize the key design principles that will now guide all future work.
1---2name: teach-impeccable3description: Gather design context for this project, then persist it for all future sessions.4---5Gather design context for this project, then persist it for all future sessions.67## Step 1: Explore the Codebase89Before asking questions, thoroughly scan the project to discover what you can:1011- **README and docs**: Project purpose, target audience, any stated goals12- **Package.json / config files**: Tech stack, dependencies, existing design libraries13- **Existing components**: Current design patterns, spacing, typography in use14- **Brand assets**: Logos, favicons, color values already defined15- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales16- **Any style guides or brand documentation**1718Note what you've learned and what remains unclear.1920## Step 2: Ask UX-Focused Questions2122{{ask_instruction}} Focus only on what you couldn't infer from the codebase:2324### Users & Purpose25- Who uses this? What's their context when using it?26- What job are they trying to get done?27- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)2829### Brand & Personality30- How would you describe the brand personality in 3 words?31- Any reference sites or apps that capture the right feel? What specifically about them?32- What should this explicitly NOT look like? Any anti-references?3334### Aesthetic Preferences35- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)36- Light mode, dark mode, or both?37- Any colors that must be used or avoided?3839### Accessibility & Inclusion40- Specific accessibility requirements? (WCAG level, known user needs)41- Considerations for reduced motion, color blindness, or other accommodations?4243Skip questions where the answer is already clear from the codebase exploration.4445## Step 3: Write Design Context4647Synthesize your findings and the user's answers into a `## Design Context` section:4849```markdown50## Design Context5152### Users53[Who they are, their context, the job to be done]5455### Brand Personality56[Voice, tone, 3-word personality, emotional goals]5758### Aesthetic Direction59[Visual tone, references, anti-references, theme]6061### Design Principles62[3-5 principles derived from the conversation that should guide all design decisions]63```6465Write this section to {{config_file}} in the project root. If the file exists, append or update the Design Context section.6667Confirm completion and summarize the key design principles that will now guide all future work.
ComeOnOliver