---
name: Contemporary
slug: contemporary
category: Frontend
description: Contemporary provides practical, implementation-ready design system guidance for modern minimalist interfaces with bento grids, dark mode, and high-performance accessible layouts. Use it when generating or reviewing UI design specifications.
github: "https://github.com/bergside/awesome-design-skills/tree/main/skills/contemporary"
stars: 2402
forks: 224
install: "npx degit https://github.com/bergside/awesome-design-skills/tree/main/skills/contemporary ~/.claude/skills/contemporary"
installs_to: ~/.claude/skills/contemporary
source_path: skills/contemporary/SKILL.md
collection_size: 25
category_size: 567
collection_url: "https://dirskills.com/collections/bergside/awesome-design-skills"
added: 2026-08-18T06:58:03.572Z
last_synced: 2026-08-18T06:58:03.572Z
canonical_url: "https://dirskills.com/skills/contemporary"
---

# Contemporary

Contemporary provides practical, implementation-ready design system guidance for modern minimalist interfaces with bento grids, dark mode, and high-performance accessible layouts. Use it when generating or reviewing UI design specifications.

**Install:**

```bash
npx degit https://github.com/bergside/awesome-design-skills/tree/main/skills/contemporary ~/.claude/skills/contemporary
```

## README

<!-- TYPEUI_SH_MANAGED_START -->
# contemporary Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for contemporary.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
Contemporary UI/UX design focuses on, minimalist, accessible, and high-performance, featuring Bento grids, dark mode, and, AI-powered personalization

## Style Foundations
- Visual style: modern, minimal, bold, playful
- Typography scale: desktop-first expressive scale | Fonts: primary=Jost, display=Jost, mono=Overpass Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral | Tokens: primary=#C800DF, secondary=#E60076, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: comfortable density mode


## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support

## Writing Tone
concise, confident, helpful, friendly, professional

## 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.

## 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.

<!-- TYPEUI_SH_MANAGED_END -->