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.
Best use case
teach-impeccable is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using teach-impeccable should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/teach-impeccable/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How teach-impeccable Compares
| Feature / Agent | teach-impeccable | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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: Write Design Context Synthesize your findings and the user's answers into a `## Design Context` section: ```markdown ## 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 `.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.
Related Skills
impeccable
Run impeccable design quality commands on frontend code — audit, critique, polish, animate, normalize, and more. Built on top of the frontend-design skill with 20 steering commands and 10 domain-specific reference files. Use when doing a design QA pass, reviewing UI quality, or refining a frontend component before shipping.
writer
Write content in Eric's voice — articles, blog posts, tweets, social media posts, marketing copy, newsletter drafts. Loads WRITING-STYLE.md and enforces kill phrases.
positioning-angles
Use when defining product positioning, choosing strategic angles, crafting value propositions, competitive positioning, product messaging, differentiation strategy, or go-to-market angles. Also use for 'how should I position my app', 'what angle should I use', 'painkiller vs vitamin', or 'market positioning'.
outline-generator
Use when generating outlines, article structures, content outlines, blog outlines, planning article sections, structuring posts, breaking down topics into sections, or organizing ideas for long-form content. Also use for 'outline this', 'structure this article', or 'plan the sections'.
last30days-open
Use only when the user explicitly asks for the open variant of last30days, including watchlists, briefings, and history queries. Sources: Reddit, X, YouTube, web.
last30days
Use when researching what happened in the last 30 days on a topic. Also triggered by 'last30'. Sources: Reddit, X, YouTube, web. Produces expert-level summary with copy-paste-ready prompts.
hooks
Use when generating hooks, headlines, titles, and scroll-stopping openers for content. Also use when analyzing viral posts, Reels, TikToks, YouTube Shorts, or successful social examples to extract reusable hook patterns and improve hook guidance.
evaluate-content
Use when judging content quality OR editing/improving existing copy: shareability, readability, voice, cuttability, angle, copy sweeps.
editor-in-chief
Use when a first draft is complete and all Phase 1 gates are done: topic selected (seo-research), title approved (hooks), outline approved (outline-generator), draft written (writer). Runs autonomous diagnosis-prescribe-rewrite loop before Substack.
copywriting
Write or improve marketing copy for any surface: pages, ads, app stores, landing pages, TikTok/Meta scripts, push notifications, UGC. Combines page copy frameworks with direct response principles.
content-strategy
Use when building content strategy: hooks, angles, and ideas from what's trending now. Covers organic and paid creative across TikTok, X, YouTube, Meta, LinkedIn.
content-pipeline
Orchestrator for the 3-article content pipeline — runs research phase, spawns parallel article sub-agents, creates Typefully drafts. Use when running the full content pipeline (usually via cron at 3am).