teach-impeccable

Scan repository files and write design context to .impeccable.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill teach-impeccable-tdalile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/teach-impeccable
Command: npx skills add https://github.com/tDalile/dotfiles --skill teach-impeccable-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures scattered design, brand, and UX information from a codebase and turns it into a persistent, machine-readable Design Context so future AI sessions and contributors have consistent guidance and avoid ad-hoc decisions.

Core Features & Use Cases

  • Repository discovery: Scan README, configs, package files, components, assets, and any existing design tokens or brand files to collect explicit and implicit design signals.
  • Targeted UX interrogation: Ask concise, user-facing questions about users, brand personality, accessibility needs, and aesthetic preferences to fill gaps the codebase cannot reveal.
  • Synthesis and persistence: Create or update a standardized ## Design Context section in .impeccable.md and optionally append the same guidance to .github/copilot-instructions.md for persistent, project-wide AI behavior.
  • Use case: Run once when onboarding an AI assistant to a new repository to establish consistent visual and interaction guidelines that will be reused across future tasks.

Quick Start

Gather design context from this repository, save it to .impeccable.md, and then ask me any unanswered UX or brand questions.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I establish persistent design guidelines for my repository?

To establish persistent design guidelines, this Skill scans your repository's README, configs, components, and assets, then synthesizes a Design Context section into .impeccable.md for consistent future AI guidance.

What is the best way to onboard an AI assistant to existing project brand and UX rules?

Onboarding an AI assistant to brand and UX rules involves scanning your codebase for design tokens and brand files, asking targeted questions to fill gaps, and writing the synthesized guidelines to .github/copilot-instructions.md.

Can I extract design context from existing code and components automatically?

You can extract design context automatically by running a one-time setup scan that collects explicit and implicit design signals from package files, components, assets, and existing design tokens across your repository.

How do I document missing UX and brand details in a machine-readable format?

To document missing UX and brand details, the Skill prompts you with concise questions about users, accessibility needs, and aesthetic preferences, then persists the clarified answers into a standardized Design Context section.

Does this design context setup process work without existing design tokens?

The setup process works without existing design tokens by relying on targeted user interrogation to surface missing UX and brand details, ensuring a complete Design Context even when the codebase lacks explicit design files.