ui-design▌
shajith003/awesome-claude-skills · updated Apr 8, 2026
Only code in HTML/Tailwind in a single code block.
- ›Any CSS styles should be in the style attribute.
- ›Start with a response, then code and finish with a response.
- ›Don't mention about tokens, Tailwind or HTML.
- ›Always include the html, head and body tags.
- ›Use lucide icons for javascript, 1.5 strokewidth.
- ›Unless style is specified by user, design in the style of Linear, Stripe, Vercel, Tailwind UI (IMPORTANT: don't mention names).
- ›Checkboxes, sliders, dropdowns, toggles should be custom (don't add, o
Only code in HTML/Tailwind in a single code block. Any CSS styles should be in the style attribute. Start with a response, then code and finish with a response. Don't mention about tokens, Tailwind or HTML. Always include the html, head and body tags. Use lucide icons for javascript, 1.5 strokewidth. Unless style is specified by user, design in the style of Linear, Stripe, Vercel, Tailwind UI (IMPORTANT: don't mention names). Checkboxes, sliders, dropdowns, toggles should be custom (don't add, only include if part of the UI). Be extremely accurate with fonts. For font weight, use one level thinner: for example, Bold should be Semibold. Titles above 20px should use tracking-tight. Make it responsive. Avoid setting tailwind config or css classes, use tailwind directly in html tags. If there are charts, use chart.js for charts (avoid bug: if your canvas is on the same level as other nodes: h2 p canvas div = infinite grows. h2 p div>canvas div = as intended.). Add subtle dividers and outlines where appropriate. Don't put tailwind classes in the html tag, put them in the body tags. If no images are specified, use these Unsplash images like faces, 3d, render, etc. Be creative with fonts, layouts, be extremely detailed and make it functional. If design, code or html is provided, IMPORTANT: respect the original design, fonts, colors, style as much as possible. Don't use javascript for animations, use tailwind instead. Add hover color and outline interactions. For tech, cool, futuristic, favor dark mode unless specified otherwise. For modern, traditional, professional, business, favor light mode unless specified otherwise. Use 1.5 strokewidth for lucide icons and avoid gradient containers for icons. Use subtle contrast. For logos, use letters only with tight tracking. Avoid a bottom right floating DOWNLOAD button.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★30 reviews- ★★★★★Shikha Mishra· Dec 20, 2024
ui-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 16, 2024
I recommend ui-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Emma Garcia· Dec 16, 2024
Keeps context tight: ui-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yash Thakker· Nov 11, 2024
Keeps context tight: ui-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Soo Robinson· Nov 7, 2024
ui-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Agarwal· Nov 3, 2024
ui-design reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Omar Bansal· Oct 26, 2024
ui-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Soo Thompson· Oct 22, 2024
I recommend ui-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Oct 2, 2024
Registry listing for ui-design matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Rahul Santra· Sep 9, 2024
Useful defaults in ui-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 30