Loading...
Loading...
Found 2,498 Skills
Builds sites, pages and components from Lucian UX/UI Prompt (lucianlabs.dev/uxui-prompt), a growing library of polished, dependency-free interactive UI elements with light and dark themes, keyboard and touch support and reduced motion. It covers buttons, toggles, inputs, menus and tabs, cards, sign-in and sign-up, toasts, loaders, empty and error states, charts, and app-level tools like editors, dashboards, schedulers and kanban boards. Searches the library, fetches only the chosen elements and ports them into the project's framework and theme. Use when the user names lucian-uxui, Lucian UX/UI or lucianlabs elements, or asks to build UI that should use them, e.g. "build a landing page with lucian-uxui", "lucian-uxui 스킬로 사이트 만들어줘", "루샨 UX/UI 요소로 로그인 화면 만들어줘". Not for backend work or for editing the library itself.
Use when asked to explain visually with section clips
Improve how interfaces use photos, screenshots, icons, illustrations, and user-uploaded media so visuals support clarity instead of undermining it. Use when the user mentions images, screenshots, background photos, hero images, icon sizing, user-uploaded media, crops, overlays, or image readability.
Extract reusable components, product patterns, and design tokens into a clearer design system with shared APIs, documented defaults, and better reuse. Use when the user wants to refactor repeated UI, consolidate buttons/cards/forms/sections, build a component library, or turn one-off values into reusable tokens.
Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.
Generate 5 distinct, production-grade UI variations for a requested new or existing section, component, page, flow, or shell, then help the user preview and apply one. Use when the user asks to add or redesign UI like a hero, pricing, navbar, auth flow, dashboard shell, ecommerce surface, or data component.
Add or refine depth through elevation systems, raised and inset surfaces, layered overlap, and meaningful shadow behavior so interfaces feel structured instead of flat. Use when the user mentions depth, elevation, shadows, layering, flat cards, pressed states, drag feedback, or inset controls.
Increase visual impact, contrast, personality, and compositional confidence when a design feels bland, generic, or too safe. Use when the design needs more energy, confidence, or memorability—not when the real problem is clutter, over-intensity, or micro-detail polish.
ALWAYS use when writing code that imports "vue-router", "vue-router/vite", "vue-router/auto-routes", or "vue-router/experimental". Consult for debugging, best practices, or modifying vue-router, vue router, router, file-based routing, typed routes, data loaders.
React Best Practices codifies 40+ rules across 8 priority categories, from Critical (eliminating waterfalls, reducing bundle size) to Low-Medium (JavaScript micro-optimizations).
Create Astro components, pages, and layouts with accessible markup and minimal client-side JavaScript.
Dynamic path segments ($paramName), splat routes ($ / _splat), optional params ({-$paramName}), prefix/suffix patterns ({$param}.ext), useParams, params.parse/stringify, pathParamsAllowedCharacters, i18n locale patterns.