Agent skill

Bencium Controlled UX Designer

by bencium in bencium/bencium-marketplace

Expert UI/UX design guidance for unique, accessible interfaces.

MITAuto-check passedFrontend & Design

Install Bencium Controlled UX Designer

skills CLI
$ npx skills add bencium/bencium-marketplace --skill bencium-controlled-ux-designer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bencium/bencium-marketplace bencium-controlled-ux-designer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/bencium-controlled-ux-designer/skills/bencium-controlled-ux-designer .claude/skills/bencium-controlled-ux-designer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bencium-controlled-ux-designer
GitHub stars
446
Token cost
~6.8k tokens
SKILL.md length
2,871 words
Files
5
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Expert UI/UX design guidance for unique, accessible interfaces.

  • Works in 6 steps: Simplicity Through Reduction → Material Honesty → Functional Layering (Not Visual Depth) → …
  • Visual decisions
  • SKILL.md covers Core Philosophy, Foundational Design Principles, Visual Design Standards and Interaction Design, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Bencium Controlled UX Designer is an agent skill from bencium/bencium-marketplace. 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.

Its SKILL.md is about 6.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `ACCESSIBILITY.md`, `DESIGN-SYSTEM-TEMPLATE.md` and `MOTION-SPEC.md`).

It sits in Frontend & Design, covering Architecture decision records, UI design and Typography. The repository describes itself as: comprehensive skills based on the Anthropic Skills guide and our design and development philosophy. The licence is MIT.

When your agent uses it

  • Visual decisions
  • The user asks to build web components

Example prompts

  • “/bencium-controlled-ux-designer”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Simplicity Through Reduction
  2. Material Honesty
  3. Functional Layering (Not Visual Depth)
  4. Obsessive Detail
  5. Coherent Design Language
  6. Invisibility of Technology

What it can do on your machine

Read from SKILL.md and the folder at commit 5de46a3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • w3.org
    • fonts.google.com
    • tailwindcss.com
    • ui.shadcn.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bencium Controlled UX Designer loads about 6.8k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 2,871 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~6.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bencium/bencium-marketplace at commit 5de46a3, republished under its MIT licence (© bencium). 2,871 words, ~6,796 tokens.

Download SKILL.mdSave it as .claude/skills/bencium-controlled-ux-designer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
bencium-controlled-ux-designer
description
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.
metadata.version
1.0.0

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: Prioritize legibility, reading comfort, accessibility
  • UI/Labels: Prioritize clarity, scannability, consistency

Font Selection:

  • Use 2-3 typefaces maximum
  • Limit to 3 weights per typeface (e.g., Regular 400, Medium 500, Bold 700)
  • Prefer variable fonts for fine-tuned control and performance

Font Version Usage:

  • Display version: Headlines and hero text only
  • Text version: Paragraphs and long-form content
  • Caption/Micro: Small UI labels (1-2 lines, non-critical info)

Recommended Sources:

  • Google Fonts for web (free, well-optimized, reliable)
  • System fonts for performance-critical apps (-apple-system, BlinkMacSystemFont, Segoe UI)
  • Choose fonts that serve your brand's purpose (not "trending" lists)

Typographic Scale:

Use mathematical relationships for size hierarchy:

  • Ratio: Major third (1.25x) for moderate contrast, Perfect fourth (1.333x) for dramatic
  • Base size: 16px (1rem) for body text
  • Example scale (1.25x):
    xs:   0.64rem (10px)
    sm:   0.8rem  (13px)
    base: 1rem    (16px)
    lg:   1.25rem (20px)
    xl:   1.563rem (25px)
    2xl:  1.953rem (31px)
    3xl:  2.441rem (39px)
    4xl:  3.052rem (49px)
    5xl:  3.815rem (61px)

Typographic Hierarchy:

  • Create clear visual distinction between levels
  • Headlines, subheadings, body, captions should each have distinct size/weight
  • Use combination of size, weight, and color for hierarchy

Spacing & Readability:

  • Line height: 1.5x font size for body text (e.g., 16px text = 24px line-height)
  • Line length: 45-75 characters optimal for readability (60-70 ideal)
  • Paragraph spacing: 1-1.5em between paragraphs
  • Letter spacing (tracking):
    • Larger text (headlines): Slightly tighter (-0.02em to -0.05em)
    • Normal text (body): Default (0)
    • Small text (captions): Slightly looser (+0.01em to +0.03em)
    • General rule: As size increases, reduce tracking; as size decreases, increase tracking

