shadcn/ui
Use existing shadcn components and installed primitives before inventing replacements.
Map repeated CSS values to semantic Tailwind v4 tokens and migrate one component before expanding the system.
---
name: knoveya-tailwind-design-system
description: "Map repeated CSS values to semantic Tailwind v4 tokens and migrate one component before expanding the system. Use for matching design systems work."
---
# Tailwind Design System
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Map repeated CSS values to semantic Tailwind v4 tokens and migrate one component before expanding the system.
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
Both themes resolve through semantic roles without hardcoded exceptions.
## Example task
Define a surface/ink pair, then test a disabled button on it.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-tailwind-design-system as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-tailwind-design-system/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.
Define a surface/ink pair, then test a disabled button on it.
Both themes resolve through semantic roles without hardcoded exceptions.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.