PROFESSION
设计师 Skills
Designer
视觉、交互与品牌设计人员
设计师 的 Skills 7778
dotnet-ui-app
Mandatory for all WinUI 3, Windows App SDK, and Avalonia UI work. Always use whenever a task creates, modifies, reviews, plans, designs, or troubleshoots a WinUI or Avalonia app; touches XAML UI, `.xaml`, `.axaml`, UI code-behind, controls, layout, navigation, windowing, styling, theming, accessibility, input, localization, responsiveness, or UI performance in those frameworks; sets up or checks a development environment; or asks to choose, build, run, package, or deploy a Windows desktop or cross-platform .NET UI app. Load `dotnet` first for C#/.NET project or CLI work, then use this skill for UI-specific guidance. Do not invoke for WPF, .NET MAUI, Uno Platform, or generic C# work unless the task also involves WinUI 3, Windows App SDK, Avalonia UI, or choosing among supported frameworks.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
architecture-design-contest
Generate multiple competing architecture designs for a feature, compare their trade-offs, and recommend or synthesize the best direction before implementation. Use this whenever the user wants architecture options, says "design it twice", asks for alternatives before coding, wants an RFC-level design review, or is unsure which approach to choose. Prefer this skill over jumping straight into implementation when the real need is exploring and comparing viable designs.
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
design-ui
Design systems, shadcn, accessibility, responsive design, Figma-to-code.
design-md
Author/validate/export Google's DESIGN.md token spec files.
claude-design
Design one-off HTML artifacts (landing, deck, prototype).
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
frontend-ui-engineering
Build production-quality React UIs in AS v2 (React 19 + Antd v5 + Tailwind). Use when creating components, implementing pages, managing client state, or modifying any user-facing interface.
frontend-ui-engineering
Build production-quality React UIs in AS v2 (React 19 + Antd v5 + Tailwind). Use when creating components, implementing pages, managing client state, or modifying any user-facing interface.
prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion, and page performance. Load with the core.
design-doc
Write an explicit design document, RFC, or consequential architecture proposal with adversarial review. Use for decisions with material ownership, compatibility, migration, or operational consequences. Do not activate for ordinary comparisons, syntax questions, or small implementation choices.
principle-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.