frontend-skill
Skill1 starsChanged 9 days agoMITView on GitHub
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
15 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- antoniolg/agent-kitedited, first seen Nov 8, 2026
- tikhomirov/skillsedited, first seen Nov 1, 2026
- julianromli/ai-skillsedited, first seen Oct 25, 2026
- realityforge/skillsedited, first seen Oct 20, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- jhy0285/monofieldtheir own version, first seen Oct 13, 2026
Used with
Projects with it also use ui-ux-pro-max, web-design-guidelines and 4 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.
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). 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.
Also in 5 projects that use this
VercelSkillweb-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Also in 4 projects that use this
DatabricksSkillshadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Also in 3 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
VercelSkillagent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Also in 3 projects that use this
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- julianromli/ai-skills★ 222100% same
- antoniolg/agent-kit★ 100100% same
- HK-hub/AgentSkills★ 6100% same
- masterno/agent-skills★ 2100% same
- ElyzeSolutions/skills★ 1100% same
- neyuki778/nanoClaudeCode★ 1100% same
- snissn/skills★ 1100% same
- tikhomirov/skills★ 1100% same
- realityforge/skills★ 0100% same
Wrote their own version · 6
- jhy0285/monofield★ 6same name
- 14BryanEspinoza/frontend-skill★ 1same name
- jpoindexter/theft-kit★ 1same name
- YOSSII812001/claude-code-jarvis★ 1same name
- adrianrosariopr/ClaudeSkills★ 0same name
- davidanthonyn/claude-skills★ 0same name
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 repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- all-skills-indexSkill
- skill-starter-categoriesSkill
- claude-code-packSkill
- deep-thinkSkill
- gpt-tasteSkill
- image-taste-frontendSkill
- full-output-enforcementSkill
- redesign-existing-projectsSkill
- design-taste-frontendSkill
- cursor-packSkill
- skill-starter-favouritesSkill
- gemini-packSkill
- official-openai-packSkill
- skill-starter-originalsSkill
- skill-starter-reccomendedSkill
- skill-starter-packSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
42 rules. 40 are common, 1 is distinctive, and 1 is very specific to this project.
40
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Self-review: before finishing, check it is modern, balanced, consistent and production-ready.
- Common: line 17
Use this skill when the quality of the work depends on art direction, hierarchy, restraint, imagery, and motion rather than component count.
- Common: line 23
Before building, write three things:
- Common: line 33
Start with composition, not components.
- Common: line 34
Prefer a full-bleed hero or full-canvas visual anchor.
- Common: line 36
Keep copy short enough to scan in seconds.
- Common: line 37
Use whitespace, alignment, scale, cropping, and contrast before adding chrome.
- Common: line 39
Default to cardless layouts.
- Common: line 40
Treat the first viewport as a poster, not a document.
- Common: line 57
No hero cards, stat strips, logo clouds, pill soup, or floating dashboards by default.
- Common: line 58
Keep headlines to roughly 2-3 lines on desktop and readable in one glance on mobile.
- Common: line 59
Keep the text column narrow and anchored to a calm area of the image.
- Common: line 60
All text over imagery must maintain strong contrast and clear tap targets.
- Common: line 62
If the first viewport still works after removing the image, the image is too weak.
- Common: line 66
If the first screen includes a sticky/fixed header, that header counts against the hero.
- Very specific: line 67
When using 100vh/100svh heroes, subtract persistent UI chrome (calc(100svh - header-height)) or overlay the header instead of stacking it …
- Common: line 71
Default to Linear-style restraint:
- Common: line 95
If a panel can become plain layout without losing meaning, remove the card treatment.
- Common: line 101
Use at least one strong, real-looking image for brands, venues, editorial pages, and lifestyle products.
- Common: line 102
Prefer in-situ photography over abstract gradients or fake 3D objects.
- Common: line 104
Do not use images with embedded signage, logos, or typographic clutter fighting the UI.
- Common: line 105
Do not generate images with built-in UI frames, splits, cards, or panels.
- Common: line 106
If multiple moments are needed, use multiple images, not one collage.
- Common: line 112
Write in product language, not design commentary.
- Common: line 116
Do not include prompt language or design commentary into the UI.
- Common: line 119
If deleting 30 percent of the copy improves the page, keep deleting.
- Common: line 123
When the work is a dashboard, app surface, admin tool, or operational workspace, default to utility copy over marketing copy.
- Common: line 126
Start with the working surface itself: KPIs, charts, filters, tables, status, or task context.
- Common: line 129
Avoid aspirational hero lines, metaphors, campaign-style language, and executive-summary banners on product surfaces unless specifically …
- Common: line 131
If a sentence could appear in a homepage hero or ad, rewrite it until it sounds like product UI.
- Common: line 132
If a section does not help someone operate, monitor, or decide, remove it.
- Common: line 137
Use motion to create presence and hierarchy, not noise.
- Common: line 145
Prefer Framer Motion when available for:
- Common: line 164
No cards by default.
- Common: line 165
No hero cards by default.
- Common: line 166
No boxed or center-column hero when the brief calls for full bleed.
- Common: line 167
No more than one dominant idea per section.
- Common: line 168
No section should need many tiny UI devices to explain itself.
- Common: line 169
No headline should overpower the brand on branded pages.
- Common: line 171
No split-screen hero unless text sits on a calm, unified side.
- Common: line 172
No more than two typefaces without a clear reason.
- Common: line 173
No more than one accent color unless the product already has a strong system.
“Common” is measured: kept by at least 6 in 10 of the 14 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 Skill
Owner quality bar (always applies)
- Bar: polished, production-grade UI. Prioritize spacing, hierarchy, alignment, typography, balance, responsiveness and component cohesion. Nothing generic, clunky, boxy, crowded, inconsistent, dated or "developer-looking".
- Existing UI first: analyze the current design system, spacing, type, colors and components before changing anything. Preserve structure and product direction unless told otherwise; refine rather than redesign; reuse components.
- Standards: consistent spacing rhythm, strong type scale, fewer but better elements, proper whitespace, aligned layouts. Mobile and desktop both feel intentional.
- References: screenshots and mocks are the source of truth. Match spacing, alignment, sizing, typography, density and composition closely.
- Self-review: before finishing, check it is modern, balanced, consistent and production-ready. If anything feels awkward, dense, plain or dated, refine it.
- Routing:
redesign-skillto improve existing UI;taste-skillorgpt-tasteskillfor premium implementation;images-taste-skillfor image-first or high-end visual direction;output-skillwhen completeness matters; style skills (brutalist-skill,minimalist-skill,soft-skill,high-end-visual-design,stitch-skill) when that style is asked for.
Use this skill when the quality of the work depends on art direction, hierarchy, restraint, imagery, and motion rather than component count.
Goal: ship interfaces that feel deliberate, premium, and current. Default toward award-level composition: one big idea, strong imagery, sparse copy, rigorous spacing, and a small number of memorable motions.
Working Model
Before building, write three things:
- visual thesis: one sentence describing mood, material, and energy
- content plan: hero, support, detail, final CTA
- interaction thesis: 2-3 motion ideas that change the feel of the page
Each section gets one job, one dominant visual idea, and one primary takeaway or action.
Beautiful Defaults
- Start with composition, not components.
- Prefer a full-bleed hero or full-canvas visual anchor.
- Make the brand or product name the loudest text.
- Keep copy short enough to scan in seconds.
- Use whitespace, alignment, scale, cropping, and contrast before adding chrome.
- Limit the system: two typefaces max, one accent color by default.
- Default to cardless layouts. Use sections, columns, dividers, lists, and media blocks instead.
- Treat the first viewport as a poster, not a document.
Landing Pages
Default sequence:
- Hero: brand or product, promise, CTA, and one dominant visual
- Support: one concrete feature, offer, or proof point
- Detail: atmosphere, workflow, product depth, or story
- Final CTA: convert, start, visit, or contact
Hero rules:
- One composition only.
- Full-bleed image or dominant visual plane.
- Canonical full-bleed rule: on branded landing pages, the hero itself must run edge-to-edge with no inherited page gutters, framed container, or shared max-width; constrain only the inner text/action column.
- Brand first, headline second, body third, CTA fourth.
- No hero cards, stat strips, logo clouds, pill soup, or floating dashboards by default.
- Keep headlines to roughly 2-3 lines on desktop and readable in one glance on mobile.
- Keep the text column narrow and anchored to a calm area of the image.
- All text over imagery must maintain strong contrast and clear tap targets.
If the first viewport still works after removing the image, the image is too weak. If the brand disappears after hiding the nav, the hierarchy is too weak.
Viewport budget:
- If the first screen includes a sticky/fixed header, that header counts against the hero. The combined header + hero content must fit within the initial viewport at common desktop and mobile sizes.
- When using
100vh/100svhheroes, subtract persistent UI chrome (calc(100svh - header-height)) or overlay the header instead of stacking it in normal flow.
Apps
Default to Linear-style restraint:
- calm surface hierarchy
- strong typography and spacing
- few colors
- dense but readable information
- minimal chrome
- cards only when the card is the interaction
For app UI, organize around:
- primary workspace
- navigation
- secondary context or inspector
- one clear accent for action or state
Avoid:
- dashboard-card mosaics
- thick borders on every region
- decorative gradients behind routine product UI
- multiple competing accent colors
- ornamental icons that do not improve scanning
If a panel can become plain layout without losing meaning, remove the card treatment.
Imagery
Imagery must do narrative work.
- Use at least one strong, real-looking image for brands, venues, editorial pages, and lifestyle products.
- Prefer in-situ photography over abstract gradients or fake 3D objects.
- Choose or crop images with a stable tonal area for text.
- Do not use images with embedded signage, logos, or typographic clutter fighting the UI.
- Do not generate images with built-in UI frames, splits, cards, or panels.
- If multiple moments are needed, use multiple images, not one collage.
The first viewport needs a real visual anchor. Decorative texture is not enough.
Copy
- Write in product language, not design commentary.
- Let the headline carry the meaning.
- Supporting copy should usually be one short sentence.
- Cut repetition between sections.
- Do not include prompt language or design commentary into the UI.
- Give every section one responsibility: explain, prove, deepen, or convert.
If deleting 30 percent of the copy improves the page, keep deleting.
Utility Copy For Product UI
When the work is a dashboard, app surface, admin tool, or operational workspace, default to utility copy over marketing copy.
- Prioritize orientation, status, and action over promise, mood, or brand voice.
- Start with the working surface itself: KPIs, charts, filters, tables, status, or task context. Do not introduce a hero section unless the user explicitly asks for one.
- Section headings should say what the area is or what the user can do there.
- Good: "Selected KPIs", "Plan status", "Search metrics", "Top segments", "Last sync".
- Avoid aspirational hero lines, metaphors, campaign-style language, and executive-summary banners on product surfaces unless specifically requested.
- Supporting text should explain scope, behavior, freshness, or decision value in one sentence.
- If a sentence could appear in a homepage hero or ad, rewrite it until it sounds like product UI.
- If a section does not help someone operate, monitor, or decide, remove it.
- Litmus check: if an operator scans only headings, labels, and numbers, can they understand the page immediately?
Motion
Use motion to create presence and hierarchy, not noise.
Ship at least 2-3 intentional motions for visually led work:
- one entrance sequence in the hero
- one scroll-linked, sticky, or depth effect
- one hover, reveal, or layout transition that sharpens affordance
Prefer Framer Motion when available for:
- section reveals
- shared layout transitions
- scroll-linked opacity, translate, or scale shifts
- sticky storytelling
- carousels that advance narrative, not just fill space
- menus, drawers, and modal presence effects
Motion rules:
- noticeable in a quick recording
- smooth on mobile
- fast and restrained
- consistent across the page
- removed if ornamental only
Hard Rules
- No cards by default.
- No hero cards by default.
- No boxed or center-column hero when the brief calls for full bleed.
- No more than one dominant idea per section.
- No section should need many tiny UI devices to explain itself.
- No headline should overpower the brand on branded pages.
- No filler copy.
- No split-screen hero unless text sits on a calm, unified side.
- No more than two typefaces without a clear reason.
- No more than one accent color unless the product already has a strong system.
Reject These Failures
- Generic SaaS card grid as the first impression
- Beautiful image with weak brand presence
- Strong headline with no clear action
- Busy imagery behind text
- Sections that repeat the same mood statement
- Carousel with no narrative purpose
- App UI made of stacked cards instead of layout
Litmus Checks
- Is the brand or product unmistakable in the first screen?
- Is there one strong visual anchor?
- Can the page be understood by scanning headlines only?
- Does each section have one job?
- Are cards actually necessary?
- Does motion improve hierarchy or atmosphere?
- Would the design still feel premium if all decorative shadows were removed?
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.

