This is your single entry point for any visual HTML/CSS/JS work, whether you're building a landing page, dashboard, or web app. It forces you to pick a build track upfront (hand-built static or component library), then runs a mandatory taste layer from an external GitHub skill for style decisions while keeping engineering quality (accessibility, responsiveness, performance, motion design) in house. The integration model is clean: taste-skill handles Brief Inference, Design Dials, and anti-slop rules, while ui-design owns track selection, component strategy, and delivery. One catch: it requires interactive pages to have actual motion design, not just static hover states. If you ship UI with Claude, this is the orchestration layer.
npx -y skills add starchild-ai-agent/official-skills --skill ui-design --agent claude-codeInstalls into .claude/skills of the current project.
This skill is the single entry point for visual work.
Use it for any user-facing HTML/CSS/JS output: landing pages, dashboards, product UI, internal tools, and portfolio pages.
Choose deliberately before coding:
Track decision and component-library strategy are always owned by ui-design.
Inside ui-design workflow, invoke taste-skill for exactly these 3 style blocks:
ui-design keeps ownership of engineering quality and delivery.taste-skill provides style direction and anti-template taste constraints.This avoids overlap with ui-design’s engineering references (component libraries, a11y, preview, data dashboard implementation).
ui-design to select Track A/B.One sentence summary:
Hard rule: if the page has interactions, motion design is mandatory (at least tactile feedback + state transition feedback). Static-looking interaction states are treated as incomplete UI.
When rules overlap:
Engineering safety includes: accessibility, responsive stability, interaction reliability, runtime correctness, and performance constraints.
Do not maintain a local mirror or version-stamp file.
Always read/update taste rules directly from GitHub:
https://github.com/Leonxlnx/taste-skillhttps://github.com/Leonxlnx/taste-skill/blob/main/skills/taste-skill/SKILL.mdhttps://raw.githubusercontent.com/Leonxlnx/taste-skill/main/skills/taste-skill/SKILL.mdhttps://github.com/Leonxlnx/taste-skill/tree/main/skillsWhen taste-skill updates, re-check the GitHub source directly and apply needed changes in the ui-design overlay contract.
| File | Purpose |
|---|---|
references/design-process.md | Engineering quality gate (a11y/theme/responsive/interaction/runtime checklist) |
references/component-libraries.md | shadcn/ui · HeroUI · coss ui selection + lookup workflow |
references/animations.md | Motion implementation standards, interactive-motion requirements (integrated with emil-design-eng decision framework), and GSAP usage notes |
references/charts.md | Chart.js/ECharts implementation patterns |
references/dashboards.md | Data sourcing, real-time updates, dashboard structure, performance |
| taste-skill GitHub source | Read style rules directly from GitHub: https://github.com/Leonxlnx/taste-skill/tree/main/skills |
mindrally/skills
giuseppe-trisciuoglio/developer-kit
syncfusion/react-ui-components-skills
supercent-io/skills-template
binjuhor/shadcn-lar