Design Systems
Tailwind Design System
Map repeated CSS values to semantic Tailwind v4 tokens and migrate one component before expanding the system.
wshobsonMaterial 3
hamenBuild a Material 3 system from semantic tokens, component states, and adaptive layout needs.
SKILL.md
---
name: knoveya-material-3
description: "Build a Material 3 system from semantic tokens, component states, and adaptive layout needs. Use for matching design systems work."
---
# Material 3
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Build a Material 3 system from semantic tokens, component states, and adaptive layout needs.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
Dynamic color does not break contrast or state meaning.
## Example task
Apply a theme to both a navigation rail and a modal sheet.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Related skills
View all
How to use
Copy the full block, including its frontmatter, into a new folder named knoveya-material-3 as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-material-3/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Example
Apply a theme to both a navigation rail and a modal sheet.
Verify
Dynamic color does not break contrast or state meaning.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
Limits
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.