teach-impeccable

Gathers project design context and persists it to .impeccable.md.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/jatwell93/pharmacy-heatmap --skill teach-impeccable-jatwell93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/jatwell93/pharmacy-heatmap/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/jatwell93/pharmacy-heatmap --skill teach-impeccable-jatwell93

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gathers design context for a project and persists it for all future sessions.

Core Features & Use Cases

  • Explores the codebase to surface design considerations from README, brand assets, and design tokens
  • Asks UX-focused questions to clarify users, brand personality, and accessibility needs
  • Generates a Design Context document and writes it to the project root (.impeccable.md), updating existing files if present
  • Optionally appends guidance to .github/copilot-instructions.md when requested by the user

Quick Start

Run the teach-impeccable skill to generate and persist a design context document for this 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 a project across multiple AI sessions?

To persist design context across multiple AI sessions, you need to generate a Design Context document at your project root. This consolidates UX goals, brand attributes, and accessibility considerations, writing them to a `.impeccable.md` file to guide future interactions.

What is the best way to capture UX goals and brand tokens for AI-assisted development?

Capturing UX goals and brand tokens for AI-assisted development involves exploring the codebase and asking focused UX questions. This synthesizes design considerations into a persistent context document, ensuring brand personality and accessibility needs are applied consistently.

How do I consolidate design system tokens and accessibility needs into a single file?

You can consolidate design system tokens and accessibility needs into a single file by stepping through codebase exploration and UX questioning. This process generates a Design Context document at the project root, persisting all extracted design attributes.

Can I update existing design context files without losing previous brand attributes?

Yes, you can update existing design context files without losing previous brand attributes. The process updates the `.impeccable.md` file if it is already present, ensuring current UX goals and accessibility considerations are merged without overwriting necessary data.

Does generating a design context document also update Copilot instructions?

Generating a design context document optionally updates Copilot instructions. When requested, the process appends design guidance to the `.github/copilot-instructions.md` file, ensuring your AI assistant applies the synthesized UX and brand context during development.