Automated summary
A frontend design guide that forces an explicit aesthetic direction (type, color, motion, composition) before generating functional, polished interface code.
Strengths
- Requires a framing step (purpose, tone, constraints, differentiation) before any implementation
- Gives concrete, actionable direction on typography, palettes, animation, layout and backgrounds
- Ships an explicit anti-pattern list to steer away from generic output (Inter, Roboto, purple gradients)
- Extends the principles to Qt/C++ desktop apps through QSS, QPalette and QPropertyAnimation
Limitations
- Purely prescriptive: no libraries, components or validation tooling included
- Aesthetic quality stays subjective and is hard to verify automatically
- The Qt/C++ adaptation is only sketched in a few bullets, with no code samples
Use it when you need a web or desktop interface with a strong visual identity instead of a default template.
Skip it for small tweaks to an existing UI, backend work, or when a fixed brand guidelines are already mandated.
Security analysis
SafeThe skill contains only frontend design guidance and does not instruct destructive actions, credential exfiltration, obfuscated payloads, or safety disabling. No allowed tools are declared, and there is no executable code or network behavior.
No concerns found
How this analysis is madeExamples
Build a landing page for an independent coffee roaster. Pick a distinctive aesthetic direction, use expressive typography and custom CSS variables, and add a staggered page-load animation — no generic fonts or purple gradients.Create a React analytics dashboard that feels editorial and refined rather than default-SaaS: asymmetric grid, muted palette with one sharp accent, Motion for micro-interactions, and a working light theme.Restyle my Qt/C++ scientific data viewer with QSS and QPalette: refined technical aesthetic, custom typography, subtle drop shadows and QPropertyAnimation transitions on panel toggles.name: frontend-design description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when building web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Frontend Design
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.
Design Thinking
Before coding, understand the context and commit to a BOLD aesthetic direction:
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Pick an extreme — brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian
- Constraints: Technical requirements (framework, performance, accessibility)
- 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.
Frontend Aesthetics Guidelines
Typography
Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt for distinctive choices that elevate the interface. 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 creates more delight than scattered micro-interactions.
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. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
Anti-Patterns (What NOT to Do)
NEVER use:
- Overused font families (Inter, Roboto, Arial, system fonts)
- Cliched color schemes (purple gradients on white backgrounds)
- Predictable layouts and component patterns
- Cookie-cutter design that lacks context-specific character
NEVER converge on common AI choices (Space Grotesk, for example) across generations.
Implementation
Match implementation complexity to the aesthetic vision:
- Maximalist designs need elaborate code with extensive animations and effects
- Minimalist designs need restraint, precision, and careful attention to spacing, typography, and subtle details
Elegance comes from executing the vision well.
Output Requirements
Implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
Vary between light and dark themes, different fonts, different aesthetics. No design should be the same.
Qt/C++ Desktop Adaptation
When applying these principles to Qt/C++ desktop applications:
- QSS (Qt Style Sheets) is the primary styling mechanism — treat it like CSS
- Use
QPalettefor system-level color theming where QSS falls short - Leverage
QGraphicsDropShadowEffect,QGraphicsOpacityEffectfor depth - Custom
QStylesubclasses for advanced rendering control QPropertyAnimationfor motion and transitions- Match the aesthetic direction to the domain: scientific tools → refined technical, creative tools → bold expressive
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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/distinctive-frontend-design-ms2s7dau' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/distinctive-frontend-design-ms2s7dau/download' --output '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md.part' && mv '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md.part' '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md' && test -s '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/frontend-design' && cp -R '.skill-downloads/distinctive-frontend-design-ms2s7dau' '.claude/skills/frontend-design'Cursor
test -f '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md' && test -s '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/frontend-design' && cp -R '.skill-downloads/distinctive-frontend-design-ms2s7dau' '.cursor/skills/frontend-design'Codex
test -f '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md' && test -s '.skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/frontend-design' && cp -R '.skill-downloads/distinctive-frontend-design-ms2s7dau' '.agents/skills/frontend-design'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/distinctive-frontend-design-ms2s7dau'openskills read 'distinctive-frontend-design-ms2s7dau'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/distinctive-frontend-design-ms2s7dau/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.