teach-impeccable

Extract UX and design intent from codebases into .impeccable.md.

Updated May 5, 2026
One-click install
npx skills add https://github.com/riabtsev/viscore_main --skill teach-impeccable-riabtsev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/riabtsev/viscore_main/tree/main/.github/skills/teach-impeccable
Command: npx skills add https://github.com/riabtsev/viscore_main --skill teach-impeccable-riabtsev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered UI and brand intent into a persistent, reusable design context so future AI-assisted work stays consistent with your project’s purpose, personality, and aesthetic direction.

Core Features & Use Cases

  • Codebase-driven design discovery: Scans README, configs, components, brand assets, and existing tokens to extract what’s already decided.
  • UX-focused clarification prompts: Asks only the missing questions (users, brand personality, aesthetic direction, accessibility) to reduce back-and-forth.
  • Persistent “Design Context” authoring: Writes a structured Design Context section into .impeccable.md and optionally appends/updates it in your AI config file for reuse in future sessions.

Quick Start

Run the skill once to generate or update the Design Context in the project root at .impeccable.md, then confirm whether it should also be appended to your AI config file.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I create persistent design context for AI-assisted development?

To create persistent design context, scan your existing project documentation and brand assets, then synthesize them into a structured Design Context section written directly to a .impeccable.md file for future AI sessions to reference.

What is the best way to establish consistent UI and brand guidelines across ongoing development?

Establishing consistent UI and brand guidelines is done by extracting existing design intent from your codebase and answering targeted UX prompts, which generates a durable configuration file that informs all subsequent design decisions.

Do I need to manually document all my brand guidelines before setting up design context?

You do not need to manually document all brand guidelines, because the tool scans your README, configs, and components to extract existing decisions, only asking you clarifying questions about missing information like accessibility or brand personality.

How does UX research factor into generating a project's design voice configuration?

UX research factors into the design voice configuration through focused clarification prompts that gather missing user intent and aesthetic direction, ensuring the finalized Design Context accurately reflects both codebase constraints and user needs.

Can I append the generated Design Context directly to my existing AI config file?

You can append the generated Design Context to your existing AI config file, allowing you to automatically reuse your established UX and brand principles across future AI-assisted development sessions without manual copying.

Why does my AI-assisted UI development lose track of my project's brand personality over time?

AI-assisted development loses track of brand personality because design intent is scattered across undocumented assets, an issue solved by persisting a structured Design Context file that consistently anchors future generations to your original aesthetic direction.