frontend-design
Skill1 starsChanged 8 months agoMITView on GitHub
Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
187 other projects use a version of this, 117 of them edited.
Adopted by
Most recently taken up by
- RostislavDugin/postgresustheir own version, first seen Nov 8, 2026
- databasus/databasustheir own version, first seen Nov 8, 2026
- ceilf6/FrontAgenttheir own version, first seen Nov 8, 2026
- maxtrigify/Ottotheir own version, first seen Nov 8, 2026
- rvdbreemen/OTGW-firmwareedited, first seen Nov 8, 2026
- open-slide/open-slideedited, first seen Nov 8, 2026
Used with
Projects with it also use instantly-campaign, albert-dm and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
yawningwhaleAISkillinstantly-campaign
Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.
Also in 6 projects that use this
yawningwhaleAISkillalbert-dm
Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).
Also in 5 projects that use this
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
julianoczkowskiSkillbrief-to-tasks
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Also in 7 projects that use this
SeifBenayedSkillfile-reading
Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.
Also in 6 projects that use this
- +6 more from naman10parikh
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 117
- bytedance/deer-flow★ 85k15% same
- novuhq/novu★ 40k26% same
- Dokploy/dokploy★ 38k28% same
- 1weiho/open-slide★ 9.7k26% same
- open-slide/open-slide★ 9.7k26% same
- basketikun/infinite-canvas★ 9.5k26% same
- mfts/papermark★ 9.2k26% same
- papermark/papermark★ 9.2k26% same
- anbeime/skill★ 7.9k26% same
- midudev/preguntas-entrevista-react★ 7.8k26% same
107 more not listed
Wrote their own version · 70
- anthropics/skills★ 189ksame name
- anthropics/claude-plugins-official★ 46ksame name
- markmead/hyperui★ 12ksame name
- mengxi-ream/read-frog★ 10ksame name
- databasus/databasus★ 9.3ksame name
- RostislavDugin/postgresus★ 9.3ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- BuilderIO/agent-native★ 7.6ksame name
- nolly-studio/cult-ui★ 6.9ksame name
60 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- documentation-auditSkill
- fresh-eyes-reviewSkill
- landing-page-designSkill
- pythonSkill
- session-reflectionSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 53
Avoid Lucide — it is overused to the point of being a visual fingerprint for AI-generated interfaces.
- Distinctive: line 56
Heroicons: When you need Apple-like simplicity and clarity.
“Common” is measured: kept by at least 6 in 10 of the 181 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend Design
Overview
This skill guides creation of distinctive, production-grade frontend interfaces for general-purpose work: components, pages, and applications. It is not for landing pages — use the landing-page-design skill for those. Implement real working code (HTML/CSS/JS, React, Vue, etc.) with exceptional attention to aesthetic details and creative choices that make every project feel genuinely designed for its context.
MANDATORY: Vibe Discovery (Do This First)
BEFORE writing any code, run the Vibe Discovery process. Do not skip this step, do not pick from a menu, and do not fall back on comfortable defaults. The Vibe Discovery process ensures every project starts with a unique aesthetic direction derived from the real world rather than from pattern-matched AI defaults.
See the full process in ../_shared/references/vibe-discovery.md.
Frontend Aesthetics Guidelines
Typography
Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial, Inter, and Roboto — opt instead for distinctive choices that elevate the interface's aesthetics. Unexpected, characterful font choices create immediate visual identity. Pair a distinctive display font with a refined body font: the display font sets the tone and personality, while the body font ensures readability and complements without competing. Never settle for the first font that comes to mind; if it feels familiar, it is probably overused.
Color & Theme
Commit to a cohesive aesthetic rather than hedging across multiple directions. Use CSS variables for consistency so that your palette propagates cleanly through every component. Dominant colors with sharp accents outperform timid, evenly-distributed palettes — a bold primary with one or two precise accent colors creates stronger visual hierarchy than five colors used in equal measure. Let the color story reinforce the vibe: warm, cool, muted, saturated, monochromatic, or high-contrast should all be deliberate choices traced back to the project's identity.
Motion
Use animations for effects and micro-interactions that make the interface feel alive. Prioritize CSS-only solutions for HTML projects; use the Motion library for React when available. Focus on high-impact moments rather than sprinkling animations everywhere: one well-orchestrated page load with staggered reveals (using animation-delay) creates more delight than scattered micro-interactions competing for attention. Scroll-triggered animations and hover states that surprise — an unexpected scale, a color shift, a subtle rotation — turn passive browsing into active discovery. Every animation should feel intentional and connected to the overall aesthetic.
Spatial Composition
Embrace unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements that draw the eye and create visual tension. Generous negative space OR controlled density — both are valid tools depending on the vibe, but the mushy middle ground of "mostly evenly spaced" is almost never interesting. Let the content's nature dictate spatial relationships: a dense data interface can be beautiful through rigorous alignment, while a creative portfolio might thrive on deliberate chaos. Break the expected grid when the design calls for it.
Backgrounds & Visual Details
Create atmosphere and depth rather than defaulting to solid colors or plain white. Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays all contribute to a sense of place and craft. These details should match and reinforce the overall aesthetic — a warm organic vibe calls for soft textures and natural gradients, while a brutalist direction might use harsh shadows and raw surfaces. The background is not empty space; it is the stage on which everything else performs.
Anti-AI-Slop Principles
Generic AI output has a look: you have seen it a thousand times and it is instantly recognizable. These principles exist to ensure your work never triggers that recognition.
Icons
Avoid Lucide — it is overused to the point of being a visual fingerprint for AI-generated interfaces. Use instead:
- Iconify Solar: Multiple styles available (outline, broken, duotone) that give you range within a single family.
- Heroicons: When you need Apple-like simplicity and clarity.
- Phosphor: A flexible weight system that adapts to different densities and moods.
- Custom SVGs: For brand differentiation when no icon set captures the right feel.
Fonts
Kill Inter, Roboto, Arial, and system fonts. These are the typographic equivalent of beige carpet — functional, invisible, and utterly devoid of character. No defaulting to comfortable choices. If a font name is the first one that comes to mind, it is probably too common. Every project deserves a typographic identity that someone actually chose with intention.
Colors
No purple gradients on white backgrounds. This specific combination has become the calling card of generic AI output. If your instinct reaches for violet-to-indigo on a light field, stop and reconsider. There are millions of color combinations in the world; use one that was not generated by default.
Anti-Anti-Slop
Dark backgrounds with monospace fonts and neon green, cyan, or magenta accents — the terminal/hacker aesthetic — is just as overplayed and lazy as purple-on-white. It is not edgy or distinctive; it is the default fallback when trying too hard to avoid looking generic. Avoiding one cliche by falling into another is not progress. If your "edgy" design looks like every other developer's dark-mode portfolio, you have simply traded one form of sameness for another.
Layouts
Break the grid. Overlapping elements, diagonal sections, asymmetric spacing, container-breaking hero elements, and negative space used as a deliberate design element all push beyond the predictable card-grid-with-rounded-corners that dominates AI output. Not every layout needs to be radical, but every layout should feel like someone made a conscious choice about spatial relationships.
Complexity Matching
Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations, layered effects, and rich interactive details — cutting corners on a maximalist vision produces something that looks half-finished rather than intentionally simple. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details — elegance comes from executing the vision well, not from writing less code. The amount of effort should match the ambition of the aesthetic.
Aesthetic Reference Library
For implementation raw materials — font pairings, hex codes, CSS techniques, and layout patterns organized by aesthetic category — see ../_shared/references/aesthetic-library.md. This is a parts bin for cherry-picking after you have completed Vibe Discovery, not a menu of styles to adopt wholesale.
Choosing an Aesthetic
When selecting a direction, consider what the content actually IS. A restaurant does not need to look like a SaaS dashboard. A personal blog does not need to look like a developer portfolio. A community forum does not need to look like a fintech app. Let the subject matter drive the aesthetic, not your default comfort zone or the last project you worked on.
Roll the dice. If your instinct says "dark background," go light. If you reach for monospace, pick a serif. If you are about to use a card grid, try a magazine layout. Fight your own patterns — the first idea is usually the most predictable one, and predictable is the enemy of distinctive.
Remember: Claude is capable of extraordinary creative work. Do not hold back. Do not settle for "good enough" or "clean and modern." Commit fully to a distinctive vision and show what can truly be created when thinking outside the box. Every project is an opportunity to make something that has never existed before.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

