material

Generate Material Design component guidelines with design tokens and WCAG 2.2 AA accessibility rules.

2.3k|211|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bergside/awesome-design-skills --skill material-bergside
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: material
Source: https://github.com/bergside/awesome-design-skills/tree/main/skills/material
Command: npx skills add https://github.com/bergside/awesome-design-skills --skill material-bergside

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves inconsistent UI styling and accessibility gaps by providing implementation-ready Material Design rules, tokens, and quality gates for consistent component behavior.

Core Features & Use Cases

  • Design foundations: Defines a shared typography scale, spacing rhythm, and color token palette (including primary/secondary/surface/text plus semantic states like success/warning/danger).
  • Accessibility compliance: Requires WCAG 2.2 AA, keyboard-first interaction, and explicit visible focus states with testable acceptance criteria.
  • Component guidance: Enforces consistent do/don’t rules, interaction-state modeling (default/hover/focus-visible/active/disabled/loading/error where relevant), and a QA checklist suitable for code review.

Quick Start

Use this skill to generate or update your design-system component guidelines so new and existing UI components follow Material tokens, accessible interaction states, and a reviewable QA checklist.

Frequently Asked Questions about material

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

FAQPage Schema
How do I build a Material Design system with WCAG 2.2 AA accessibility compliance?

To build a Material Design system with WCAG 2.2 AA accessibility, define explicit design tokens, enforce keyboard-first interaction, and apply visible focus states with testable acceptance criteria for UI components.

What are Material Design tokens and how do they standardize UI components?

Material Design tokens are shared variables for typography, spacing, and color palettes that standardize UI components. They define primary, secondary, surface, text, and semantic states to ensure consistent styling across products.

How do I model interaction states for accessible UI components?

Model accessible UI component interaction states by defining explicit default, hover, focus-visible, active, disabled, loading, and error behaviors. Apply concrete do and don't constraints to enforce consistent interaction modeling.

Can I use this Material Design skill to generate QA checklists for component code review?

Yes, you can use this skill to generate QA checklists for component code review. It provides testable acceptance criteria and reviewable constraints to verify accessibility compliance and token usage for UI families.

What is the best way to standardize UI styling across multiple product teams?

The best way to standardize UI styling across teams is implementing a shared Material Design foundation. Use explicit design tokens, semantic color palettes, and enforced interaction-state rules to eliminate inconsistent styling and accessibility gaps.