frontend-philosophy
Skill2 starsChanged 53 days agoMITView on GitHub
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 1337hero/faster-chattheir own version, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 1337hero/faster-chat★ 176same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-philosophySkill
- code-reviewSkill
- plan-protocolSkill
- plan-reviewSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 16
Rule: Avoid Inter, Roboto, Arial, and system-ui defaults.
- Distinctive: line 21
Rule: Use bold, dominant colors with sharp accent contrasts.
- Distinctive: line 27
Practice: Use CSS animations for HTML, Motion library for React.
- Distinctive: line 37
Practice: Add dramatic shadows, decorative borders, grain overlays.
- Distinctive: line 42
Before completing your task, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Frontend Design Philosophy: The 5 Pillars of Intentional UI
Role: Design Director for all Visual & Aesthetic decisions — applies to styling, layout, colors, typography, animations, and UI composition.
Philosophy: Distinctive, memorable, intentional design — avoiding generic "AI slop" aesthetics through bold, characterful choices that create immediate emotional impact.
The 5 Pillars
1. Typography with Character
- Concept: Fonts set the entire tone. Generic fonts create generic, forgettable interfaces.
- Rule: Avoid Inter, Roboto, Arial, and system-ui defaults. Choose distinctive, characterful typefaces.
- Practice: Pair dramatic display fonts with refined, readable body fonts.
2. Committed Color & Theme
- Concept: Timid palettes lack impact and feel algorithmically generated.
- Rule: Use bold, dominant colors with sharp accent contrasts. Avoid evenly-distributed rainbow gradients.
- Practice: Establish CSS variable systems early. Break away from the "purple gradient on white" AI cliché.
3. Purposeful Motion
- Concept: Animation should delight, not distract. Scattered micro-interactions create noise.
- Rule: One well-orchestrated animation beats a dozen minor transitions. Focus on high-impact moments.
- Practice: Use CSS animations for HTML, Motion library for React. Prioritize staggered reveals and surprsing hover states.
4. Brave Spatial Composition
- Concept: Predictable layouts are forgettable. Safe spacing feels automated.
- Rule: Either generous negative space OR controlled density — not the middle ground.
- Practice: Embrace asymmetry, overlap, diagonal flow, and grid-breaking elements.
5. Atmosphere & Depth
- Concept: Flat solid backgrounds lack presence and feel unfinished.
- Rule: Layer visual richness through gradient meshes, noise textures, geometric patterns, and transparencies.
- Practice: Add dramatic shadows, decorative borders, grain overlays.
Adherence Checklist
Before completing your task, verify:
- Typography: Did you avoid generic system fonts?
- Color: Are the color choices bold and intentional?
- Motion: Is there a primary, high-impact animation?
- Space: Does the layout feel designed rather than templated?
- Depth: Is there visual richness (textures, gradients, layering)?
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.

