teach-impeccable

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

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/yahya-azeem/Pokedex --skill teach-impeccable-yahya-azeem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/yahya-azeem/Pokedex/tree/main/library/impeccable/skills/teach-impeccable
Command: npx skills add https://github.com/yahya-azeem/Pokedex --skill teach-impeccable-yahya-azeem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

teach-impeccable helps you avoid repeatedly re-explaining your project’s UI/brand/design constraints by gathering design-relevant context and persisting it into your AI configuration.

Core Features & Use Cases

  • Codebase-driven design discovery: Scans documentation and existing design artifacts (README/docs, configs, components, brand assets, tokens) to infer what’s already decided.
  • UX-focused gap questioning: Asks only the questions that can’t be determined from the codebase to clarify users, brand personality, aesthetic direction, and accessibility needs.
  • Persistent design guidelines generation: Writes a structured ## Design Context section into a .impeccable.md file (creating or updating it), and can also append/update that same context in your configured AI config file for future sessions.
  • Future-proofing: Produces a reusable set of design principles that guide all subsequent design work for the project.

Quick Start

Run teach-impeccable to explore your project, answer the UX questions it prompts, and generate/update the Design Context in .impeccable.md for future sessions.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I capture and persist design context for my project?

To capture design context, this Skill scans your codebase for brand assets and design tokens, asks targeted UX questions for missing details, and persists the structured guidelines into a .impeccable.md file for future AI sessions.

What is the best way to stop re-explaining brand guidelines to my AI assistant?

The best way to stop re-explaining brand guidelines is to generate a persistent Design Context file. This Skill analyzes your existing artifacts and saves consistent design principles to your AI configuration, ensuring future sessions follow them automatically.

How does codebase-driven design discovery work for UX research?

Codebase-driven design discovery works by scanning your project's documentation, configurations, and existing components to infer established UX and design decisions, reducing the need for manual input during project onboarding.

Can I align a new front-end project with an existing design system automatically?

Yes, you can align front-end work with an existing design system. The Skill extracts design tokens and brand assets from your codebase, asks clarifying questions about accessibility needs, and generates a reusable set of design principles for ongoing development.

Do I need existing design tokens in my codebase to establish persistent design guidelines?

No, you do not need existing design tokens. If the Skill cannot find design artifacts in your codebase, it will ask targeted UX-focused questions about your brand personality, aesthetic direction, and accessibility needs to establish the guidelines from scratch.

When should I not use an automated design context capture approach?

You should avoid automated design context capture if your project lacks both a codebase to scan and clear UX decisions to share, as the Skill relies on existing artifacts or your direct answers to generate a structured design context.