skills.rest
microlinkhq
microlinkhqOFFICIAL
Explore all skills by this author →
Website𝕏@microlinkhqGitHub

teach-impeccable

Generate a root .impeccable.md file with a Design Context section from codebase and user input.

142|31|Updated Jul 13, 2017
Search Tags:#documentation#accessibility#design systems#codebase analysis#ux research#design context#brand direction
One-click install
npx skills add https://github.com/microlinkhq/www --skill teach-impeccable-microlinkhq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/microlinkhq/www/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/microlinkhq/www --skill teach-impeccable-microlinkhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes repeated back-and-forth about project design goals by gathering clear UX and aesthetic direction from the codebase and user input, then persisting that guidance for all future work.

Core Features & Use Cases

  • Codebase-driven discovery: Scans README, configuration, components, assets, and existing design tokens to extract what’s already known.
  • UX-focused clarification: Prompts targeted questions only for what remains unclear, covering users, brand personality, aesthetic preferences, and accessibility considerations.
  • Persistent design context: Writes a synthesized ## Design Context section into a root-level .impeccable.md file (updating it if it already exists), optionally aligning with any existing CLAUDE.md section.

Quick Start

Run the teach-impeccable skill for this repository to generate or update .impeccable.md with a durable design context summary.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I persist UX and design context to avoid repeated clarification in front-end projects?▼

Persist design context by scanning your codebase for existing tokens and assets, prompting for missing UX details, and writing a durable `.impeccable.md` file to guide all future work.

What is the best way to translate existing code and brand direction into durable design guidance?▼

The best way to translate code and brand direction into durable design guidance is to extract existing design tokens and README information, clarify missing aesthetic goals, and synthesize a persistent design context file.

Can I use this design context capture tool with an existing CLAUDE.md file?▼

Yes, you can use it with an existing CLAUDE.md file. The tool updates or creates a root-level `.impeccable.md` file with an actionable design context section and can optionally align with your existing CLAUDE.md configurations.

How does codebase analysis extract accessibility and design system information?▼

Codebase analysis extracts accessibility and design system information by scanning your README, configuration files, components, and existing design tokens to discover what is already known before prompting for missing UX details.

Do I need to manually answer all UX research questions to generate the design context file?▼

No, you do not need to manually answer all UX research questions. The tool only prompts targeted questions for what remains unclear after scanning your codebase, covering users, brand personality, and accessibility considerations.

Related Skills

Explore More Design & Creative Skills→
vobasevobase
59

teach-impeccable

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

Official
Intermediate
yahya-azeemyahya-azeem

teach-impeccable

Analyze codebase artifacts and ask targeted questions to generate persistent design guidelines.

Community
Intermediate
yasim-doneryasim-doner

impeccable

Coordinate frontend UI design workflows with DESIGN.md and product tokens.

Community
Advanced
xlsamaxlsama

teach-impeccable

Analyze project files and user answers to write a Design Context section for CLAUDE.md.

Community
Intermediate