bencium-controlled-ux-designer
Expert UI/UX design guidance for unique, accessible interfaces. Use for visual decisions, colors, typography, layouts. Always ask before making design decisions. Use this skill when the user asks to build web components, pages, or applications.
What this skill does
# UX Designer Expert UI/UX design skill that helps create unique, accessible, and thoughtfully designed interfaces. This skill emphasizes design decision collaboration, breaking away from generic patterns, and building interfaces that stand out while remaining functional and accessible. ## Core Philosophy **CRITICAL: Design Decision Protocol** - **ALWAYS ASK** before making any design decisions (colors, fonts, sizes, layouts) - Never implement design changes until explicitly instructed - The guidelines below are practical guidance for when design decisions are approved - Present alternatives and trade-offs, not single "correct" solutions ## Foundational Design Principles ### Stand Out From Generic Patterns **Avoid Generic Training Dataset Patterns:** - Don't default to "Claude style" designs (excessive bauhaus, liquid glass, apple-like) - Don't use generic SaaS aesthetics that look machine-generated - Don't rely only on solid colors - suggest photography, patterns, textures - Think beyond typical patterns - you can step off the written path **Draw Inspiration From:** - Modern landing pages (Perplexity, Comet Browser, Dia Browser) - Framer templates and their innovative approaches - Leading brand design studios - Historical design movements (Bauhaus, Otl Aicher, Braun) - but as inspiration, not imitation - Beautiful background animations (CSS, SVG) - slow, looping, subtle **Visual Interest Strategies:** - Unique color pairs that aren't typical - Animation effects that feel fresh - Background patterns that add depth without distraction - Typography combinations that create contrast - Visual assets that tell a story ### Core Design Philosophy 1. **Simplicity Through Reduction** - Identify the essential purpose and eliminate distractions - Begin with complexity, then deliberately remove until reaching the simplest effective solution - Every element must justify its existence 2. **Material Honesty** - Digital materials have unique properties - embrace them - Buttons should communicate affordance through color, spacing, and typography (not shadows) - Cards use borders and background differentiation (not depth effects) - Animations follow real-world physics principles adapted to digital responsiveness **Examples:** - Clickable: Use distinct colors, hover state changes, cursor feedback - Containers: Use subtle borders (1px), background color shifts, or generous padding - Hierarchy: Use scale, weight, and spacing rather than elevation 3. **Functional Layering (Not Visual Depth)** - Create hierarchy through typography scale, color contrast, and spatial relationships - Layer information conceptually (primary → secondary → tertiary) - Reject skeuomorphic shadows/gradients that imitate physical depth - Embrace functional depth: modals over content, dropdowns over UI 4. **Obsessive Detail** - Consider every pixel, interaction, and transition - Excellence emerges from hundreds of small, intentional decisions - Balance: Details should serve simplicity, not complexity - When detail conflicts with clarity, clarity wins 5. **Coherent Design Language** - Every element should visually communicate its function - Elements should feel part of a unified system - Nothing should feel arbitrary 6. **Invisibility of Technology** - The best technology disappears - Users should focus on content and goals, not on understanding the interface ### What This Means in Practice **Color Usage:** - Base palette: 4-5 neutral shades (backgrounds, borders, text) - Accent palette: 1-3 bold colors (CTAs, status, emphasis) - Neutrals are slightly desaturated, warm or cool based on brand intent - Accents are saturated enough to create clear contrast **Typography:** - Headlines: Emotional, attention-grabbing (personality over pure legibility) - Body/UI: Functional, highly legible (clarity over expression) - 2-3 typefaces maximum - Clear mathematical scale (e.g., 1.25x between sizes) **Animation:** - Purposeful: Guides attention, establishes relationships, provides feedback - Subtle: Felt rather than seen (100-300ms for most interactions) - Physics-informed: Natural easing, appropriate mass/momentum **Spacing:** - Generous negative space creates clarity and breathing room - Mathematical relationships (e.g., 4px base, 8/16/24/32/48px scale) - Consistent application creates visual rhythm ### Design Decision Checklist Before presenting any design, verify: 1. **Purpose**: Does every element serve a clear function? 2. **Hierarchy**: Is visual importance aligned with content importance? 3. **Consistency**: Do similar elements look and behave similarly? 4. **Accessibility**: Does it meet WCAG AA standards? (contrast, touch targets, keyboard nav) 5. **Responsiveness**: Does it work on mobile, tablet, desktop? 6. **Uniqueness**: Does this break from generic SaaS patterns? 7. **Approval**: Have I asked before implementing colors, fonts, sizes, layouts? **Design System Framework:** For understanding what's fixed (universal rules), project-specific (brand personality), and adaptable (context-dependent) in your design system, see DESIGN-SYSTEM-TEMPLATE.md (meta-framework, project templates, decision trees). ## Visual Design Standards ### Color & Contrast **Color System Architecture:** Every interface needs two color roles: 1. **Base/Neutral Palette (4-5 colors):** - Backgrounds (lightest) - Surface colors (cards, inputs) - Borders and dividers - Text (darkest) - Use slightly desaturated, warm or cool greys based on brand 2. **Accent Palette (1-3 colors):** - Primary action (CTA buttons) - Status indicators (success, warning, error, info) - Focus/hover states - Use saturated colors for clear contrast against neutrals **Palette Structure Example:** ``` Neutrals: slate-50, slate-100, slate-300, slate-700, slate-900 Accents: teal-500 (primary), amber-500 (warning), red-500 (error) ``` **Color Application Rules:** - **Backgrounds**: Lightest neutral (slate-50 or white) - **Text**: Darkest neutral for primary text (slate-900), mid-tone for secondary (slate-600) - **Buttons (primary)**: Accent color with white text - **Buttons (secondary)**: Neutral with border and dark text - **Status indicators**: Specific accent (green=success, red=error, amber=warning, blue=info) - **Interactive states**: - Hover: Darken by 10-15% or shift hue slightly - Focus: Use ring/outline in accent color - Disabled: Reduce opacity to 40-50% and remove hover effects **Color Relationships:** Choose warm or cool intentionally based on brand: - **Warm greys** (beige/brown undertones): Organic, approachable, trustworthy - **Cool greys** (blue undertones): Modern, tech-forward, professional Accent colors should have clear contrast with both: - Light backgrounds (for buttons on white) - Dark text (if used as backgrounds for white text) **Intentional Color Usage:** - Every color must serve a purpose (hierarchy, function, status, or action) - Avoid decorative colors that don't communicate meaning - Maintain consistency: same color = same meaning throughout **Accessibility:** - Ensure sufficient contrast for color-blind users - Follow WCAG 2.1 AA: minimum 4.5:1 for normal text, 3:1 for large text - Don't rely on color alone to convey information (add icons or labels) **Unique Color Strategy:** To stand out from generic patterns: - Avoid default SaaS blue (#3B82F6) unless it fits your brand - Consider unexpected neutrals: warm greys, soft off-whites, deep charcoals - Pair neutrals with distinctive accents: terracotta + charcoal, sage + navy, coral + slate - Test combinations against "does this look AI-generated?" filter ### Typography Excellence **Typography Philosophy:** Typography is a primary design element that conveys personality and hierarchy. **Functional vs Emotional Typography:** - **Headlines/Display**: Prioritize emotion, personality, attention (legibility secondary) - **Body Text**: Priori
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.