teach-impeccable_skill

This skill gathers project design context and persists it in your AI config to enforce consistent design guidelines across sessions.

JavaScript

10.4k

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 pbakaus/impeccable --skill teach-impeccable

SKILL.md2.7 KB

Overview

This skill performs a one-time design-context capture for your project and persists it to the project's AI config. It scans the codebase, asks targeted UX and brand questions, and writes a consolidated Design Context to .impeccable.md. The goal is to create a persistent, machine-readable design language that guides every future AI session.

How this skill works

The skill inspects README, package.json, components, brand assets, CSS variables, and any style guides to infer visual and interaction patterns. It then asks only the UX-focused questions needed to fill gaps you couldn’t infer from the codebase. Finally, it synthesizes findings into a Design Context section and writes or updates .impeccable.md, with an optional append/update to your AI config file.

When to use it

Initial project setup to establish a persistent design language
When onboarding new designers or AI assistants to the project
Before major UI refactors or redesigns to keep decisions consistent
When adding new components to ensure alignment with existing tokens and patterns
If visual or accessibility requirements are unclear and need to be formalized

Best practices

Run once early in the project lifecycle and re-run only for major brand or product shifts
Scan the entire repo first — only ask questions about what can’t be inferred from files
Keep answers concise and actionable for direct inclusion in the Design Context
Prefer concrete tokens (hex values, font stacks, spacing scales) over vague preferences
Commit .impeccable.md to version control so the design language is auditable and shareable

Example use cases

Establishing consistent color, typography, and spacing rules for a new app
Capturing brand tone and accessibility targets before building UI components
Persisting design decisions so AI assistants can generate UI that fits the product’s voice
Updating component libraries with a single source of visual truth
Onboarding contractors or external vendors to the product’s visual and interaction expectations

FAQ

.impeccable.md in the project root contains the Design Context; you can opt to also append/update your AI config file.

Do I need to answer every question?

No. The workflow only asks questions that couldn’t be inferred from the codebase scan; skip items that are already clear.

Can I update the Design Context later?

Yes. Re-run the skill or manually edit .impeccable.md; the skill will update the Design Context in place if it already exists.