Skills

Impeccable

A modern, graphic, editorial-poster aesthetic, warm and confident, built on...

Install

npx skills add bergside/awesome-design-skills --skill impeccable -g -a claude-code -y
Category
Marketing
Updated
4mo ago
License
MIT
Context cost
Lightabout 834 tokens
Runs scripts
No, instructions only

What it does

A modern, graphic, editorial-poster aesthetic, warm and confident, built on alternating cream and burnt orange sections, an amber brand color.

<!-- TYPEUI_SH_MANAGED_START -->

Impeccable 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

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. End with a QA checklist that can be executed in code review.
Read the whole SKILL.md on GitHub

More in Marketing