cafe

Generate Cafe design-system guidance with tokens, states, and WCAG 2.2 AA criteria.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill cafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cafe
Source: https://github.com/PiercingXX/xx-stack/tree/main/packs/design/design-skills/cafe
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill cafe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves inconsistent UI styling by giving engineers and designers a single, implementation-ready Cafe design-system specification for building cohesive, readable interfaces.

Core Features & Use Cases

  • Design tokens & foundations: warm color palette, typography (Poppins + JetBrains Mono), and spacing rhythm anchored to explicit token values.
  • Component-level rules: opinionated guidance on anatomy, states (default/hover/focus-visible/active/disabled/loading/error where relevant), variants, and responsive/edge cases like long labels and empty states.
  • Accessibility & QA acceptance criteria: keyboard-first expectations, visible focus states, and testable rules to prevent low-contrast or vague interactions.

Quick Start

Ask the AI to generate Cafe design-system guidance for your target UI components using the Cafe foundations, required states, accessibility acceptance criteria, and a code-review QA checklist.

Frequently Asked Questions about cafe

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

FAQPage Schema
How do I create a warm design system with accessible UI components?

A cafe-inspired design system provides warm color palette tokens, Poppins and JetBrains Mono typography, and spacing rhythm to build cohesive, readable, and accessible interface components.

How do I ensure my design system meets WCAG 2.2 AA accessibility standards?

To ensure your design system meets WCAG 2.2 AA standards, define keyboard-first interaction expectations, mandate visible focus states, and establish testable acceptance criteria to prevent low-contrast or vague interactions.

What UI component states should a design system specification cover?

A design system specification should cover default, hover, focus-visible, active, disabled, loading, and error states, including responsive edge cases like long labels and empty states to ensure consistent component behavior.

Can I use token-based rules for standardizing product interface components?

Yes, you can use token-based rules to standardize product interfaces by anchoring typography, spacing, and color palette to explicit token values, ensuring consistent and readable UI styling across all components.

What is the best way to prevent low-contrast interactions in a UI design system?

The best way to prevent low-contrast interactions is to include an anti-pattern QA checklist within your design system guidance, enforcing testable accessibility rules and visible focus states during code review.