| name | teach-impeccable |
| description | One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines. |
| user-invokable | true |
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
STOP and call the AskUserQuestion tool to clarify. 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: Select a Design Style
Present the style catalog from knowledge/design-styles/styles/:
| Style | Vibe |
|---|
| american-industrial | Raw materials, exposed structure, craft heritage |
| brutalist-raw | Stark, unpolished, confrontational |
| corporate-clean | Professional, trustworthy, systematic |
| dark-luxury | Premium, moody, high-contrast elegance |
| editorial-magazine | Print-inspired, typographic, narrative |
| ethereal-abstract | Soft, dreamlike, organic gradients |
| liminal-portal | Transitional, spatial, between-states |
| minimalist-swiss | Grid-perfect, reductive, International Typographic |
| retro-analog | Warm, textured, nostalgic analog feel |
Ask the user to:
- Pick one as the primary style
- Blend 2-3 for a hybrid direction
- Go custom if none fit (describe it and we'll codify it)
Record their choice. This becomes the style: field in .impeccable.md.
If unsure, recommend 2-3 styles based on the brand personality from Step 2.
Step 4: Write Design Context
Synthesize your findings and the user's answers into a ## Design Context section:
## Style
style: {chosen-style-name}
## 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]
The style: field enables automatic style pack loading. frontend-designer will load
knowledge/design-styles/styles/{style}.md and knowledge/design-styles/swipes/{style}/
on every invocation. ux-auditor will compare implementation against the style spec.
Write this section to .impeccable.md in the project root. If the file already exists, update the Design Context section in place.
Then STOP and call the AskUserQuestion tool to clarify. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well.
Confirm completion and summarize the key design principles that will now guide all future work.
