Cafe
- 102 installs
- 2.2k repo stars
- Updated June 28, 2026
- bergside/awesome-design-md-skills
cafe is a design-system skill that authors UI guidelines for a cozy cafe-inspired style with warm tones, soft typography, and clean layouts.
About
This skill makes the agent a design-system guideline author for the Cafe style, a cozy cafe-inspired interface blending warm tones, soft typography, and clean layouts for a relaxed browsing experience. It supplies concrete tokens (Poppins typography, a #5D4432 brown primary, an #F9F7F5 surface, a 2/4/8/12/16/24/32/48 spacing scale), WCAG 2.2 AA rules, and a required output structure with component rules and a QA checklist. A developer uses it to keep a warm, relaxed interface consistent and accessible.
- Authors design-system guidance for a warm, cozy cafe-inspired style
- Ships concrete tokens: Poppins type, #5D4432 brown primary, #F9F7F5 surface
- Enforces WCAG 2.2 AA and a code-review QA checklist
Cafe by the numbers
- 102 all-time installs (skills.sh)
- Ranked #1,126 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
cafe capabilities & compatibility
- Capabilities
- design system · ui design · design tokens
- Use cases
- ui design · web design
What cafe says it does
Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts for a relaxed browsing experience.
A cozy café-inspired interface that blends warm tones, soft typography, and clean layouts to create a relaxed browsing experience
Tokens: primary=#5D4432, secondary=#E9E3DD, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#F9F7F5, text=#3E2B1E
npx skills add https://github.com/bergside/awesome-design-md-skills --skill cafeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 102 |
|---|---|
| repo stars | ★ 2.2k |
| Last updated | June 28, 2026 |
| Repository | bergside/awesome-design-md-skills ↗ |
What it does
Generate design-system guidance for a warm, cozy cafe-inspired interface style.
Who is it for?
Building a warm, relaxed, cozy interface with soft typography and clean layouts using defined tokens.
When should I use this skill?
You need design-system rules or tokens for a warm, cafe-inspired interface.
What you get
A token-driven, WCAG 2.2 AA guideline for a cozy, relaxed browsing interface.
- Design-system guidance covering tokens, component rules, accessibility criteria, and a QA checklist
By the numbers
- Spacing scale 2/4/8/12/16/24/32/48
Files
<!-- TYPEUI_SH_MANAGED_START -->
Cafe Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Cafe. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
A cozy café-inspired interface that blends warm tones, soft typography, and clean layouts to create a relaxed browsing experience
Style Foundations
- Visual style: minimal, clean
- Typography scale: desktop-first expressive scale | Fonts: primary=Poppins, display=Poppins, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#5D4432, secondary=#E9E3DD, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#F9F7F5, text=#3E2B1E
- Spacing scale: 2/4/8/12/16/24/32/48
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.
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 -->
Overview
Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts for a relaxed browsing experience.
Style Foundations
- Visual style: minimal, clean
- Typography scale: desktop-first expressive scale
- Typography fonts: primary=Poppins, display=Poppins, mono=JetBrains Mono
- Typography weights: 100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger
- Spacing scale: 2/4/8/12/16/24/32/48
Colors
- Primary (#5D4432): Token from style foundations.
- Secondary (#E9E3DD): Token from style foundations.
- Success (#16A34A): Token from style foundations.
- Warning (#D97706): Token from style foundations.
- Danger (#DC2626): Token from style foundations.
- Surface (#F9F7F5): Token from style foundations.
- Text (#3E2B1E): Token from style foundations.
- Neutral (#F9F7F5): Derived from the surface token for official format compatibility.
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.716k165k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.498k29.6k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst389k16k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k476
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.301k69.4k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.290k112kFAQ
What is the cafe style?
A cozy cafe-inspired interface blending warm tones, soft typography, and clean layouts for a relaxed browsing experience, using Poppins type and a #5D4432 brown primary.
What surface color does it use?
A soft #F9F7F5 surface with a 2/4/8/12/16/24/32/48 spacing scale.