Loading...
Loading...
Found 595 Skills
Build and maintain design systems. Use when creating component libraries, design tokens, or style guides. Covers atomic design and tokens.
Casper Studios internal design system for generating consistent, production-grade SaaS UI. Use this skill whenever generating UI code for internal tools, client apps, dashboards, POCs, prototypes, or any visual interface — even quick mockups or artifacts. Apply it any time the output is a React component, page, or layout. If the user mentions "our design system", "Casper style", "match our look", or asks you to build any kind of app or interface, use this skill. Also trigger when restyling or theming existing UI to match Casper's visual language. This skill takes priority over generic frontend-design guidance.
Generate design systems and theme variations. Creates cohesive visual systems with color schemes, typography, and component styling.
Create a complete, actionable design system for any project (website, app, product) grounded in physical/sensory anchoring rather than design trends. Delivers CSS tokens, typography scale, component patterns, accessibility checklist, and absolute rules as a single developer-ready markdown document. Use this skill whenever the user asks to create a design system, theme, color palette, visual identity, CSS tokens, theme variables, or propose an art direction. Also triggers on "style guide", "site colors", "choose fonts", "look and feel", "visual branding", "charte graphique", "identite visuelle", "direction artistique", "refonte visuelle", or any new project where design isn't yet defined — propose this skill proactively.
Build or audit a design system including component library, design tokens, naming conventions, contribution model, and documentation. Use this skill whenever the user wants to build a design system, audit an existing system, define design tokens at the system level, structure a component library, or set up design system governance. Triggers on design system, component library, design tokens, atomic design, atoms, molecules, organisms, design system documentation, Storybook, Figma library, system governance, design contribution model. Also triggers when teams are inconsistent across products and a system is the answer.
Community skill for applying the Geist design system to Vercel-inspired UI across React, Next.js, Vite, Astro, Svelte, Vue, HTML/CSS, Tailwind, shadcn, and Radix surfaces. Use it for typography, spacing, color tokens, material treatment, component styling, app shells, dashboards, forms, tables, dialogs, empty/loading/error states, responsive layouts, and UI polish. This is a community-authored skill, not an official Vercel skill. Trigger when the user asks for Geist, Vercel-style UI, or generic clean, modern, premium, beautiful, polished SaaS/developer-product visual design where no other final visual system, brand direction, or art direction is requested. Do not trigger for non-visual frontend work such as bug fixes, data wiring, analytics, tests, build tooling, API/state changes, or behavior-only accessibility fixes unless the task also creates or materially changes rendered UI.
World-class design systems architecture - tokens, components, documentation, and governance. Design systems create the shared language between design and engineering that makes products feel cohesive at any scale. Use when "design system, component library, design tokens, atomic design, style guide, theme, theming, design scale, component api, variant, figma tokens, style dictionary, design-system, tokens, components, theming, documentation, figma, accessibility, versioning" mentioned.
Design system principles, component libraries, typography, color theory, spacing systems, and design tokens
Collaborative design system creation using Atomic Design methodology. Produces a specification artifact with philosophy, tokens, and component hierarchy. Activate when creating a design system, defining visual language, specifying UI tokens, or planning component architecture before implementation begins.
Usage guidelines for the PIE design system by Just Eat Takeaway. Use when building, modifying, debugging any user-facing web UI, referencing @justeattakeaway/pie-* packages or when the user asks for a UI that should follow JET/PIE design standards.
Initialize the design system or create new UI components with accessibility, Tailwind/shadcn integration, and documentation. Use when setting up the initial design system, adding component categories, or creating complex UI components that need design review.
Design System — Generate & Audit Visual Systems