teach-impeccable

Scan repositories and write design context to .impeccable.md.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill teach-impeccable-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/Catsofsuffering/CCGS/tree/main/templates/skills/impeccable/teach-impeccable
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill teach-impeccable-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and persist a project's design context so future sessions and contributors follow consistent UX, brand, and visual decisions without re-asking the same foundational questions.

Core Features & Use Cases

  • Repository exploration: Scan READMEs, config files, components, design tokens, and brand assets to infer existing design constraints.
  • Targeted user discovery: Ask concise UX-focused questions to fill gaps about users, brand personality, accessibility needs, and aesthetic direction.
  • Design Context authoring: Synthesize findings into a structured Design Context section and write or update .impeccable.md in the project root, with an option to append the same section to CLAUDE.md.
  • Use Case: Onboard a new design/AI session with a consistent style guide so future tasks (copy, UI tweaks, component design) adhere to established principles.

Quick Start

Teach the repository's design context and save it to .impeccable.md.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I maintain consistent UX and brand guidelines across different coding sessions?

A design context file captures your project's UX constraints, brand personality, and visual tokens, persisting them in the repository. This ensures future sessions and contributors automatically follow established design principles without needing to re-establish guidelines.

What is the best way to document design tokens and style guides for an existing codebase?

The best way is to scan existing repository files like components, config, and design tokens to infer constraints, then synthesize them into a structured design context section saved as a markdown file in the project root for persistent reference.

How do I onboard a new AI session to follow my project's visual style and accessibility needs?

You can onboard an AI session by generating a design context file that captures your project's aesthetic direction, accessibility needs, and brand personality. This file guides the session's future UI and component decisions to align with established principles.

Does generating a persistent design context require existing design files in the repository?

No, it does not require existing design files. The process scans available repository components and brand assets to infer constraints, then fills any gaps by asking targeted UX questions about users, accessibility needs, and aesthetic direction.

Can I append the synthesized design context directly to my CLAUDE.md file?

Yes, you can append the synthesized design context to CLAUDE.md. The process writes the structured section to a dedicated .impeccable.md file in the project root and optionally appends the same content to CLAUDE.md for broader session visibility.

What limitations exist when scanning a repository to infer brand and UX constraints?

The main limitation is that inference quality depends on the repository containing sufficient READMEs, config files, or brand assets. When these are absent, the process relies heavily on targeted user discovery questions to manually establish the missing UX foundations.