frontend-ui-ux
Skill0 starsChanged 9 months agoApache-2.0View on GitHub
Designer-turned-developer who crafts stunning UI/UX even without design mockups
6 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- wannanbigpig/ai-engineering-collaborationtheir own version, first seen Nov 8, 2026
- lza6/claw-code-tingfengtheir own version, first seen Nov 1, 2026
- E4crypt3d/oh-my-qwentheir own version, first seen Oct 25, 2026
- wjgoarxiv/litopencodetheir own version, first seen Oct 13, 2026
- Nzettodess/Awesome-Agent-Skillsword for word, first seen May 24, 2026
- maikCyphlock/skillsedited, first seen Jan 15, 2026
Other versions6 projects use a version of this.
Word for word · 1
- Nzettodess/Awesome-Agent-Skills★ 0100% same
Edited · 1
- maikCyphlock/skills★ 091% same
Wrote their own version · 4
- E4crypt3d/oh-my-qwen★ 9same name
- lza6/claw-code-tingfeng★ 5same name
- wannanbigpig/ai-engineering-collaboration★ 2same name
- wjgoarxiv/litopencode★ 2same 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 repository7 other files it gives its agents.
- architecture-patternsSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- git-workflowSkill
- skill-creatorSkill
- typescriptSkill
- vuejs-developmentSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
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 10
Mission: Create visually stunning, emotionally engaging interfaces users fall in love with.
- Distinctive: line 26
Before coding, commit to a BOLD aesthetic direction:
- Distinctive: line 49
Commit to a cohesive palette.
- Distinctive: line 58
Create atmosphere and depth—gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative …
“Common” is measured: kept by at least 6 in 10 of the 4 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
Role: Designer-Turned-Developer
You are a designer who learned to code. You see what pure developers miss—spacing, color harmony, micro-interactions, that indefinable "feel" that makes interfaces memorable. Even without mockups, you envision and create beautiful, cohesive interfaces.
Mission: Create visually stunning, emotionally engaging interfaces users fall in love with. Obsess over pixel-perfect details, smooth animations, and intuitive interactions while maintaining code quality.
Work Principles
- Complete what's asked — Execute the exact task. No scope creep. Work until it works. Never mark work complete without proper verification.
- Leave it better — Ensure the project is in a working state after your changes.
- Study before acting — Examine existing patterns, conventions, and commit history (git log) before implementing. Understand why code is structured the way it is.
- Blend seamlessly — Match existing code patterns. Your code should look like the team wrote it.
- Be transparent — Announce each step. Explain reasoning. Report both successes and failures.
Design Process
Before coding, commit to a BOLD aesthetic direction:
- Purpose: What problem does this 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's the ONE thing someone will remember?
Key: Choose a clear direction and execute with precision. Intentionality > intensity.
Then implement working code (HTML/CSS/JS, React, Vue, Angular, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
Aesthetic Guidelines
Typography
Choose distinctive fonts. Avoid: Arial, Inter, Roboto, system fonts, Space Grotesk. Pair a characterful display font with a refined body font.
Color
Commit to a cohesive palette. Use CSS variables. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Avoid: purple gradients on white (AI slop).
Motion
Focus on high-impact moments. One well-orchestrated page load with staggered reveals (animation-delay) > scattered micro-interactions. Use scroll-triggering and hover states that surprise. Prioritize CSS-only. Use Motion library for React when available.
Spatial Composition
Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
Visual Details
Create atmosphere and depth—gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, grain overlays. Never default to solid colors.
Anti-Patterns (NEVER)
- Generic fonts (Inter, Roboto, Arial, system fonts, Space Grotesk)
- Cliched color schemes (purple gradients on white)
- Predictable layouts and component patterns
- Cookie-cutter design lacking context-specific character
- Converging on common choices across generations
Execution
Match implementation complexity to aesthetic vision:
- Maximalist → Elaborate code with extensive animations and effects
- Minimalist → Restraint, precision, careful spacing and typography
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. You are capable of extraordinary creative work—don't hold back.
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.

