teach-impeccable

Gather project design context and write a .impeccable.md document.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/mahou-labs/shiru --skill teach-impeccable-mahou-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/mahou-labs/shiru/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/mahou-labs/shiru --skill teach-impeccable-mahou-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-time setup that gathers project design context and persists it for all future AI sessions.

Core Features & Use Cases

  • Automatically scans for README and docs, brand assets, design tokens, and existing design patterns to inform context
  • Asks targeted UX-focused questions to align style and brand voice
  • Generates or updates a Design Context document (.impeccable.md) for reuse in future interactions

Quick Start

Run this skill once to establish and persist your project's design guidelines.

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 for future AI sessions?▼

You can persist design guidelines by scanning repository readmes, tokens, and assets to generate a `.impeccable.md` document, ensuring AI sessions retain your project's design context automatically.

How do I capture design tokens and brand assets during project onboarding?▼

During onboarding, design tokens and brand assets are captured by automatically scanning the repository for readmes and assets, then asking UX-focused questions to align style and brand voice before generating the context document.

Can I update CLAUDE.md with my project's design guidelines?▼

Yes, CLAUDE.md can be updated with design guidelines. The skill writes a `.impeccable.md` document and provides an optional CLAUDE.md update if you consent to the modification during the setup process.

What is the best way to document UX constraints for codebase onboarding?▼

Documenting UX constraints during onboarding is best achieved by extracting contextual signals from your repository and prompting targeted UX questions to generate a persistent Design Context document for future reference.

Do I need existing documentation to generate a design context file?▼

Existing documentation is not strictly required to generate a design context file. The process scans available readmes and assets, but relies on prompting UX questions to fill gaps if documentation is missing.