Font Pairing Logic:

When using multiple typefaces, create contrast through:

  • Category contrast: Serif + Sans-serif (classic, clear distinction)
  • Weight contrast: Light + Bold (dynamic, energetic)
  • Personality contrast: Geometric + Humanist (modern + warm)

Examples:

  • Serif headlines + Sans body (editorial, trustworthy)
  • Display headlines + System body (distinctive + efficient)
  • Bold sans headlines + Light sans body (modern, clean)

UI Typography:

Specific guidance for interface elements:

  • Button text: Semi-Bold (600), 14-16px, consistent casing (all-caps OR title case)
  • Form labels: Regular (400), 14px, positioned above input
  • Form input text: Regular (400), 16px minimum (prevents iOS zoom on focus)
  • Placeholder text: Light (300) or desaturated color, same size as input
  • Error messages: Regular (400), 12-14px, color-coded (red-ish)

Responsive Typography:

Scale type sizes across breakpoints:

tsx
// Example with Tailwind
<h1 className="text-3xl md:text-4xl lg:text-5xl">
  Responsive Headline
</h1>

// Or with CSS clamp (fluid)
h1 {
  font-size: clamp(2rem, 5vw, 4rem);
}

Reduce sizes on mobile (20-30% smaller than desktop) Reduce hierarchy levels on small screens (fewer distinct sizes)

Layout & Spatial Design

Compositional Balance:

  • Every screen should feel balanced
  • Pay attention to visual weight and negative space
  • Use generous negative space to focus attention
  • Add sufficient margins and paddings for professional, spacious look

Grid Discipline:

  • Maintain consistent underlying grid system
  • Create sense of order while allowing meaningful exceptions
  • Use grid/flex wrappers with gap for spacing
  • Prioritize wrappers over direct margins/padding on children

Spatial Relationships:

  • Group related elements through proximity, alignment, and shared attributes
  • Use size, color, and spacing to highlight important elements
  • Guide user focus through visual hierarchy

Attention Guidance:

  • Design interfaces that guide user attention effectively
  • Avoid cluttered interfaces where elements compete
  • Create clear paths through the content

Interaction Design

Motion & Animation

Purposeful Animation:

Every animation must serve a functional purpose:

  • Orient users: Smooth transitions during navigation changes
  • Establish relationships: Show how elements connect (expand from source, slide between states)
  • Provide feedback: Confirm interactions (button press, form submission)
  • Guide attention: Direct focus to important changes (new messages, errors)

Animation & Gestalt Principles:

Motion should reinforce visual relationships:

  • Proximity: Elements near each other move together (grouped cards animating)
  • Similarity: Similar elements animate similarly (all buttons have same hover timing)
  • Continuity: Movement follows natural paths (smooth curves, not jumpy angles)
  • Figure-ground: Important elements animate while backgrounds stay stable

Natural Physics:

Animations should feel organic, not mechanical:

  • Easing: Use ease-out for entrances (fast start, slow end)
  • Easing: Use ease-in for exits (slow start, fast end)
  • Easing: Use ease-in-out for transitions (smooth both ends)
  • Avoid linear easing (feels robotic) except for continuous loops
  • Apply appropriate mass/momentum (lightweight UI vs weighty modals)

Subtle Restraint:

  • Animations should be felt rather than seen
  • Don't delay user actions unnecessarily (keep under 300ms for interactive feedback)
  • Never block critical actions with decorative animations
  • Respect prefers-reduced-motion media query

Timing Guidelines:

  • Micro-interactions (button press, checkbox toggle): 100-150ms
  • State changes (expanding accordion, tab switch): 200-300ms
  • Page transitions (route changes, modal open/close): 300-500ms
  • Attention-directing (notification appearance, error highlight): 200-400ms

Physics Profiles:

Define consistent durations for element types:

  • Lightweight (icons, small UI): 150ms
  • Standard (cards, panels): 300ms
  • Weighty (modals, page transitions): 500ms

Performance Optimization:

  • Animate transform and opacity only (GPU-accelerated, smooth 60fps)
  • Avoid animating width, height, top, left, margin (causes reflow/repaint)
  • Use will-change sparingly for complex animations (pre-allocates GPU resources)
  • Test on low-end devices (60fps on powerful hardware ≠ 60fps on mobile)

