Create distinctive, production-grade frontend interfaces that avoid generic “AI slop” aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. Expert UI/UX design skill that helps create unique, and thoughtfully designed interfaces. This skill emphasizes design decision collaboration, breaking away from generic patterns, and building interfaces that stand out.
This skill emphasizes bold creative commitment, breaking away from generic patterns, and building interfaces that are visually striking and memorable while remaining functional.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. Based on Anthropic's Frontend Designer Skill
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
All rights reserved — view on GitHub — with no detectable licence, this issue links rather than republishes: the skills are omitted from the agent manifest and from the whole-book markdown.
Discovery
16 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 16 distinct layouts observed: adaptive-communication/skills/*/SKILL.md, bencium-aeo/skills/*/SKILL.md, bencium-code-conventions/skills/*/SKILL.md, bencium-controlled-ux-designer/skills/*/SKILL.md, bencium-impact-designer/skills/*/SKILL.md, bencium-innovative-ux-designer/skills/*/SKILL.md, design-audit/skills/*/SKILL.md, eu-ai-act-reviewer/skills/*/SKILL.md, human-architect-mindset/skills/*/SKILL.md, hungarian-humanizer/skills/*/SKILL.md, insurgent-campaign/skills/*/SKILL.md, negentropy-lens/skills/*/SKILL.md, relationship-design/skills/*/SKILL.md, renaissance-architecture/skills/*/SKILL.md, typography/skills/*/SKILL.md, vanity-engineering-review/skills/*/SKILL.md.
Issue colours
Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.
Purpose: What problem does this interface solve? Who uses it?
Tone: What aesthetic extreme fits? (see Tone Options below) Use these for inspiration but design one that is true to the aesthetic direction.
Differentiation: What makes this UNFORGETTABLE? What’s the one thing someone will remember?
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
Then implement working code (HTML/CSS/JS, React, TypeScript, etc.) that is:
Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend’s aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
Backgrounds & Visual Details: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
NEVER Use These AI-Generated Aesthetics:
Fonts: Inter, Roboto, Arial, system fonts as primary choice, Space Grotesk (overused by AI)
Colors: Generic SaaS blue (#3B82F6), purple gradients on white backgrounds
Identify the essential purpose and eliminate distractions
Begin with complexity,
Every element must justify its existence
Material Honesty
Digital materials have unique properties - embrace them
Buttons communicate affordance through color, spacing, typography, AND shadows when intentional
Cards can use borders, background differentiation, OR dramatic shadows for depth
Animations follow real-world physics principles adapted to digital responsiveness
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
Remember: Claude is capable of extraordinary creative work. Don’t hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
Examples:
Clickable: Use distinct colors, hover state changes, cursor feedback, subtle lift effects
Containers: Use borders, background shifts, generous padding, OR shadow depth
Hierarchy: Use scale, weight, spacing, AND elevation when it serves the aesthetic
Functional Layering
Create hierarchy through typography scale, color contrast, and spatial relationships
Layer information conceptually (primary → secondary → tertiary)
Use shadows and gradients INTENTIONALLY when they serve the aesthetic direction
Embrace functional depth: modals over content, dropdowns over UI
Avoid: glass morphism, Apple mimicry (but shadows/gradients are tools, not enemies)
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
Coherent Design Language
Every element should visually communicate its function
Elements should feel part of a unified system
Nothing should feel arbitrary
Invisibility of Technology
The best technology disappears
Users should focus on content and goals, not on understanding the interface
Purpose: Does every element serve a clear function?
Hierarchy: Is visual importance aligned with content importance?
Consistency: Do similar elements look and behave similarly?
Accessibility: Does it meet WCAG AA standards? (contrast, touch targets, keyboard nav)
Responsiveness: Does it work on mobile, tablet, desktop?
Uniqueness: Does this break from generic SaaS patterns?
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, think of a design system.
Dominant colors with SHARP accents outperform timid, evenly-distributed palettes
Test combinations against “does this look AI-generated?” filter
Vary between light and dark themes - no design should look the same
Create Atmosphere with Color:
See Visual Effects (Implementation Checklist) for implementation details on gradient meshes, grain overlays, layered transparencies, and dramatic shadows.
// 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)
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>
For this content hierarchy, I'm thinking:- Headline: Large, bold, attention-grabbing- Subheading: Medium, regular weight- Body: Smaller, optimized for readingShould 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>
Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.
Marketplace
A plugin manifest is published at .claude-plugin/marketplace.json by bencium.io, declaring 19 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.
Signal
This repository is unranked on skills.sh, which says nothing about it: the leaderboard covers a fraction of published skills.
Agent surfaces
The whole issue is available as one markdown document at /bencium/bencium-marketplace.md, and each skill at its own .md URL.
Publication
Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.
Appendix 5.1–5.3
3 files · 7 KB
Everything this skill ships beside its prose. All of it is set here, as subchapters of skill 5.