teach-impeccable

Gathers design context from a codebase and persists it to the AI config file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This one-time setup gathers design context for your project and saves it to your AI config file, ensuring consistent guidance across future sessions.

Core Features & Use Cases

  • Gather design context from the codebase (goals, branding, tokens, typography) and persist it to a centralized AI config.
  • Provide a structured prompt for onboarding new contributors with clear design guidelines.
  • Enable quick re-use of design decisions by applying the saved context to upcoming sessions and reviews.

Quick Start

Run teach-impeccable to gather design context and persist it to the 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 capture design context and save it to an AI configuration file?

Capturing design context involves reading the codebase to infer goals, branding, and design tokens, then writing a structured Design Context into the AI config file as a single authoritative entry for future sessions.

What is the best way to persist brand guidelines for AI-assisted design reviews?

Persisting brand guidelines is done by running a one-time setup that extracts design context from the codebase and saves it to a centralized AI config, ensuring consistent guidance across upcoming reviews.

How do I onboard new contributors with consistent design guidelines in AI sessions?

Onboarding new contributors with design guidelines requires a structured prompt generated from the saved design context, providing clear branding and design token rules for future AI sessions.

Can I reuse design tokens and typography settings across multiple AI sessions?

Reusing design tokens and typography across sessions is possible because the setup persists these design decisions to the AI configuration file, applying them automatically to upcoming sessions.

Does gathering design context for a project require a manual token input process?

Gathering design context does not require manual token input; the process efficiently reads the codebase to infer goals, branding, and tokens, then writes a single authoritative entry to the config.

When should I lock in design guidelines using an AI configuration file?

Locking in design guidelines using an AI config should occur during initial project setup, capturing goals and branding early to ensure consistent guidance across all future sessions.