impeccable skill
✓ VerifiedProvides design system guidelines and implementation-ready guidance for a modern, editorial-poster aesthetic.
- GitHub stars
- 3,629
- Files
- 2
- Last commit
- Jun 28, 2026
- License
- MIT
- Allowed tools
- —
What does the impeccable skill do?
impeccable provides design system guidelines and implementation-ready guidance for a modern, editorial-poster aesthetic.
Summary generated from the skill's SKILL.md.
About the impeccable skill
Designing interfaces with a modern, graphic, editorial-poster aesthetic is what this skill enables for engineers and designers. It provides implementation-ready guidance based on a warm and confident brand identity characterized by alternating cream and burnt orange sections with an amber brand color. An agent should load this skill when it needs to generate design system documentation, component rules, or technical specifications that adhere to specific visual foundations.
The skill produces structured guidance including design tokens, component anatomy, and accessibility acceptance criteria. It relies on a specific typography scale using Chakra Petch and JetBrains Mono, a defined color palette featuring primary amber and secondary burnt orange, and a strict spacing scale. Users receive opinionated, concise instructions that prioritize WCAG 2.2 AA accessibility standards and semantic tokens over raw values to ensure consistency across digital products.
What an agent can do with it
- 1Generate component documentationCreate detailed rules for a new UI component including its anatomy, states, and responsive behavior.
- 2Establish design tokensDefine the foundational color, typography, and spacing scales for a project.
- 3Audit for accessibilityEnsure all design decisions meet high accessibility standards and include testable criteria.
- 4Create developer QA checklistsProduce a list of requirements to verify implementation during a code review.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the impeccable skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the impeccable skill in Claude Code
~/.claude/skills/impeccable/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/impeccable ~/.claude/skills/impeccableInstall the impeccable skill in Claude Code (project)
.claude/skills/impeccable/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/impeccable .claude/skills/impeccableInstall the impeccable skill in Codex
~/.agents/skills/impeccable/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/impeccable ~/.agents/skills/impeccableInstall the impeccable skill in Gemini CLI
~/.gemini/skills/impeccable/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/impeccable ~/.gemini/skills/impeccableInstall the impeccable skill in Claude.ai
npx degit bergside/awesome-design-skills/skills/impeccable impeccable && zip -r impeccable.zip impeccable # claude.ai → Customize → Skills → + → Create skill → Upload a skill → impeccable.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablebergside/awesome-design-skills/skills/impeccable is public and reachablegithub.com/bergside/awesome-design-skills/tree/HEAD/skills/i ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-06-28github.com/bergside/awesome-design-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/bergside/awesome-design-skills/blob/HEAD/skills/i ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/bergside/awesome-design-skills/blob/HEAD/skills/i ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/bergside/awesome-design-skills/blob/HEAD/skills/i ↗Finding
SKILL.md
View on GitHubImpeccable Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Impeccable. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.
Style Foundations
- Visual style: modern, clean, high-contrast
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Chakra Petch, display=Chakra Petch, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#CC8800, secondary=#C55221, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
Files in this skill
2impeccable skill questions
How do I install the impeccable skill in Claude Code?
Run npx degit bergside/awesome-design-skills/skills/impeccable ~/.claude/skills/impeccable. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the impeccable skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What is the visual aesthetic of the Impeccable design system?
It features a modern, graphic, editorial-poster aesthetic that is warm and confident, utilizing alternating cream and burnt orange sections with an amber brand color.
Which fonts are used in this design system?
The system uses Chakra Petch for primary and display fonts, and JetBrains Mono for monospaced text.
What accessibility standards does the system follow?
The system adheres to WCAG 2.2 AA standards and emphasizes keyboard-first interactions and visible focus states.