material

Standardize Material Design component rules with tokens and accessibility criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Material Design guidance turns UI inconsistency into a shared, implementation-ready system so teams can build coherent, accessible interfaces faster.

Core Features & Use Cases

  • Style foundations: defines typography, spacing, and color tokens (including action/intent colors) to keep design and implementation aligned.
  • Operational design-system workflow: provides a repeatable method for authoring component rules with states, variants, and responsive behavior.
  • Accessibility and quality gates: enforces testable WCAG-oriented requirements plus a QA checklist suitable for code review.
  • Use case: standardize a product’s design language across new and refactored screens by generating component rules (states, interactions, content tone) that engineering can implement consistently.

Quick Start

Use the Material skill to generate implementation-ready design-system rules for a specific component (including anatomy, states like default/hover/focus-visible/disabled, token usage, accessibility acceptance criteria, and QA checks).

Frequently Asked Questions about material

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

FAQPage Schema
How do I create implementation-ready Material Design component rules for engineering teams?

To create Material Design component rules, you define component anatomy, interaction states like default and hover, color tokens, and responsive behavior, ensuring engineering teams can implement consistent UI across product interfaces.

What are design tokens and how do they standardize UI guidelines in a design system?

Design tokens are predefined variables for typography, spacing, and color that standardize UI guidelines. They keep design and implementation aligned by providing a shared, token-first foundation for consistent component styling across product interfaces.

How do I add testable accessibility criteria to my design system's component states?

You add testable accessibility criteria by enforcing WCAG-oriented requirements for component states like focus-visible and disabled. This includes writing token-first rules with anti-patterns and a QA checklist suitable for code review.

Can I use Material Design guidelines to standardize UI across refactored screens?

Yes, you can use Material Design guidelines to standardize a product's design language across refactored screens by generating implementation-ready component rules, interaction states, and content tone standards that engineering can implement consistently.

Does this approach support authoring responsive behavior and content tone standards?

Yes, this approach provides a repeatable method for authoring component rules that include responsive behavior, interaction states, and content tone standards, ensuring design and engineering teams maintain consistent UI implementation.

What is the best way to document UI component states and anti-patterns for code review?

The best way to document UI component states and anti-patterns is to generate token-first rules with testable accessibility criteria and a QA checklist, ensuring consistent implementation and measurable quality gates during code review.