aesthetic
Skill0 starsChanged 24 days agoMITView on GitHub
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Dinh2026/claudekit-skillsword for word, first seen Oct 15, 2026
- VoDaiLocz/kilo-kit-mcpword for word, first seen Aug 21, 2026
- duongthinh03/portfolioword for word, first seen Jun 24, 2026
- truongtv22/theone-training-skillsword for word, first seen Nov 19, 2025
- Linhv14/claude-skillword for word, first seen Nov 10, 2025
- mrgoonie/claudekit-skillsword for word, first seen Nov 10, 2025
Used with
Projects with it also use research.
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.
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions6 projects use a version of this.
Word for word · 6
- mrgoonie/claudekit-skills★ 2.2k100% same
- duongthinh03/portfolio★ 85100% same
- VoDaiLocz/kilo-kit-mcp★ 27100% same
- truongtv22/theone-training-skills★ 1100% same
- Dinh2026/claudekit-skills★ 0100% same
- Linhv14/claude-skill★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository104 other files it gives its agents.
- .claude/skills/claude-code/llms.txtllms.txt
- ai-multimodalSkill
- angular-architectSkill
- api-designerSkill
- architecture-designerSkill
- atlassian-mcpSkill
- backend-developmentSkill
- banner-designSkill
- better-authSkill
- brandSkill
- bunnySkill
- chaos-engineerSkill
- chrome-devtoolsSkill
- claude-codeSkill
- cli-developerSkill
- cloud-architectSkill
- code-documenterSkill
- code-reviewerSkill
- code-reviewSkill
- context-engineeringSkill
- cpp-proSkill
- csharp-developerSkill
- database-optimizerSkill
- databasesSkill
- debuggingSkill
- debugging-wizardSkill
- designSkill
- design-systemSkill
- devops-engineerSkill
- devopsSkill
- django-expertSkill
- django-storages-s3Skill
- docs-seekerSkill
- dotnet-core-expertSkill
- embedded-systemsSkill
- fastapi-expertSkill
- feature-forgeSkill
- fine-tuning-expertSkill
- flutter-expertSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- fullstack-guardianSkill
- game-developerSkill
- golang-proSkill
- google-adk-pythonSkill
- graphql-architectSkill
- java-architectSkill
- javascript-proSkill
- kotlin-specialistSkill
- kubernetes-specialistSkill
- laravel-specialistSkill
- legacy-modernizerSkill
- mcp-builderSkill
- mcp-developerSkill
- mcp-managementSkill
- media-processingSkill
- mermaidjs-v11Skill
- microservices-architectSkill
- ml-pipelineSkill
- monitoring-expertSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
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 8
Create aesthetically beautiful interfaces by following proven design principles and systematic workflows.
- Distinctive: line 51
Use chrome-devtools skill to capture full-screen screenshots (not full page)
- Distinctive: line 52
Use ai-multimodal skill to analyze screenshots and extract:
- Distinctive: line 63
Document findings in project design guidelines using templates
- Distinctive: line 67
Purpose: Create aesthetically pleasing design images through iteration.
- Distinctive: line 71
Use ai-multimodal skill to generate design images with Gemini API
- Distinctive: line 72
Use ai-multimodal skill to analyze output images and evaluate aesthetic quality
- Distinctive: line 73
If score < 7/10 or fails professional standards:
- Distinctive: line 78
Document final design decisions using templates
- Very specific: line 83
Use assets/design-guideline-template.md to document:
- Distinctive: line 119
Document decisions for consistency across development
- Distinctive: line 120
Use progressive disclosure in design—reveal complexity gradually
- Distinctive: line 121
Always evaluate aesthetic quality objectively (score ≥ 7/10)
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Aesthetic
Create aesthetically beautiful interfaces by following proven design principles and systematic workflows.
When to Use This Skill
Use when:
- Building or designing user interfaces
- Analyzing designs from inspiration websites (Dribbble, Mobbin, Behance)
- Generating design images and evaluating aesthetic quality
- Implementing visual hierarchy, typography, color theory
- Adding micro-interactions and animations
- Creating design documentation and style guides
- Need guidance on accessibility and design systems
Core Framework: Four-Stage Approach
1. BEAUTIFUL: Understanding Aesthetics
Study existing designs, identify patterns, extract principles. AI lacks aesthetic sense—standards must come from analyzing high-quality examples and aligning with market tastes.
Reference: references/design-principles.md - Visual hierarchy, typography, color theory, white space principles.
2. RIGHT: Ensuring Functionality
Beautiful designs lacking usability are worthless. Study design systems, component architecture, accessibility requirements.
Reference: references/design-principles.md - Design systems, component libraries, WCAG accessibility standards.
3. SATISFYING: Micro-Interactions
Incorporate subtle animations with appropriate timing (150-300ms), easing curves (ease-out for entry, ease-in for exit), sequential delays.
Reference: references/micro-interactions.md - Duration guidelines, easing curves, performance optimization.
4. PEAK: Storytelling Through Design
Elevate with narrative elements—parallax effects, particle systems, thematic consistency. Use restraint: "too much of anything isn't good."
Reference: references/storytelling-design.md - Narrative elements, scroll-based storytelling, interactive techniques.
Workflows
Workflow 1: Capture & Analyze Inspiration
Purpose: Extract design guidelines from inspiration websites.
Steps:
- Browse inspiration sites (Dribbble, Mobbin, Behance, Awwwards)
- Use chrome-devtools skill to capture full-screen screenshots (not full page)
- Use ai-multimodal skill to analyze screenshots and extract:
- Design style (Minimalism, Glassmorphism, Neo-brutalism, etc.)
- Layout structure & grid systems
- Typography system & hierarchy IMPORTANT: Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
- Color palette with hex codes
- Visual hierarchy techniques
- Component patterns & styling
- Micro-interactions
- Accessibility considerations
- Overall aesthetic quality rating (1-10)
- Document findings in project design guidelines using templates
Workflow 2: Generate & Iterate Design Images
Purpose: Create aesthetically pleasing design images through iteration.
Steps:
- Define design prompt with: style, colors, typography, audience, animation specs
- Use ai-multimodal skill to generate design images with Gemini API
- Use ai-multimodal skill to analyze output images and evaluate aesthetic quality
- If score < 7/10 or fails professional standards:
- Identify specific weaknesses (color, typography, layout, spacing, hierarchy)
- Refine prompt with improvements
- Regenerate with ai-multimodal or use media-processing skill to modify outputs (resize, crop, filters, composition)
- Repeat until aesthetic standards met (score ≥ 7/10)
- Document final design decisions using templates
Design Documentation
Create Design Guidelines
Use assets/design-guideline-template.md to document:
- Color patterns & psychology
- Typography system & hierarchy
- Layout principles & spacing
- Component styling standards
- Accessibility considerations
- Design highlights & rationale
Save in project ./docs/design-guideline.md.
Create Design Story
Use assets/design-story-template.md to document:
- Narrative elements & themes
- Emotional journey
- User journey & peak moments
- Design decision rationale
Save in project ./docs/design-story.md.
Resources & Integration
Related Skills
- ai-multimodal: Analyze documents, screenshots & videos, generate design images, edit generated images, evaluate aesthetic quality using Gemini API
- chrome-devtools: Capture full-screen screenshots from inspiration websites, navigate between pages, interact with elements, read console logs & network requests
- media-processing: Refine generated images (FFmpeg for video, ImageMagick for images)
- ui-styling: Implement designs with shadcn/ui components + Tailwind CSS utility-first styling
- web-frameworks: Build with Next.js (App Router, Server Components, SSR/SSG)
Reference Documentation
References: references/design-resources.md - Inspiration platforms, design systems, AI tools, MCP integrations, development strategies.
Key Principles
- Aesthetic standards come from humans, not AI—study quality examples
- Iterate based on analysis—never settle for first output
- Balance beauty with functionality and accessibility
- Document decisions for consistency across development
- Use progressive disclosure in design—reveal complexity gradually
- Always evaluate aesthetic quality objectively (score ≥ 7/10)
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.