Implementation:

  • Use framer-motion sparingly and purposefully
  • Prefer CSS animations over JavaScript when possible (better performance)
  • Use CSS transitions for simple hover/focus states
  • Implement @media (prefers-reduced-motion: reduce) to disable/reduce animations

Example:

tsx
// Simple hover transition
<button className="
  transition-colors duration-200 ease-out
  bg-blue-600 hover:bg-blue-700
">
  Click me
</button>

// Framer Motion for complex interaction
<motion.div
  initial={{ opacity: 0, y: 20 }}
  animate={{ opacity: 1, y: 0 }}
  exit={{ opacity: 0, y: -20 }}
  transition={{ duration: 0.3, ease: "easeOut" }}
>
  Content
</motion.div>

Motion Specification:

For detailed motion specs, see MOTION-SPEC.md (easing curves, duration tables, state-specific animations, implementation patterns).

Show full SKILL.md (1,156 more words)Show less
User Experience Patterns

Core UX Principles:

  1. Direct Manipulation

    • Users interact directly with content, not through abstract controls
    • Examples:
      • Drag & drop to reorder items (not up/down buttons)
      • Inline editing (click to edit, not separate form)
      • Sliders for ranges (not numeric input with +/-)
      • Pinch/zoom gestures on mobile (not +/- buttons)
  2. Immediate Feedback

    • Every interaction provides instantaneous visual feedback (within 100ms)
    • Types of feedback:
      • Visual: Button pressed state, hover effects, color changes
      • Haptic: Vibration on mobile (submit, error, success)
      • Audio: Subtle sounds for critical actions (optional, user-controlled)
      • Loading: Skeleton screens, spinners for >300ms operations
      • Success: Checkmarks, green highlights, toast notifications
      • Error: Red highlights, inline error messages, shake animations
  3. Consistent Behavior

    • Similar-looking elements behave similarly
    • Examples:
      • Visual consistency: All primary buttons have same colors, sizes, hover states
      • Behavioral consistency: All modals close via X button, ESC key, and outside click
      • Interaction consistency: All drag targets have same hover state and drop feedback
      • Pattern consistency: All forms validate on blur and submit
  4. Forgiveness

    • Make errors difficult, but recovery easy
    • Prevention strategies:
      • Disable invalid actions (grey out unavailable buttons)
      • Validate inputs inline (before submission)
      • Confirm destructive actions (delete, overwrite)
      • Auto-save in background (drafts, progress)
    • Recovery strategies:
      • Undo/redo for all state changes
      • Soft deletes (trash/archive before permanent delete)
      • Clear error messages with actionable fixes
      • Preserve user input on errors (don't clear forms)
  5. Progressive Disclosure

    • Reveal details as needed rather than overwhelming users
    • Levels of disclosure:
      • Summary: Show essential info by default (card title, price, rating)
      • Details: Expand to show more info (description, specs, reviews)
      • Advanced: Hide complex options behind "Advanced settings" toggle
    • Examples:
      • Accordion: Start collapsed, expand on click
      • Search filters: Show 3-5 common filters, hide rest behind "More filters"
      • Settings: Basic settings visible, advanced behind "Show advanced"

Modern UX Patterns:

  1. Conversational Interfaces

    Prioritize natural language interaction where appropriate:

    Four types:

    • Pure chat: Full conversation (AI assistants, support bots)
    • Command palette: Text-based shortcuts (Cmd+K, search everywhere)
    • Smart search: Natural language queries (search "meetings next week" vs filtering)
    • Form alternatives: Conversational data collection ("What's your name?" vs form fields)

    When to use:

    • Complex searches with multiple variables
    • Task guidance (wizards, onboarding)
    • Contextual help
    • Quick actions (command palette)

    When NOT to use:

    • Simple forms (just use inputs)
    • Precise control interfaces (design tools, dashboards)
    • High-frequency repetitive tasks
  2. Adaptive Layouts

    Respond to user context automatically:

    • Time-based: Dark mode at night, light during day
    • Device-based: Simplified UI on mobile, full features on desktop
    • Connection-based: Reduce images/video on slow connections
    • Usage-based: Prioritize frequent actions, hide rarely-used features

    Examples:

    • Auto dark/light mode based on time or system preference
    • Simplified mobile navigation (hamburger menu) vs full desktop nav
    • Collapsed sidebar on small screens, expanded on large
  3. Minimal, Flat Design

    Current aesthetic preference:

    • No drop shadows (except subtle ones for modals/dropdowns)
    • No gradients for depth (use for accents/backgrounds if desired)
    • No glass morphism effects
    • Focus on typography, color, and spacing to create hierarchy
    • Functional depth: Layers of content (modals, sheets) use positioning, not visual depth

Navigation:

  • Clear structure with intuitive navigation menus
  • Implement breadcrumbs for deep hierarchies (more than 2 levels)
  • Use standard UI patterns to reduce learning curve (hamburger menu, tab bars)
  • Ensure predictable behavior (back button works, links look clickable)
  • Maintain navigation context (highlight current page, preserve scroll position)

Styling Implementation

Component Library & Tools

Component Library:

  • Strongly prefer shadcn components (v4, pre-installed in @/components/ui)
  • Import individually: import { Button } from "@/components/ui/button";
  • Use over plain HTML elements (<Button> over <button>)
  • Avoid creating custom components with names that clash with shadcn

Styling Engine:

  • Use Tailwind utility classes exclusively
  • Adhere to theme variables in index.css via CSS custom properties
  • Map variables in @theme (see tailwind.config.js)
  • Use inline styles or CSS modules only when absolutely necessary

Icons:

  • Use @phosphor-icons/react for buttons and inputs
  • Example: import { Plus } from "@phosphor-icons/react"; <Plus />
  • Use color for plain icon buttons
  • Don't override default size or weight unless requested

Notifications:

  • Use sonner for toasts
  • Example: import { toast } from 'sonner'

Loading States:

  • Always add loading states, spinners, placeholder animations
  • Use skeletons until content renders
Layout Implementation

Spacing Strategy:

  • Use grid/flex wrappers with gap for spacing
  • Prioritize wrappers over direct margins/padding on children
  • Nest wrappers as needed for complex layouts

Conditional Styling:

  • Use ternary operators or clsx/classnames utilities
  • Example: className={clsx('base-class', { 'active-class': isActive })}
Responsive Design

Fluid Layouts:

  • Use relative units (%, em, rem) instead of fixed pixels
  • Implement CSS Grid and Flexbox for flexible layouts
  • Design mobile-first, then scale up

Media Queries:

  • Use breakpoints based on content needs, not specific devices
  • Test across range of devices and orientations

Touch Targets:

  • Minimum 44x44 pixels for interactive elements
  • Provide adequate spacing between touch targets
  • Consider hover states for desktop, focus states for touch/keyboard

Performance:

  • Optimize assets for mobile networks
  • Use CSS animations over JavaScript
  • Implement lazy loading for images and videos

Accessibility Standards

Core Requirements:

  • Follow WCAG 2.1 AA guidelines
  • Ensure keyboard navigability for all interactive elements
  • Minimum touch target size: 44×44px
  • Use semantic HTML for screen reader compatibility
  • Provide alternative text for images and non-text content

Implementation Details:

  • Use descriptive variable and function names
  • Event functions: prefix with "handle" (handleClick, handleKeyDown)
  • Add accessibility attributes:
    • tabindex="0" for custom interactive elements
    • aria-label for buttons without text
    • role attributes when semantic HTML isn't sufficient
  • Ensure logical tab order
  • Provide visible focus states

Design Process & Testing

Design Workflow
  1. Understand Context:

    • What problem are we solving?
    • Who are the users and when will they use this?
    • What are the success criteria?
  2. Explore Options:

    • Present 2-3 alternative approaches
    • Explain trade-offs of each option
    • Ask which direction resonates
  3. Implement Iteratively:

    • Start with structure and hierarchy
    • Add visual polish progressively
    • Test at each stage
  4. Validate:

    • Use playwright MCP to test visual changes
    • Check across different screen sizes
    • Verify accessibility
Testing Checklist

Visual Testing:

  • Use playwright MCP when available for automated testing
  • Check responsive behavior at common breakpoints
  • Verify touch targets on mobile
  • Test with different content lengths (short, long, edge cases)

Accessibility Testing:

  • Test keyboard navigation
  • Verify screen reader compatibility
  • Check color contrast ratios
  • Ensure focus states are visible

Cross-Device Testing:

  • Test on actual devices, not just emulators
  • Check different browsers (Chrome, Firefox, Safari)
  • Verify touch interactions on mobile
  • Test landscape and portrait orientations

Examples

Example 1: Designing a Button

Initial Question to Ask:

Before I implement this button, I have a few design questions:
1. What's the primary action you want to emphasize?
2. Do you have brand colors in mind, or should I suggest options?
3. What emotion should this button convey? (urgent, calm, playful, professional)

After Getting Approval, Implementation:

tsx
import { Button } from "@/components/ui/button";
import { ArrowRight } from "@phosphor-icons/react";

<Button
  className="bg-slate-800 hover:bg-slate-700 text-white px-6 py-3 rounded-lg transition-colors duration-200"
>
  Get Started
  <ArrowRight className="ml-2" />
</Button>
Example 2: Typography Hierarchy

Question First:

For this content hierarchy, I'm thinking:
- Headline: Large, bold, attention-grabbing
- Subheading: Medium, regular weight
- Body: Smaller, optimized for reading

Should we go bold and contemporary, or subtle and refined?

Implementation After Approval:

tsx
<div className="space-y-4">
  <h1 className="text-5xl font-bold tracking-tight text-slate-900">
    Headline Here
  </h1>
  <h2 className="text-2xl text-slate-600">
    Supporting subheading
  </h2>
  <p className="text-base leading-relaxed text-slate-700">
    Body text optimized for readability with proper line height.
  </p>
</div>
Example 3: Unique Color Palette Suggestion

Presenting Options:

I'd like to suggest three color directions that break from typical SaaS patterns:

1. **Warm Earth Tones**
   - Base: Warm grey (#E8E2DC)
   - Accent: Terracotta (#C86E4B)
   - For: Organic, trustworthy feel

2. **Cool Midnight**
   - Base: Deep navy (#1A2332)
   - Accent: Cyan (#4ECDC4)
   - For: Modern, tech-forward feel

3. **Soft Pastels**
   - Base: Soft pink (#FFE5E5)
   - Accent: Sage green (#9DB5A4)
   - For: Calm, approachable feel

Which direction feels right for your brand?

Common Patterns to Avoid

❌ Don't:

  • Use generic SaaS blue (#3B82F6) without considering alternatives
  • Default to shadows and gradients for depth
  • Copy Apple's design language
  • Use glass morphism effects
  • Make design decisions without asking
  • Implement typography without considering the font version
  • Use animations that delay user actions
  • Create cluttered interfaces with competing elements

✅ Do:

  • Ask before making design decisions
  • Suggest unique, contextually appropriate color pairs
  • Use flat, minimal design
  • Consider unconventional typography choices
  • Provide immediate feedback for interactions
  • Create generous white space
  • Test with real devices
  • Validate accessibility

Version History

  • v1.0.0 (2025-10-18): Initial release with comprehensive UI/UX design guidance

References

For additional context, see:

© bencium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in bencium-controlled-ux-designer/skills/bencium-controlled-ux-designer of bencium/bencium-marketplace.

  • SKILL.md
  • ACCESSIBILITY.md
  • DESIGN-SYSTEM-TEMPLATE.md
  • MOTION-SPEC.md
  • RESPONSIVE-DESIGN.md

Open the folder on GitHubat commit 5de46a3

Compare with similar skills

Bencium Controlled UX Designer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bencium Controlled UX Designer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bencium Controlled UX Designer this skillbencium/bencium-marketplace446—~6.8kAutomated safety check: PassMIT
Typeui Fundamentalsbergside/typeui2k—~861Automated safety check: PassMIT
Make Interfaces Feel Bettersamuelclay/NewsBlur7.6k10 repos~1.5kAutomated safety check: PassMIT
UI UX Pro Maxsaoudi-h/solar-icons19018 repos~11kAutomated safety check: NotesCustom licence
Baseline UIibelick/ui-skills9.6k8 repos~855Automated safety check: PassMIT
Frontend Designanthropics/skills180k38 repos~2.3kAutomated safety check: PassApache-2.0

Similar skills

  • Typeui Fundamentals

    bergside/typeui

    Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements.

    2k GitHub stars~861 tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Make Interfaces Feel Better

    samuelclay/NewsBlur

    Design engineering principles for making interfaces feel polished.

    7.6k GitHub starsUsed in 10 repos~1.5k tokens
    Frontend & DesignAuto-check passed
  • UI UX Pro Max

    saoudi-h/solar-icons

    UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.

    190 GitHub starsUsed in 18 repos~11k tokens
    Frontend & DesignAuto-check: notes
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.6k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed
  • Frontend Design

    anthropics/skills

    Official

    Pushes the agent toward distinctive visual design for new or reworked UI: a clear aesthetic direction, deliberate typography and choices rooted in the subject.

    180k GitHub starsUsed in 38 repos~2.3k tokens
    Frontend & DesignAuto-check passed
  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    100k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed

More from bencium/bencium-marketplace

All 13 skills in this repo
  • Vanity Engineering Review

    bencium/bencium-marketplace

    Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or…

    446 GitHub stars~2.4k tokensUpdated 7 days ago
    Auto-check passed
  • Adaptive Communication

    bencium/bencium-marketplace

    A skill your agent uses when detecting ambiguous user intent, hedging language, open-ended framing, personal context before requests, or when unsure whether user wants exploration vs direct answer.

    446 GitHub stars~839 tokensUpdated 7 days ago
    Auto-check passed
  • Insurgent Campaign

    bencium/bencium-marketplace

    Grassroots-first campaign design for anyone being outspent — startups vs.

    446 GitHub stars~12k tokensUpdated 7 days ago
    Auto-check passed
  • Eu AI Act Reviewer

    bencium/bencium-marketplace

    Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions.

    446 GitHub stars~1.9k tokensUpdated 7 days ago
    Auto-check passed
  • Hungarian Humanizer

    bencium/bencium-marketplace

    Detect and remove AI-generated markers from Hungarian text, making it sound like a native Hungarian speaker wrote it.

    446 GitHub stars~1.9k tokensUpdated 7 days ago
    Auto-check passed
  • UI Typography

    bencium/bencium-marketplace

    Professional typography rules for UI design, web applications, software interfaces, and all screen-based text.

    446 GitHub stars~3.5k tokensUpdated 7 days ago
    Auto-check: warnings

Questions about Bencium Controlled UX Designer

What does Bencium Controlled UX Designer do?

Expert UI/UX design guidance for unique, accessible interfaces. Bencium Controlled UX Designer is an agent skill from bencium/bencium-marketplace. Expert UI/UX design guidance for unique, accessible interfaces.

When should I use Bencium Controlled UX Designer?

Bencium Controlled UX Designer fits situations like: visual decisions; the user asks to build web components.

How do I install Bencium Controlled UX Designer in Claude Code?

Run `npx skills add bencium/bencium-marketplace --skill bencium-controlled-ux-designer -a claude-code`. Or copy the skill folder (bencium-controlled-ux-designer/skills/bencium-controlled-ux-designer in bencium/bencium-marketplace) into .claude/skills/bencium-controlled-ux-designer in your project. Claude Code loads it when a task matches its description.

How do I install Bencium Controlled UX Designer in Codex?

Run `npx skills add bencium/bencium-marketplace --skill bencium-controlled-ux-designer -a codex`. Or copy the skill folder (bencium-controlled-ux-designer/skills/bencium-controlled-ux-designer in bencium/bencium-marketplace) into .agents/skills/bencium-controlled-ux-designer in your project. Codex loads it when a task matches its description.

Can I use Bencium Controlled UX Designer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bencium/bencium-marketplace --skill bencium-controlled-ux-designer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bencium-controlled-ux-designer, .gemini/skills/bencium-controlled-ux-designer, .github/skills/bencium-controlled-ux-designer and .opencode/skills/bencium-controlled-ux-designer in your project.

What does Bencium Controlled UX Designer need to run?

SKILL.md names no scripts, command-line tools or credentials: Bencium Controlled UX Designer is instructions for the agent only.

Does Bencium Controlled UX Designer access the network?

SKILL.md names 4 domains. As links in the text: w3.org, fonts.google.com, tailwindcss.com and ui.shadcn.com. This is read from the text; nothing was executed.

Is Bencium Controlled UX Designer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bencium Controlled UX Designer use?

Bencium Controlled UX Designer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bencium Controlled UX Designer use?

About 6.8k tokens (SKILL.md is roughly 27k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bencium Controlled UX Designer?

Skills that share tags, products or a category with Bencium Controlled UX Designer: Typeui Fundamentals (bergside/typeui, 2k stars), Make Interfaces Feel Better (samuelclay/NewsBlur, 7.6k stars), UI UX Pro Max (saoudi-h/solar-icons, 190 stars) and Baseline UI (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bencium Controlled UX Designer?

bencium (a GitHub user) maintains it in bencium/bencium-marketplace, which has 446 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 4, 2026.

Source: bencium/bencium-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.