Loading...
Loading...
Found 71 Skills
The most important actions and content in a UI should be visually prominent — through size, colour, weight, and position. Visual hierarchy guides the user's eye to what matters most and signals which action is primary. Use when designing button groups, CTAs, dashboards, cards, or any layout where actions or content have different importance levels.
World-class color theory expertise combining the scientific precision of Josef Albers' "Interaction of Color," the systematic thinking of color systems from Pantone and RAL, and the perceptual psychology insights from researchers like Bevil Conway. Color is not just aesthetics - it's communication, emotion, and usability compressed into wavelengths. Great color work is invisible when done right. Users don't notice "nice colors" - they notice when they can't read text, when buttons don't look clickable, when errors don't feel urgent, or when the interface feels "off" without knowing why. Color theory is the science of making the right thing feel obvious. Use when "color theory, color palette, color scheme, color harmony, complementary colors, analogous colors, contrast ratio, dark mode colors, light mode, color tokens, semantic colors, color accessibility, color blindness, color psychology, color system, brand colors, data visualization colors, color, design, accessibility, contrast, dark-mode, theming, tokens, wcag, palette, harmony" mentioned.
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
Software design principles and patterns. This skill should be used when making architectural decisions, designing classes or modules, or evaluating code structure. Use proactively when discussing SOLID principles, coupling, cohesion, connascence, refactoring structure, class design, module boundaries, dependency injection, or the Four Rules of Simple Design. (user)
Apply principles of good design taste when creating, reviewing, or critiquing any creative or technical work. Use this skill whenever the user asks you to design something, review a design, create UI/UX, architect a system, write something with aesthetic intent, evaluate the quality of code or creative work, or asks for feedback on whether something is "good." Also trigger when users mention taste, aesthetics, beauty in design, elegance, simplicity, or when they want help making something not just functional but genuinely well-crafted. This skill applies across domains: software, writing, visual design, architecture, presentations, APIs, data models, and more. Even if the user doesn't explicitly mention "design," use this skill when the underlying task is about making something better, more elegant, or more refined.
Establish clear visual hierarchy through size, weight, color, spacing, and positioning.
Use when making UI/UX decisions, building components, choosing colors, layouts, typography, or reviewing any visual design — enforces anti-slop standards against generic AI aesthetics
Design judgment for any user interface work, including web apps, dashboards, landing pages, ecommerce, forms, mobile apps, redesigns and design reviews.
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
Audit the visual quality of a UI against established visual-design principles — hierarchy, emphasis, contrast, spacing, alignment, grouping, consistency, and depth. Produces a severity-rated issue list with concrete fixes. Specializes in catching overdesign, clutter, and competing focal points. Use when reviewing whether a screen looks professional, or as a validation step after generating UI.
Apply Robert C. Martin-inspired architecture rules when separating business policy from frameworks, databases, UI, or infrastructure details.