Scan repository design tokens and write UX context to .impeccable.md.
npx skills add https://github.com/jcdiv47/cool-paper --skill teach-impeccable-jcdiv47
Please help me install this Agent Skill. Skill: teach-impeccable Source: https://github.com/jcdiv47/cool-paper/tree/main/.agents/skills/teach-impeccable Command: npx skills add https://github.com/jcdiv47/cool-paper --skill teach-impeccable-jcdiv47
Many projects lack a persistent, machine-readable design context, which leads to inconsistent UI decisions, onboarding friction, and repeated design questions across sessions. This Skill automates gathering visual and UX context from the repository and saves a concise Design Context to the project's AI config so future sessions reuse the same guidelines.
Persist project design guidelines by scanning the repository, asking the UX questions listed in the skill, and writing a Design Context section to .impeccable.md.
High-intent search queries and answers about installing and using this skill.
To establish persistent design guidelines, you can scan your repository's README, docs, components, and style tokens, then save the extracted design context to an AI config file like .impeccable.md. This ensures consistent UI and branding decisions across future sessions.
A machine-readable design context is a concise set of design rules and tokens saved to an AI config file. It solves UI inconsistency by providing future AI sessions with persistent guidance on typography, branding, and patterns, eliminating repeated design questions.
You can onboard a new designer by scanning the codebase for brand assets and style tokens, asking targeted UX questions to resolve ambiguities, and writing a Design Context section to .impeccable.md. This documents existing design principles for consistent UI generation.
Automatic repository analysis extracts existing design tokens and patterns, but it pauses to ask focused UX and brand questions where the codebase is ambiguous. This ensures human-aligned decisions before writing the final design guidelines to your AI config.
Writing design context to CLAUDE.md works for front-end onboarding by appending persistent UI and branding guidelines. The skill optionally adds the documented design rules there, ensuring all future AI sessions reuse the same visual standards.
A repository scan cannot infer unwritten UX intent, so it limits accuracy when code is ambiguous. It requires targeted UX questions to fill gaps before writing to .impeccable.md, meaning incomplete repos may yield partial design guidelines.
1IssaMohamedScan codebase artifacts and write a CLAUDE.md Design Context.
ai-sapira-pocAssess and implement systematic typography systems for interfaces and documents.
gabriellpequenoEnforce external UI guideline compliance during front-end design reviews and critiques.
Bigalan09Collect design context and persist guidelines to the AI config file.
