cafe

Standardize cafe-inspired UI components with token-based styling and WCAG 2.2 AA accessibility.

Updated May 13, 2026
One-click install
npx skills add https://github.com/superpollo02/awesome-design-skill --skill cafe-superpollo02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cafe
Source: https://github.com/superpollo02/awesome-design-skill/tree/main/skills/cafe
Command: npx skills add https://github.com/superpollo02/awesome-design-skill --skill cafe-superpollo02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams consistently build a cozy, cafe-inspired interface without drifting on typography, spacing, colors, or accessibility.

Core Features & Use Cases

  • Tokenized cafe foundation: Warm primary/neutral/surface colors, explicit typography (Poppins + JetBrains Mono), and a defined spacing scale.
  • Implementation-ready guidance: Opinionated do/don’t rules and quality gates aimed at engineering-friendly adoption.
  • Accessibility-first UX: WCAG 2.2 AA, keyboard-first interactions, and visible focus state requirements for interactive components.

Quick Start

Ask your AI agent to generate a cafe-themed component set using the provided tokens and include WCAG 2.2 AA keyboard and focus-visible behaviors.

Frequently Asked Questions about cafe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a warm cafe-inspired UI design system without drifting on spacing and typography?

To build a warm cafe-inspired UI design system, use token-based styling for colors, typography, and spacing scales. This approach enforces repeatable guidance for component layouts and interaction states, ensuring consistent visual experiences across product teams.

What typography and spacing tokens are needed for a cozy cafe-themed design system?

A cozy cafe-themed design system requires explicit typography tokens like Poppins and JetBrains Mono, a defined spacing scale, and warm primary, neutral, and surface color tokens. These foundational UI tokens ensure consistent component-level layouts.

How do I ensure my UI components meet WCAG 2.2 AA accessibility requirements?

To ensure UI components meet WCAG 2.2 AA accessibility requirements, implement keyboard-first interactions and visible focus states. Enforcing these explicit accessibility standards during component creation guarantees testable quality gates for interactive elements.

Can I use this cafe design system for generating accessible component sets with an AI agent?

Yes, you can use this cafe design system with an AI agent to generate component sets. Simply ask the agent to build cafe-themed components using the provided UI tokens while including WCAG 2.2 AA keyboard and focus-visible interaction behaviors.

What are the best practices for managing interaction states in a token-based UI design system?

Managing interaction states in a token-based UI design system requires opinionated do-and-don't rules and explicit quality gates. Standardizing focus-visible behaviors and keyboard-first interactions ensures engineering-friendly adoption and accessible component layouts.

Why do engineering teams need opinionated rules for UI tokens and interaction states?

Engineering teams need opinionated rules for UI tokens and interaction states to prevent visual drift across typography, spacing, and colors. Implementation-ready guidance with testable quality gates streamlines development and maintains accessibility standards.