frontend-design
Frontend design skill for UI/UX implementation - generates distinctive, production-grade interfaces
Best use case
frontend-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Frontend design skill for UI/UX implementation - generates distinctive, production-grade interfaces
Teams using frontend-design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/frontend-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How frontend-design Compares
| Feature / Agent | frontend-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Frontend design skill for UI/UX implementation - generates distinctive, production-grade interfaces
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Frontend Design Skill This skill helps create **distinctive, production-grade frontend interfaces** that avoid generic AI aesthetics. ## Core Principles When building any frontend interface, follow these principles to create visually striking, memorable designs: ### 1. Establish Bold Aesthetic Direction **Before writing any code**, define a clear aesthetic vision: - **Understand the purpose**: What is this interface trying to achieve? - **Choose an extreme tone**: Select a distinctive aesthetic direction - Brutalist: Raw, bold, functional - Maximalist: Rich, layered, decorative - Retro-futuristic: Nostalgic tech aesthetics - Minimalist with impact: Powerful simplicity - Neo-brutalist: Modern take on brutalism - **Identify the unforgettable element**: What will make this design memorable? ### 2. Implementation Standards Every interface you create should be: - ✅ **Production-grade and functional**: Code that works flawlessly - ✅ **Visually striking and memorable**: Designs that stand out - ✅ **Cohesive with clear aesthetic point-of-view**: Unified vision throughout ## Critical Design Guidelines ### Typography **Choose fonts that are beautiful, unique, and interesting.** - ❌ **AVOID**: Generic system fonts (Arial, Helvetica, default sans-serif) - ✅ **USE**: Distinctive choices that elevate aesthetics - Display fonts with character - Unexpected font pairings - Variable fonts for dynamic expression - Fonts that reinforce your aesthetic direction ### Color & Theme **Commit to cohesive aesthetics with CSS variables.** - ❌ **AVOID**: Generic color palettes, predictable combinations - ✅ **USE**: Dominant colors with sharp accents - Define comprehensive CSS custom properties - Create mood through color temperature - Use unexpected color combinations - Build depth with tints, shades, and tones ### Motion & Animation **Use high-impact animations that enhance the experience.** - For **HTML/CSS**: CSS-only animations (transforms, transitions, keyframes) - For **React**: Motion library (Framer Motion, React Spring) - ❌ **AVOID**: Generic fade-ins, boring transitions - ✅ **USE**: High-impact moments - Purposeful movement that guides attention - Smooth, performant animations - Delightful micro-interactions - Entrance/exit animations with personality ### Composition & Layout **Embrace unexpected layouts.** - ❌ **AVOID**: Predictable grids, centered everything, safe layouts - ✅ **USE**: Bold composition choices - Asymmetry - Overlap - Diagonal flow - Unexpected whitespace - Breaking the grid intentionally ### Details & Atmosphere **Create atmosphere through thoughtful details.** - ✅ Textures and grain - ✅ Sophisticated gradients - ✅ Patterns and backgrounds - ✅ Custom effects (blur, glow, shadows) - ✅ Attention to spacing and rhythm ## What to AVOID **Generic AI Design Patterns:** - ❌ Overused fonts (Inter, Roboto, Open Sans as defaults) - ❌ Clichéd color schemes (purple gradients, generic blues) - ❌ Predictable layouts (everything centered, safe grids) - ❌ Cookie-cutter design that lacks context-specific character - ❌ Lack of personality or point-of-view - ❌ Generic animations (basic fade-ins everywhere) ## Execution Philosophy **Show restraint or elaboration as the vision demands—execution quality matters most.** - Every design decision should serve the aesthetic direction - Don't add complexity for its own sake - Don't oversimplify when richness is needed - Commit fully to your chosen direction - Polish details relentlessly ## Implementation Process When creating a frontend interface: 1. **Define the aesthetic direction** (brutalist, maximalist, minimalist, etc.) 2. **Choose distinctive typography** that reinforces the aesthetic 3. **Establish color system** with CSS variables 4. **Design layout** with unexpected but purposeful composition 5. **Add motion** that enhances key moments 6. **Polish details** (textures, shadows, spacing) 7. **Review against principles** - is this distinctive and production-grade? ## Examples of Strong Aesthetic Directions - **Brutalist Dashboard**: Monospace fonts, high contrast, grid-based, utilitarian - **Retro-Futuristic Landing**: Neon colors, chrome effects, 80s sci-fi inspired - **Minimalist with Impact**: Generous whitespace, bold typography, single accent color - **Neo-Brutalist App**: Raw aesthetics, asymmetric layouts, bold shadows - **Maximalist Content**: Rich layers, decorative elements, abundant color ## Resources For deeper guidance on prompting for high-quality frontend design, see the [Frontend Aesthetics Cookbook](https://github.com/anthropics/claude-cookbooks/blob/main/coding/prompting_for_frontend_aesthetics.ipynb). --- **Remember**: The goal is to create interfaces that are both functionally excellent and visually unforgettable. Avoid generic AI aesthetics by committing to a clear, bold direction and executing it with meticulous attention to detail.
Related Skills
stitch-design
Unified entry point for Stitch design work. Handles prompt enhancement (UI/UX keywords, atmosphere), design system synthesis (.stitch/DESIGN.md), and high-fidelity screen generation/editing via Stitch MCP.
frontend-slides
Generate zero-dependency HTML presentations with keyboard navigation, print CSS, responsive design, and speaker notes. Creates a single self-contained HTML file — no build step, no framework, no CDN. Use when: (1) Creating slide decks or presentations, (2) Building pitch decks, (3) Making technical talks, (4) User asks for slides or a presentation, (5) Quick visual content for meetings.
design-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design
token-usage
Show Claude Code token usage across sessions — daily, weekly, per-project, and per-session breakdowns. Parses {{HOME_TOOL_DIR}}/projects/**/*.jsonl for consumption data. Use when the user asks about token usage, costs, how many tokens were used, session statistics, or wants a usage report.
tmux-status
Show status of all tmux sessions including dev environments, spawned agents, and running processes
tmux-monitor
Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.
tmux-message
Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — "claude-peers fallback", "tmux send-keys", "send to peer via tmux", "inject directive", "deliver to nanoclaw/hermes peer", "peer message". Tmux-only — won't reach peers running outside tmux.