i-teach-impeccable

Capture project design context into a persistent .impeccable.md file.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/alexzhang1030/platform-demo --skill i-teach-impeccable-alexzhang1030
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-teach-impeccable
Source: https://github.com/alexzhang1030/platform-demo/tree/main/.agents/skills/i-teach-impeccable
Command: npx skills add https://github.com/alexzhang1030/platform-demo --skill i-teach-impeccable-alexzhang1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams establish clear, persistent design direction when a project has incomplete or scattered visual guidance, reducing rework and inconsistent UI decisions.

Core Features & Use Cases

  • Scans repository docs, config files, existing components, and design tokens to infer the current visual language.
  • Asks only the UX, brand, aesthetic, and accessibility questions that cannot be answered from the codebase.
  • Writes a reusable Design Context section to .impeccable.md and can also append it to .github/copilot-instructions.md.
  • Useful for onboarding a new project, resetting stale design assumptions, or aligning AI-assisted work to a consistent product style.

Quick Start

Use this skill to gather the project’s design context, save it to .impeccable.md, and ask whether to also sync it to .github/copilot-instructions.md.

Frequently Asked Questions about i-teach-impeccable

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

FAQPage Schema
How do I establish consistent design context when my project has scattered UI patterns?

To establish design context, scan repository docs, config files, and design tokens to infer the visual language, then ask clarifying UX and brand questions to generate persistent guidance in .impeccable.md.

Can I sync my design system guidelines directly to Copilot instructions?

Yes, you can sync design system guidelines by writing the established design context to .impeccable.md and appending it directly to .github/copilot-instructions.md for AI-assisted work.

What is the best way to align AI-assisted product work with existing brand guidelines?

The best way to align AI-assisted work with brand guidelines is to audit existing codebase components and design tokens, answering only missing accessibility and aesthetic questions to create reusable design direction.

How do I extract design tokens and UX research context from an existing codebase?

Extract design tokens and UX context by scanning repository docs, config files, and existing UI patterns to infer the current visual language, capturing missing aesthetic details through targeted user answers.

Does this approach work for onboarding a new project with incomplete visual direction?

Yes, this approach works for onboarding a new project with incomplete visual direction by auditing scattered design docs and existing components to generate a persistent, aligned design context file.

When should I not use automated repository audits for UX clarification?

Avoid automated repository audits for UX clarification when a project completely lacks existing docs, design tokens, or UI patterns, as the tool requires existing codebase clues to infer visual language.