teach-impeccable

Gather design context from code and persist it to the AI config.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gathers the project's design context from code, docs, and assets and persists it to the AI config for consistent guidelines across sessions and teams.

Core Features & Use Cases

  • Gathers design context from README/docs, token values, color palettes, typography, and brand assets to establish a single source of truth.
  • Persists guidelines to your AI config so future sessions and AI assistants operate with aligned design rules.
  • Use Case: onboarding a new developer or designer, or refreshing tokens and brand rules across projects to reduce drift.

Quick Start

Gather design context from the repository and persist it to your AI config for all 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 persist design context to AI config for consistent UX guidelines?

To persist design context to AI config, the Skill extracts design rules from your codebase, docs, and brand assets, writing a persistent file validated against the AI config path for future sessions.

What is the best way to capture design tokens for onboarding new developers?

Capturing design tokens for onboarding involves scanning the repository for color palettes, typography, and token values to establish a single source of truth written directly to your AI config.

How does persisting brand guidelines reduce design drift across projects?

Persisting brand guidelines reduces design drift by writing a one-time design-context file to the AI config, ensuring all future AI assistants and sessions operate with aligned design rules.

Can I audit and refresh brand consistency across multiple projects using AI config?

Yes, you can refresh brand consistency by gathering updated design context and token values from the codebase, validating the AI config path, and persisting the new rules for all sessions.

Do I need to manually update AI config every session to maintain design context?

No, a one-time setup gathers the project's design context and persists it to the AI config, automatically applying the validated design rules to all future sessions without manual updates.