teach-impeccable

Capture project design context and export it to .impeccable.md.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill teach-impeccable-ev3rlit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/ev3rlit/magam-canonical-archive/tree/main/.claude/skills/teach-impeccable
Command: npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill teach-impeccable-ev3rlit

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. Run once to establish persistent design guidelines.

Core Features & Use Cases

  • Collects project purpose, goals, brand assets, design tokens, and existing UI patterns from the codebase.
  • Asks UX-focused questions to clarify users, brand personality, aesthetics, and accessibility needs.
  • Writes a Design Context document and updates design guidance for ongoing use.

Quick Start

Run the one-time setup to capture and persist design guidelines for your project.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I persist design context for AI-assisted development across sessions?

To persist design context across sessions, run a one-time setup that scans your codebase, asks UX-focused questions, and writes the guidelines to a Markdown file for ongoing AI use.

What design guidelines does an AI config file need for consistent UX?

AI config files need project purpose, goals, brand assets, design tokens, and existing UI patterns to maintain consistent UX, branding, and aesthetic decisions across future sessions.

Can I update Copilot instructions with my project's design tokens and branding?

Yes, you can optionally update the Copilot instructions file to include your captured design tokens, branding, and accessibility needs for consistent AI-assisted development.

How do I capture existing UI patterns from a codebase for AI onboarding?

Capture existing UI patterns by running a setup process that scans the codebase and asks UX-focused questions, exporting the collected design tokens and patterns into a context document.

When do I need to establish persistent design context for an AI project?

Establish persistent design context during initial onboarding to ensure AI-assisted development consistently applies your branding, accessibility needs, and design tokens across all future sessions.

What are the limitations of using a one-time setup for design context capture?

A one-time setup captures a snapshot of your design context, meaning significant branding changes or new design tokens require running the setup again to update the persisted guidelines.