teach-impeccable

Scan a codebase and write design context to .impeccable.md.

7|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Davie521/claude-skills --skill teach-impeccable-davie521
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/Davie521/claude-skills/tree/main/plugins/design/skills/teach-impeccable
Command: npx skills add https://github.com/Davie521/claude-skills --skill teach-impeccable-davie521

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects and persists project design context, enabling a single setup to guide future AI interactions.

Core Features & Use Cases

  • Automatic context capture: Scans the repository for README, brand assets, tokens, and style guides to build a design brief.
  • Persistent configuration: Writes a Design Context file (.impeccable.md) and optionally updates CLAUDE.md to share guidelines across sessions.
  • Guided handoff: Provides prompts and a design rationale to ensure consistent design decisions across teams and sessions.

Quick Start

Run the teach-impeccable skill to gather design context and persist guidelines to your AI config.

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 across multiple AI sessions?

To persist design context across sessions, this Skill scans your codebase for brand assets and style guides, then writes a persistent configuration file to ensure future AI interactions follow your established design guidelines.

What is the best way to establish AI design policies during project onboarding?

Establishing AI design policies during onboarding involves scanning the repository for design tokens and style guides, then writing a Design Context file to configure persistent AI behavior for future tasks.

How do I generate a design brief from existing brand guidelines and codebase assets?

Generating a design brief from existing assets is done by automatically scanning your repository for README files, brand assets, and style guides to capture and consolidate the project's design context.

Does this approach to design context require updating CLAUDE.md manually?

Updating CLAUDE.md manually is not required; the Skill optionally writes the Design Context directly to CLAUDE.md and prompts you for confirmation before finalizing any configuration changes.

Can I use this to share design system guidelines across a team?

Yes, you can share design system guidelines across a team by generating a persistent Design Context file that provides design rationale and guided handoff for consistent decisions across sessions.

What are the limitations of persisting design context in a markdown file?

Persisting design context in a markdown file limits configuration to text-based guidelines and requires user confirmation before finalization, meaning complex visual design system rules may need manual clarification.