frontend-design
Skill1 starsChanged 48 days agoMITView on GitHub
先定美学方向再写码:10 种极端美学方向(极简/极繁/复古未来/有机/奢华/玩具感/编辑杂志/粗野/装饰艺术/工业)、 字体与配色创意准则、空间构图(非对称/重叠/破网格)、动效与氛围(渐变网格/噪点/颗粒)、以及「AI 味」黑名单。 触发词:美学方向、设计风格、风格定义、创意UI、独特界面、AI味、避免AI感、紫渐变、 字体选择、字体搭配、展示字体、氛围营造、渐变网格、噪点、视觉冲击、页面调性、设计差异化 不用于:基础排版/间距/对比度规范(走 ui-design);响应式断点实现(走 responsive-design)
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
7
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 18
Create memorable frontend interfaces that stand out from generic AI-generated aesthetics through bold creative choices.
- Distinctive: line 53
Before writing code, commit to an aesthetic direction:
- Distinctive: line 85
NEVER: use generic fonts:
- Distinctive: line 131
Prefer CSS animations for HTML.
- Distinctive: line 148
Create depth and atmosphere:
- Distinctive: line 166
Never converge on patterns:
- Distinctive: line 168
Use different font families each time
“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
Create memorable frontend interfaces that stand out from generic AI-generated aesthetics through bold creative choices.
See also:
ui-designfor fundamentals (typography, color, spacing),web-designfor CSS patterns.
Installation
OpenClaw / Moltbot / Clawbot
npx clawhub@latest install frontend-designWHAT This Skill Does
Guides creation of visually distinctive web interfaces by:
- Establishing a bold aesthetic direction before coding
- Making intentional typography, color, and spatial choices
- Implementing motion and micro-interactions that delight
- Avoiding the predictable patterns that mark AI-generated UIs
WHEN To Use
- Building a new component, page, or web application
- Creating landing pages, marketing sites, or product UIs
- Redesigning interfaces to be more memorable
- Any frontend work where visual impact matters
KEYWORDS
frontend design, web ui, ui design, landing page, creative ui, web aesthetics, typography, visual design, motion design, distinctive interface
Design Thinking Process
Before writing code, commit to an aesthetic direction:
1. Understand Context
- Purpose: What problem does this interface solve?
- Audience: Who uses it and what do they expect?
- Constraints: Framework, performance, accessibility requirements
2. Choose a Bold Direction
Pick an extreme aesthetic — mediocrity is forgettable:
| Direction | Characteristics |
| Brutally Minimal | Stark, essential, nothing extra |
| Maximalist Chaos | Dense, layered, overwhelming intentionally |
| Retro-Futuristic | Blends vintage aesthetics with modern tech |
| Organic/Natural | Soft, flowing, nature-inspired |
| Luxury/Refined | Premium materials, subtle elegance |
| Playful/Toy-like | Fun, approachable, bright |
| Editorial/Magazine | Type-forward, grid-based |
| Brutalist/Raw | Exposed structure, anti-design |
| Art Deco/Geometric | Bold shapes, symmetry, ornament |
| Industrial/Utilitarian | Function-forward, robust |
3. Identify the Memorable Element
What single thing will someone remember about this interface? Commit to it.
Aesthetic Guidelines
Typography
NEVER use generic fonts:
- Arial, Helvetica, system-ui
- Inter, Roboto (unless highly intentional)
DO choose distinctive fonts:
- Pair a characterful display font with a refined body font
- Explore: Space Grotesk, Clash Display, Cabinet Grotesk, Satoshi, General Sans, Instrument Serif, Fraunces, Newsreader
/* Example pairing */
--font-display: 'Clash Display', sans-serif;
--font-body: 'Satoshi', sans-serif;Color & Theme
- Commit to a cohesive palette — don't hedge with safe choices
- Dominant + accent outperforms evenly-distributed colors
- Use CSS variables for consistency
- Avoid purple gradients on white (the "AI default")
:root {
--color-bg: #0a0a0a;
--color-surface: #141414;
--color-text: #fafafa;
--color-accent: #ff4d00;
--color-muted: #666666;
}Spatial Composition
Break expectations:
- Asymmetry over perfect balance
- Overlap elements intentionally
- Diagonal flow or unconventional layouts
- Generous negative space OR controlled density — not middle ground
- Grid-breaking elements that draw attention
Motion & Interaction
Focus on high-impact moments:
- Page load: Staggered reveals with
animation-delay - Scroll-triggered animations that surprise
- Hover states with personality
- Prefer CSS animations for HTML; Motion library for React
/* Staggered entrance */
.card { animation: fadeUp 0.6s ease-out backwards; }
.card:nth-child(1) { animation-delay: 0.1s; }
.card:nth-child(2) { animation-delay: 0.2s; }
.card:nth-child(3) { animation-delay: 0.3s; }
@keyframes fadeUp {
from { opacity: 0; transform: translateY(20px); }
to { opacity: 1; transform: translateY(0); }
}Backgrounds & Atmosphere
Create depth and atmosphere:
- Gradient meshes and multi-stop gradients
- Noise textures and grain overlays
- Geometric patterns or subtle grids
- Layered transparencies
- Dramatic shadows or complete flatness
- Custom cursors for interactive elements
Implementation Principles
Match Complexity to Vision
- Maximalist vision → elaborate code with extensive animations
- Minimalist vision → restraint, precision, perfect spacing
- Elegance = executing the vision well, not adding more
Vary Between Generations
Never converge on patterns:
- Alternate light/dark themes
- Use different font families each time
- Explore different aesthetic directions
- Each design should feel unique
NEVER Do
- NEVER use generic font families (Inter, Roboto, Arial, system fonts)
- NEVER use purple gradients on white backgrounds — the "AI aesthetic"
- NEVER use predictable, cookie-cutter layouts
- NEVER skip the design thinking phase — understand before building
- NEVER hedge with safe, middle-ground aesthetics — commit to a direction
- NEVER forget that distinctive design requires distinctive code
- NEVER converge on the same patterns across generations — vary intentionally
- NEVER add complexity without purpose — minimalism and maximalism both require intention
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- anthropics/skills★ 186ksame name
- bytedance/deer-flow★ 85ksame name
- anthropics/claude-plugins-official★ 46ksame name
- novuhq/novu★ 40ksame name
- Dokploy/dokploy★ 38ksame name
- markmead/hyperui★ 12ksame name
- mengxi-ream/read-frog★ 10ksame name
- 1weiho/open-slide★ 9.3ksame name
- mfts/papermark★ 9.2ksame name
- papermark/papermark★ 9.2ksame name
177 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.
Used alongsideProjects with it also use file-reading, brief-to-tasks 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.
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
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
AnthropicSkillacademy-guide
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
Also in 5 projects that use this
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 16 projects that use this
huyvpSkillcost-reducer
Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.
Also in 10 projects that use this
mm-mazharSkillcache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR).
Also in 6 projects that use this
In this repository60 other files it gives its agents.
- accessibility-auditSkill
- agent-browser-coreSkill
- ai-explainer-videoSkill
- ai-short-video-makerSkill
- ai-video-shortSkill
- AI 工具箱Skill
- antislopSkill
- browser-useSkill
- cangjie-skillSkill
- delivery-no-pseudoblockSkill
- design-reviewSkill
- design-routerSkill
- edge-tts-readSkill
- frontend-devSkill
- fuheshun-auto-clipSkill
- fullstack-devSkill
- githubSkill
- git-shipSkill
- grillingSkill
- hfut-inspectorSkill
- humanizerSkill
- image-to-editable-pptxSkill
- kdocsSkill
- local-video-pipelineSkill
- markitdown-skillSkill
- pdfSkill
- pptxSkill
- qf-english-polishSkill
- qq-emailSkill
- responsive-designSkill
- self-improving-agentSkill
- sherpa-onnx-ttsSkill
- short-video-script-to-finished-videoSkill
- skill-creatorSkill
- skill-integratorSkill
- tastemakerSkill
- techdebtSkill
- Typography FoundationsSkill
- ui-designSkill
- video-scriptSkill
- web-accessSkill
- web-design-guidelinesSkill
- web-design-layoutSkill
- wechat-article-proSkill
- wechat-article-searchSkill
- weekly-reviewSkill
- word-toolkitSkill
- WorkBuddy 工作原则Skill
- xlsxSkill
- yuketang-harvesterSkill
- 学术研究工具箱Skill
- 安全审查工具箱Skill
- 工程方法论工具箱Skill
- 开发工具箱Skill
- 微信小程序开发套件Skill
- 技能包跨机器打包Skill
- 文档工具箱Skill
- 知识工具箱Skill
- 联网工具箱Skill
- 评审委员会Skill
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.

