Agent skill · design visual · aiskillstore
teach-impeccable
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.
Why this skill is useful
Establishes a structured design context and guidelines that the AI can use for future design decisions, which it wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 {{askinstruction}} 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: Write this section to .impeccable.md in the project root. If the file already exists, update the Design Context section in place. Then {{askinstruction}} whether they'd also like the Design Context appended to {{configfile}}. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/teach-impeccable