teach-impeccable

Gathers project design context and writes persistent design guidelines to a config file.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/AkaraChen/proxy-up --skill teach-impeccable-akarachen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teach-impeccable
Source: https://github.com/AkaraChen/proxy-up/tree/main/.agents/skills/teach-impeccable
Command: npx skills add https://github.com/AkaraChen/proxy-up --skill teach-impeccable-akarachen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants lack persistent knowledge of your project's design direction, so every session starts from scratch with inconsistent visual decisions. This Skill captures your brand personality, aesthetic preferences, and accessibility requirements once and stores them where future sessions can reuse them. ## Core Features & Use Cases - Codebase Design Discovery: Scans README files, package configs, components, brand assets, and CSS variables to infer existing design patterns before asking questions. - Guided UX Questionnaire: Asks targeted questions about users, brand personality, aesthetic direction, and accessibility needs only where the codebase leaves gaps. - Persistent Design Context: Writes a structured Design Context section to .impeccable.md and optionally to .github/copilot-instructions.md so all future AI sessions follow the same guidelines. - Use Case: A developer starting a new Vite monorepo runs this once to establish that the product targets enterprise users, should feel calm and confident, uses dark mode, and must meet WCAG AA—every later design task then follows these principles automatically. ## Quick Start Run the teach-impeccable skill to analyze my project and set up persistent design guidelines.

Frequently Asked Questions about teach-impeccable

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

FAQPage Schema
How do I give my AI assistant persistent design guidelines for a project?▼

Run this Skill once in your project root. It scans your codebase for existing design signals, asks clarifying questions about brand and users, then writes a Design Context section to .impeccable.md that future sessions can reference.

What questions does the design context setup ask?▼

It asks about users and their goals, brand personality in three words, reference and anti-reference sites, visual direction preferences, light or dark mode, color constraints, and accessibility requirements such as WCAG level or reduced motion needs.

Does it work with GitHub Copilot instructions?▼

Yes. After writing .impeccable.md, it asks whether you also want the Design Context appended to .github/copilot-instructions.md, and updates that section in place if you confirm.

Can I run the design context setup more than once?▼

Yes. If .impeccable.md already exists, the Skill updates the Design Context section in place rather than duplicating it, so re-running refreshes your guidelines safely.

What does the design setup scan in my codebase?▼

It examines the README and docs, package.json and config files, existing components, brand assets like logos and favicons, CSS variables and design tokens, and any style guides to infer design patterns before asking questions.