teach-impeccable

Gathers project design context through codebase exploration and user questions, then persists it to a config file.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill teach-impeccable-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/impeccable/teach-impeccable
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill teach-impeccable-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design decisions made without documented context lead to inconsistent interfaces across sessions. This Skill captures your project's users, brand personality, and aesthetic direction once, then saves it as persistent design guidelines that inform all future design work. ## Core Features & Use Cases - Codebase Discovery: Scans README files, package configs, existing components, brand assets, and CSS variables to infer design context before asking questions. - Guided Questioning: Uses structured prompts covering users, brand personality, aesthetic preferences, and accessibility requirements to fill gaps the codebase cannot answer. - Persistent Design Context: Writes a synthesized Design Context section to .impeccable.md in the project root, with an optional copy appended to CLAUDE.md. - Use Case: Run once at the start of a new web project to establish design principles (e.g., minimal aesthetic, dark mode, WCAG AA compliance) that every subsequent UI task will follow. ## Quick Start Ask the AI to run the teach-impeccable setup to gather design context for this project and save it for future sessions.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I set up persistent design guidelines for my AI coding assistant?

Run this Skill once in your project. It scans your codebase for existing design signals, asks targeted questions about users and brand, then writes a Design Context section to .impeccable.md that guides all future sessions.

What questions does the design context setup ask?

It asks about your users and their goals, brand personality in three words, reference sites and anti-references, visual direction preferences, light or dark mode, color constraints, and accessibility requirements such as WCAG level or reduced motion needs.

Where is the design context saved after setup?

The Design Context section is written to .impeccable.md in the project root, updating the section in place if the file already exists. You can optionally also append it to CLAUDE.md when prompted.

Does the setup scan my existing codebase before asking questions?

Yes. It first explores README files, package configs, existing components, brand assets, and CSS variables or design tokens. It only asks questions about things it could not infer from that exploration.

Do I need to run the design context setup more than once?

No, it is designed as a one-time setup. Re-run it only if your brand direction, target users, or accessibility requirements change significantly, and it will update the existing section in place.