teach-impeccable

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

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Gyanano/Bower --skill teach-impeccable-gyanano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/Gyanano/Bower/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/Gyanano/Bower --skill teach-impeccable-gyanano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project-specific design intent from getting lost by capturing a comprehensive context summary before any further work begins, ensuring future sessions inherit the same guiding principles.

Core Features & Use Cases

  • Context Discovery: Explore README files, docs, configs, components, and brand assets to catalog the existing design signals that define the project’s visual direction.
  • Clarification Engine: Pause to call AskUserQuestion when critical UX, brand, or accessibility details remain unclear so that assumptions are avoided.
  • Persistent Guidelines: Synthesize findings into a ## Design Context section, write it to .impeccable.md, and optionally update AGENTS.md so every collaborator can rely on the documented principles.

Quick Start

Document the project's design context and write it to .impeccable.md before asking any follow-up UX questions.

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 sessions for a local-first UX research repository?

To persist design context, scan READMEs, configs, and brand assets to synthesize a Design Context entry, then write it to a .impeccable.md file so future sessions inherit the same guiding principles.

What is the best way to document project-specific brand guidelines before starting UX research?

Documenting brand guidelines involves scanning project assets and components to catalog visual direction, composing a summary, and writing it to .impeccable.md to ensure consistent definitions of users and aesthetics.

How do I prevent AI from making assumptions about missing accessibility details during project onboarding?

To prevent assumptions during project onboarding, pause the workflow and invoke a clarification engine to ask the user directly about unresolved UX, brand, or accessibility details before finalizing the context.

Does capturing design context work with existing AGENTS.md files for team collaboration?

Yes, capturing design context works with existing AGENTS.md files by optionally updating them alongside the .impeccable.md file, ensuring every collaborator can rely on the documented UX principles.

When do I need to scan project components and configs for design context discovery?

You need to scan project components and configs for design context discovery before any further work begins, ensuring project-specific design intent is captured and not lost between sessions.