teach-impeccable

Extract design tokens and brand assets into .impeccable.md.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/aymenhamoudii/digitn-website --skill teach-impeccable-aymenhamoudii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/aymenhamoudii/digitn-website/tree/main/.qwen/skills/teach-impeccable
Command: npx skills add https://github.com/aymenhamoudii/digitn-website --skill teach-impeccable-aymenhamoudii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates repeated manual setup by extracting and persisting a project's design and brand context into a repository file so future AI sessions start with consistent, actionable design guidelines.

Core Features & Use Cases

  • Codebase exploration: Scans README, config files, components, design tokens, and brand assets to infer existing visual guidelines.
  • UX-focused discovery: Prompts the user for missing information about users, brand personality, accessibility, and aesthetic preferences.
  • Context persistence: Writes or updates a Design Context section in .impeccable.md at the project root and can optionally append the same to .github/copilot-instructions.md for broader automation.
  • Use Case: Onboard a new design or development task by running the Skill once to capture typography, color palettes, spacing scales, and brand tone so every subsequent session honors those decisions.

Quick Start

Run the teach-impeccable skill to scan the repository, ask clarifying UX questions, and create or update .impeccable.md with the project's Design Context.

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 tokens and brand guidelines for future AI sessions?

It scans your codebase to extract design tokens and brand guidelines, then writes them into a `.impeccable.md` file at the project root to ensure future AI sessions maintain consistent design context.

What is the best way to capture project design context for repository automation?

Running this Skill explores README and config files to infer visual guidelines, prompts you for missing UX decisions, and updates `.github/copilot-instructions.md` for repository automation.

How do I onboard a new front-end project with consistent style guide enforcement?

Run the Skill once to capture typography, color palettes, and spacing scales, establishing a persistent design context for all subsequent front-end development sessions.

Does this design context extraction work with existing GitHub Copilot instructions?

Yes, it optionally appends the extracted style tokens and brand guidelines directly to your `.github/copilot-instructions.md` file.

Why does my AI coding session keep missing my project's brand guidelines?

AI sessions miss brand guidelines because the design context is not persisted in the repository, which is solved by extracting readable brand assets and writing them into a `.impeccable.md` configuration file.

Can I use this to extract design tokens from an existing codebase without manual entry?

Yes, it automatically scans components and config files to infer existing visual guidelines before prompting you only for missing information.