How do I install the Teach Impeccable skill?

Run npx skillmds@latest add tomevault-io/teach-impeccable in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Teach Impeccable safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Teach Impeccable?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Teach Impeccable free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Teach Impeccable?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Teach Impeccable by tomevault-io — Agent Skill

Name: Teach Impeccable
Author: tomevault-io

File contents

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 the user directly to clarify what you cannot infer. 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 .impeccable.md in the project root. If the file already exists, update the Design Context section in place.

Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github/copilot-instructions.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.

Source: joewinke/jat — distributed by TomeVault.

---name: teach-impeccabledescription: 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. Use when this capability is needed.---Gather design context for this project, then persist it for all future sessions.## Step 1: Explore the CodebaseBefore 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 Questionsask the user directly to clarify what you cannot infer. 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 ContextSynthesize 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 ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github/copilot-instructions.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.---> Source: [joewinke/jat](https://github.com/joewinke/jat) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Teach Impeccable