teach-impeccable

Collect project design context and persist it to AI configuration files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill teach-impeccable-kevin-mok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/Kevin-Mok/ai-cli-dotfiles/tree/main/dot_agents/skills/teach-impeccable
Command: npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill teach-impeccable-kevin-mok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-time setup that gathers design context for your project and saves it to your AI config file, enabling persistent design guidelines across sessions.

Core Features & Use Cases

  • Step 1: Explore the Codebase: Thoroughly scan the repository for README/docs, package configuration, existing components, brand assets, design tokens, and style guides to ground the context.
  • Step 2: Ask UX-Focused Questions: Collect clarifications on Users & Purpose, Brand & Personality, Aesthetic Preferences, and Accessibility & Inclusion to resolve ambiguities.
  • Step 3: Write Design Context: Synthesize findings into a Design Context file (e.g., .impeccable.md) and optionally update .github/copilot-instructions.md; confirm completion and summarize guiding principles.

Quick Start

Run teach-impeccable to gather design context and persist it in your AI config for future sessions.

Frequently Asked Questions about teach-impeccable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save design context for reuse across AI coding sessions?

To save design context, run the teach-impeccable skill to scan your repository, answer UX-focused questions, and persist the synthesized guidelines into an AI configuration file for future reuse.

What is the best way to generate UX design guidelines from existing codebase documentation?

Generating UX design guidelines involves scanning your repository for READMEs, brand assets, and design tokens, then resolving ambiguities by asking clarifying questions about users, aesthetics, and accessibility to output a formal context file.

How do I configure Copilot instructions to follow my project's brand personality and accessibility standards?

You can configure Copilot instructions by running a setup process that collects your project's brand personality and accessibility standards, optionally updating the .github/copilot-instructions.md file with the finalized design context.

Can I update .impeccable.md with new aesthetic preferences after the initial project setup?

Yes, you can update .impeccable.md with new aesthetic preferences by running the skill whenever you need to clarify users, brand personality, aesthetics, or accessibility to regenerate a formal Design Context.

Does this design context generation approach work without existing design tokens or style guides in the repository?

Yes, the design context generation works without existing design tokens because it thoroughly scans the repository for available assets and uses UX-focused questions to resolve ambiguities and establish guidelines.