Loading...
Loading...
Found 595 Skills
Enforces design token usage, component reusability, SOLID, and DRY principles when writing or editing React/Next.js frontend code. Use when creating components, pages, or modifying UI code in a project that has a design-tokens.json file.
Design engineering skill for Claude Code that enforces consistent UI patterns through memory, craft principles, and systematic design tokens.
Guide for using Sentry's layout and text primitives. Use when implementing UI components, layouts, or typography. Enforces use of core components over styled components.
Integrate and implement apps and screens using gts-central-library tokens, styles, and components. Use when adding the design system to Vite, Next.js, Lovable, or React apps; migrating from shadcn or parallel token systems; setting up Tailwind v4 with GTS css; implementing configurator-style layouts; or troubleshooting token/theme/style mismatches.
Design System Governance Workflow for auditing, refactoring, and syncing enterprise design systems, design tokens, Figma variables, and developer handoff outputs.
Sync design system components between Figma and code using Code Connect mappings
Create adoption strategies and materials to drive design system usage across teams.
Build UIs using IBM's Carbon Design System. Use when the user requests Carbon-styled interfaces, IBM-style dashboards, enterprise UIs following Carbon conventions, or explicitly mentions Carbon, IBM design, or @carbon/react. Covers component usage, design tokens (color, typography, spacing, motion), theming (White, Gray 10, Gray 90, Gray 100), grid layout, and accessibility. Supports both artifact/HTML output (CDN-based) and full React project output (@carbon/react). Triggers include "Carbon", "IBM design system", "enterprise dashboard", "@carbon/react", "carbon components", or requests for IBM-style professional interfaces.
Clinic-architecture-aligned iOS design system engineering for SwiftUI (iOS 26 / Swift 6.2) covering token architecture, color/typography/spacing systems, component style libraries, asset governance, and theming. Enforces @Equatable on views and keeps design-system usage compatible with Feature-to-Domain+DesignSystem boundaries. Use when building or refactoring DesignSystem infrastructure for the clinic modular MVVM-C stack.
Generate project-specific design system rules for Figma-to-code workflows. Useful for capturing tokens, naming, and lint rules in one source.
Use this skill to scaffold new Expo / React Native design system components that obey the expo-design-system rules by construction — a variant-driven pressable primitive, a slot-based card surface, a typed text primitive, a labeled form field, a FlashList entity screen, a theme token group, and a Storybook variant catalog. Trigger whenever the user wants to create, add, generate, or scaffold a new shared UI component, primitive, design token group, or screen for the clinic mobile app, even if they don't mention the design system — the generated code uses Unistyles v3 variants instead of style props, ref-as-prop, design tokens, built-in accessibility, and web/iOS parity (`_web` hover/focus/cursor on interactive primitives), so it follows expo-design-system without rework. Output is TSX/TS using react-native-unistyles.
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 on generic visual direction such as clean, modern, premium, beautiful, polished, SaaS, developer tool, product UI, app shell, navigation, data views, and marketing sections. Skip only when the user explicitly names a non-Geist final visual system/art direction as the final visual authority, supplies a non-Geist design artifact as the final visual authority, or asks for game/illustrative output where Geist UI is not the requested surface.