Tailwind Design System
Map repeated CSS values to semantic Tailwind v4 tokens and migrate one component before expanding the system.
Resolve visual direction through audience, content, typography, and density rather than fashionable defaults.
---
name: knoveya-taste-design
description: "Resolve visual direction through audience, content, typography, and density rather than fashionable defaults. Use for matching design systems work."
---
# Taste Design
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Resolve visual direction through audience, content, typography, and density rather than fashionable defaults.
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
The direction explains why it fits this product.
## Example task
Choose an editorial hierarchy for a long-form research interface.
## 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-taste-design as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-taste-design/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.
Choose an editorial hierarchy for a long-form research interface.
The direction explains why it fits this product.
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.