premium
bergside/awesome-design-skills
Apple-inspired premium design system with precise spacing, modern typography, and refined visual language.
What is premium?
A design-system skill that provides implementation-ready guidance for creating premium, Apple-inspired interfaces. Use it when building polished, accessible UIs that prioritize semantic tokens, visual hierarchy, and WCAG 2.2 AA compliance.
- Defines a complete typography scale (12–36px) with Inter and JetBrains Mono fonts across 9 weights
- Establishes a semantic color palette (primary, secondary, success, warning, danger, surface, text) with specific hex tokens
- Provides an 8-point spacing scale (4/8/12/16/24/32) for consistent rhythm and layout
- Specifies component anatomy, states (default, hover, focus, active, disabled, loading, error), and interaction behavior
- Enforces WCAG 2.2 AA accessibility with keyboard-first interactions and visible focus states
- Includes QA checklists, anti-patterns, and migration guidance for design consistency
How to install premium
npx skills add https://github.com/bergside/awesome-design-skills --skill premiumHow to use premium
- 1.Review the typography scale, color tokens, and spacing scale to understand the foundational system
- 2.Apply semantic tokens (primary, secondary, success, etc.) instead of raw hex values in your components
- 3.Define component anatomy and required states (default, hover, focus-visible, active, disabled, loading, error)
- 4.Implement keyboard-first interactions with visible focus states per WCAG 2.2 AA
- 5.Use the QA checklist during code review to verify spacing rhythm, contrast, and interaction behavior
- 6.Reference the anti-patterns section to avoid low-contrast text, inconsistent spacing, and ambiguous labels
Use cases
- Building a cohesive design system for a SaaS or consumer product with premium positioning
- Creating component libraries with explicit state definitions and accessibility acceptance criteria
- Establishing consistent spacing, typography, and color usage across engineering and design teams
- Migrating existing inconsistent UI to a unified, Apple-inspired aesthetic
- Documenting design tokens and interaction patterns for code review and implementation
- Design system authors and maintainers
- Product engineers implementing premium UI components
- Design leads establishing brand consistency
- Teams adopting semantic token-based workflows
premium FAQ
Primary and display fonts are Inter (weights 100–900); monospace is JetBrains Mono. Use the scale 12/14/16/18/24/30/36px for consistent hierarchy.
Use semantic tokens (primary=#3B82F6, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827) instead of raw hex values to maintain consistency.
Follow the 8-point scale: 4/8/12/16/24/32px. Preserve visual hierarchy and avoid inconsistent spacing rhythm.
WCAG 2.2 AA with keyboard-first interactions, visible focus states, and no low-contrast text. Every accessibility rule must be testable in implementation.
Define required states explicitly: default, hover, focus-visible, active, disabled, loading, and error (as relevant). Specify color tokens, spacing, and interaction behavior for each state.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: premium description: Apple-inspired premium aesthetic with precise spacing, modern typography, and a refined, polished visual language. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->Premium Design System Skill (Universal)
Mission
You are an expert design-system guideline author for premium. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Apple design style
Style Foundations
- Visual style: modern
- Typography scale: 12/14/16/18/24/30/36 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#3B82F6, secondary=#8B5CF6, 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.
Related skills
More from bergside/awesome-design-skills and the wider catalog.
