i-teach-impeccable_skill

This skill collects design context from the project and persists it to your AI config for consistent, long-term guidelines.

Shell

31

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill steveclarke/dotfiles --skill i-teach-impeccable

SKILL.md2.8 KB

Overview

This skill performs a one-time setup that gathers design context for your project and persists it to the AI config file so every future session shares the same design guidance. It inspects the codebase, prompts for a few targeted UX and brand questions, and writes a structured Design Context to .impeccable.md at the project root. After saving, it asks whether you also want the same section appended to CLAUDE.md.

How this skill works

The skill scans repos for README, package/config files, components, brand assets, design tokens, and any style guides to infer what’s already decided. It pauses to call an AskUserQuestion tool for only the unclear or missing items (users, brand personality, accessibility needs, aesthetic direction). Finally, it synthesizes findings into a standard Design Context block and writes or updates .impeccable.md; it then asks whether to append/update CLAUDE.md as well.

When to use it

Initial project setup so design decisions are persistent across machines and sessions
Onboarding a new contributor or machine to ensure consistent visual and UX expectations
Before major UI work or refactor to lock down guiding principles
When no centralized design guidance exists in the repo
When migrating or standardizing design tokens and brand assets

Best practices

Run once per project root and commit the resulting .impeccable.md to version control
Thoroughly review project docs and styles first; only ask questions for gaps the scanner cannot answer
Keep answers concise and concrete (audience, emotional goals, color constraints, accessibility levels)
Maintain 3–5 actionable design principles that guide all future changes
Update .impeccable.md intentionally when brand or product goals change, not for every small tweak

Example use cases

You cloned a utility-tool repo and want every machine to share the same visual defaults
A solo maintainer standardizes spacing, typography, and color tokens before UI development
A small team sets a 1-hour onboarding step that establishes brand tone and accessibility targets
Preparing a repo for a design system extraction where consistent design context is essential
Ensuring CI/CD and automated AI agents use the same UI assumptions across environments

FAQ

.impeccable.md is written or updated in the project root with a ## Design Context section. If it exists, the section is replaced in place.

Will this change code or assets?

No code or binary assets are modified. The skill only reads the repo and writes the textual Design Context file; token or asset edits remain manual.

What if I want the same section in another doc?

After writing .impeccable.md the skill will ask whether you want the same Design Context appended or updated in CLAUDE.md and will proceed only with confirmation.