Design Claude Skills
2 394 design skills from 450 authors. They decide how things look — layout, type and interface behaviour. Half of them fit into 1 928 tokens or less — that is what one costs your context window when the agent loads it. 316 ship runnable scripts rather than instructions alone. 2 of them cannot work without an MCP server, most often rube. We also found 395 copies of these same skills sitting in other people's repositories — counted once here, not 395 times.
2 394 unique 450 authors 1 378 updated this month 195 from vendors
Plan and implement Next.js App Router routing for premium websites and apps. Use when working with app/ routes, pages, layouts, templates, loading, error, not-found files, route groups, dynamic segments, nested navigation, Link usage, or homepage structure in a Next.js project.
Use Radix Primitives for accessible custom React UI. Use for dialogs, dropdown menus, popovers, tooltips, tabs, accordions, switches, sliders, radio groups, checkboxes, select menus, navigation menus, focus management, keyboard interactions, and unstyled primitives that need premium custom styling.
Craft React component composition for websites and apps. Use when splitting large JSX files, creating reusable sections, primitives, slots, children-based composition, product UI components, portfolio sections, landing-page modules, design-system primitives, or maintainable component structure.
Build accessible React components for websites and apps. Use when creating buttons, links, menus, dialogs, tabs, accordions, carousels, forms, icon buttons, nav, skip links, focus states, keyboard behavior, ARIA, semantic markup, or reusable UI primitives.
Craft polished React components for websites and apps. Use for reusable sections, UI primitives, composition, props, state, responsive behavior, interaction states, accessibility, and avoiding monolithic or brittle frontend implementations.
Build responsive React components and sections for premium websites. Use when components need mobile, tablet, desktop, container-query, CSS-grid, flex, aspect-ratio, text-fit, overflow, media-crop, navigation, dashboard density, or responsive interaction behavior.
Design reduced-motion alternatives for websites and apps. Use for prefers-reduced-motion, Motion useReducedMotion, CSS media queries, disabling parallax, replacing large movement, simplifying scroll scenes, preserving state feedback, accessibility, vestibular-sensitive animation, and motion QA.
Design non-generic website section layouts. Use when a page needs alternatives to card grids, bento overuse, generic feature blocks, repetitive centered sections, bland stat strips, or template-like section sequencing.
Run responsive visual QA and polish for websites and apps. Use after building or editing any frontend to inspect desktop, laptop, tablet, and mobile widths; fix typography, spacing, overlaps, media crops, interactions, motion, forms, canvas rendering, accessibility, and final build quality.
Create token-driven Tailwind and CSS variable systems for premium websites. Use for color tokens, typography tokens, spacing rhythm, radius, shadows, gradients, surfaces, responsive constraints, dark/light modes, and avoiding random utility-class styling.
Design surface, shadow, border, material, radius, glass, elevation, overlay, divider, and depth systems for premium websites and apps. Use when cards, panels, modals, nav, product UI, dashboards, luxury sections, or editorial layouts need polished material hierarchy without generic glassmorphism or heavy shadows.
Build responsive Tailwind CSS layouts for premium websites and apps. Use for breakpoints, mobile-first layout, grids, flex, spacing, container widths, aspect ratios, responsive typography, media crops, nav adaptation, dashboard density, and preventing mobile stacking from looking generic.
Use shadcn/ui, Radix-style primitives, and lucide-react icons without producing generic default UI. Use for dialogs, menus, accordions, tabs, forms, buttons, toolbars, icons, inputs, and app controls that need accessibility and polished custom styling.
Compose UI screenshots inside website layouts. Use for product sections, feature blocks, app showcases, case studies, dashboards, mockup stacks, detail crops, callout overlays, annotation systems, responsive screenshot art direction, and avoiding generic SaaS screenshot-card sections.
Inspect, test, and refine frontend visual quality before delivery. Use after building or editing websites, landing pages, portfolios, dashboards, games, interactive tools, cinematic sites, luxury sites, or any UI where Codex should run a second polish pass for responsive layout, typography, spacing, hierarchy, motion, accessibility, and browser-rendered correctness.
Define vague website taste words as concrete design decisions. Use when prompts include premium, luxury, cinematic, modern, editorial, minimal, polished, brutalist, avant-garde, classy, clean, high-end, professional, Squarespace-like, Framer-like, or any subjective visual adjective that Codex must translate into layout, typography, color, media, and motion rules.
Create a website blueprint before coding. Use for new sites, redesigns, image-to-site work, premium landing pages, portfolios, brand sites, product sites, and any frontend project where Codex should define pages, sections, assets, tokens, layout, motion, and QA criteria before implementation.
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Use when designing UI, choosing palettes, typography, or component architecture.
UI/UX design intelligence. Use when user asks for UI/UX design, component architecture, layout, color system, or visual hierarchy decisions. Includes 50+ styles, 161 palettes, 57 font pairings.
| Trigger this skill when the user works on modern architecture design — 当代建筑设计 (concept → schematic → DD → CD → CA + sustainability / BIM / parametric / 中外双语 canon, 不含纯室内 / 景观 / 城市规划 / 结构 / MEP, 那些是相邻专业) problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「建筑设计」「建筑师」「建筑事务所」「设计院」「方案设计」
Beat Hintermann (Kantonsspital Baselland, Switzerland) 视角. 踝关节置换 (TAA) HINTEGRA 假体设计师 + 20 年长期 follow-up 数据 + Patient selection 派. 调用此 skill 时, 用 Hintermann 框架做终末期踝关节炎 / 置换 vs 融合 / 长期 follow-up 决策.
| 触发词：「figma 转 psd」「figma to psd」「figma 转 photoshop」「figma 导出 psd」「设计稿转换」
| 触发词：「game design」「game designer」「游戏设计」「游戏设计师」「我做游戏设计」
| Trigger this skill when the user works on 中国保险经纪人/代理人 (从业者视角) problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「保险经纪人」「保险代理人」「保单方案设计」「保险经纪 master」「中国保险 broker」
| Bret Taylor 视角. Sierra 联合创始人 / CEO, OpenAI 董事会主席 (2024-), ex-Salesforce co-CEO, Google Maps 联合创造者. B2B SaaS enterprise 派代表 / outcome-based pricing 第一手提倡者 / brand-as-moat 在 agent 时代重新阐述者. 把 monetize-agents 语境从 "卖软件 access" 换成 "卖 outcome — 客户问题解决一次收一次费", 把 product 设计从 "feature breadth" 换成 "vertical depth + measurable outcome + procurement-grade trust". enterprise 0 到 1 / vertical 还是 horizontal / design partner 怎么搭 / 一开始要不要融大钱" 类问题时, 用 Bret Taylor 视角先把 "outcome 可不可测量 + vertical 是哪个 + 第一批 design partner 是谁" 盘清楚, 再给定价 / GTM / 融资判断. 当用户提到 "Bret Taylor" "Sierra" "outcome-based pricing" "deflection" "vertical agent" "design partner" "enterprise agent" "B2B agent GTM" "agent 定价" "agent procurement" 时使用. 即使用户只是说 "用 Sierra 思路看一下" 也应触发.
| 触发词：「医美」「医疗美容」「注射美容」「微整」「轻医美」
| 触发词：「产品设计」「UX 设计」「用户体验」「用户体验设计」「交互设计」
| Trigger this skill when the user works on software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「软件架构」「系统设计」「system design」「应用架构」「service design」
| Trigger this skill when the user works on 研学旅行与营地教育（体验式教育新赛道，从业者 + 运营视角）— 中国 2016 年教育部《关于推进中小学生研学旅行的意见》政策驱动后形成的细分赛道，含 (a) 子赛道：自然教育 / 科技研学 / 红色研学（爱国主义+党史）/ 历史人文研学 / 国际游学营地 / 户外营地（夏令营·冬令营）；(b) 课程设计：项目制(PBL)·探究式·体验式学习设计、研学手册、学习目标与学科融合、课程评价；(c) 营地与基地运营：安全管理（师生比·应急预案·保险·食宿交通）、营期排期、辅导员(camp counselor)/研学导师排班、基地/营地建设与等级认定；(d) 政策合规：教育部研学旅行政策、研学实践教育基地/营地认定、营地与户外教育团体标准、双减后校外培训监管边界；(e) 商业模式：B 端（学校集采·教育局采购·公立校综合实践课时）、C 端（家庭付费夏令营·亲子）、渠道分销（旅行社·机构代理）、获客与履约。核心矛盾：教育属性 vs 旅游属性、安全 vs 体验、标准化课程 vs 在地化资源。不含：纯 K12 学科培训 / 留学中介 / 纯旅行社跟团 / 学校内 STEAM 硬件采购。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「研学」「研学旅行」「营地教育」「研学营地」「自然教育」
| Andrew von Nagy 视角 — 高密度 Wi-Fi 工程的容量优先设计学派代表 (Revolution Wi-Fi 博客, ex-Target Senior Wireless Architect, 现 Nile Principal Architect, CCIE-Wireless + CWNE). 加载后让 AI 用「capacity-first」「retry-rate-over-RSSI」「predictive-must-validate」「client-is-weakest-link」「spectrum-is-shared」五大镜片诊断企业 Wi-Fi 问题, 特别是高密度场景 (≥30 客户端共享区域, 典型 80 人办公室).
Builds distinctive, production-grade UIs that avoid generic AI aesthetics. Use whenever the user wants to build, restyle, or give visual direction to any interface — pages, dashboards, landing pages, components, onboarding flows, mobile screens, or design systems — even without an explicit 'design' request. Also triggers for: picking an aesthetic direction, improving the look of a dull/generic existing page, adding visual personality, or choosing colors/typography. Includes a bundled design intelligence database for concrete guidance across web (React, Next.js, Vue, Tailwind) and mobile (React Native, Flutter, SwiftUI).
Specialized visual and multimedia processing tools. Use this skill whenever a task involves complex visual content — UI mockups, dense screenshots, design images, charts, artwork — where precise details like spacing, hex colors, font sizes, and component hierarchy need to be extracted accurately. Also use for: reviewing or auditing existing UI against designs, comparing screenshots for visual regressions, transcribing audio/video, extracting data from PDFs with complex layouts, and generating images. Trigger whenever the user wants to implement from a design, review or compare UI screenshots, analyze visual details precisely, describe artwork or aesthetic content, or process any media file (audio, video, PDF).
Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps.
Codebase intelligence for TypeScript and JavaScript. Static analysis of code and styles reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security candidates. Runtime coverage can merge production execution data for hot-path review, cold-path deletion confidence, and stale-flag evidence. 123 framework plugins, zero configuration, sub-second static analysis. Use when asked to audit PR risk, find unused code or dependencies, detect duplicates, check styling consistency, inspect architecture boundaries, merge runtime coverage, auto-fix supported issues, or run fallow.
Design understandable and accessible product interactions. Use when shaping workflows, information architecture, navigation, interface copy, forms, controls, empty states, onboarding, feedback, error recovery, progressive disclosure, discoverability, accessibility, trust, group dynamics, or interaction edge cases. Use lamina-product-behavior for authoritative state rules and lamina-evaluation to judge a built product.
Guide for working with Next.js App Router (Next.js 13+). Use when migrating from Pages Router to App Router, creating layouts, implementing routing, handling metadata, or building Next.js 13+ applications. Activates for App Router migration, layout creation, routing patterns, or Next.js 13+ development tasks.
Run comprehensive accessibility audit (WCAG 2.1) on Webflow pages - checks buttons, forms, links, focus states, headings, keyboard navigation, and generates detailed reports with fixes. Runs entirely headlessly against a page ID — no Designer connection required. Excludes image alt text (covered by asset-audit skill).
Generate new Webflow Code Component boilerplate with React component, definition file, and optional styling. Automatically checks prerequisites and can set up missing config/dependencies.
Build and manage pages, elements, components, and styles in Webflow Designer. Use when adding sections, creating layouts, building elements, inspecting or updating components, viewing what's inside a component, restructuring pages, creating new pages, previewing page structure, styling elements, or managing component properties. Building, styling, and inspecting run headlessly against an explicit page ID — no Designer connection needed. Designer is required for `designer_tool` actions (reading/switching the page open on canvas, interactively selecting an element, creating page folders, opening a component's canvas view) and for `element_snapshot_tool` visual previews.
>- Build a Webflow page, section, component, or full site from a Figma design using the Figma MCP and the Webflow MCP (Designer Bridge + Data API). Use whenever translating a Figma file/frame into Webflow, building directly in a Webflow project, or implementing a design as live Webflow elements/styles "Figma to Webflow", "implement this design in Webflow", a figma.com URL + a Webflow site, "recreate this in my Webflow project".
Apply Flowkit CSS naming system in Webflow. Use when creating classes, auditing existing naming, or building new components following Flowkit conventions. Flowkit is Webflow's official CSS framework with utility-first approach. Runs headlessly against a page ID — no Designer connection required, except for the optional live-canvas conveniences (current page, interactive element selection).
Initialize a new Webflow Code Components project from scratch. Creates project structure, installs dependencies, configures webflow.json, and sets up development environment.
Pre-deployment validation for Webflow Code Components. Checks bundle size, dependencies, prop configurations, SSR compatibility, styling setup, and common issues before running webflow library share.
Use when creating, redesigning, or reviewing web interfaces that need product-specific structure, clear hierarchy, responsive composition, accessible interaction, or relief from generic AI-generated SaaS aesthetics. Adapt grid, typography, imagery, motion, and product evidence to the established brand—including technical, editorial, image-led, warm, playful, and utilitarian directions—across React, Next.js, Tailwind CSS, HTML/CSS, landing pages, dashboards, documentation, portfolios, and interactive tools.
Use when building or modifying UI with the Dile Components library (@dile/ui, @dile/crud, @dile/editor, @dile/utils, @dile/lib, @dile/iconlib, @dile/icons) — a framework-agnostic, Lit-based web component catalog. Trigger when installing/importing dile-* custom elements, using tags like <dile-input>, <dile-modal>, <dile-table>, building CRUD screens, adding a WYSIWYG/Markdown editor, using icon components, or theming with Dile's CSS custom properties.
Complete visual content system for Claude Code. Default aesthetic - light backgrounds, teal/burnt orange accents, hand-drawn sketch style.
Extract comprehensive site specifications from simple descriptions. Use when analyzing a user's theme request to determine site type, audience, tone, layout requirements, and typography.
Extract comprehensive site specifications from simple descriptions. Use when analyzing a user's theme request to determine site type, audience, tone, layout requirements, and typography.