frontend-philosophy

Guides UI styling decisions using five design pillars for typography, color, motion, spacing, and depth.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill frontend-philosophy-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-philosophy
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/frontend-philosophy
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill frontend-philosophy-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces often look generic and templated, relying on default fonts, timid color palettes, and predictable layouts. This Skill provides a structured design philosophy that helps you make intentional visual decisions and avoid generic "AI slop" aesthetics. ## Core Features & Use Cases - The 5 Pillars Framework: Covers typography with character, committed color themes, purposeful motion, brave spatial composition, and atmospheric depth. - Concrete Rules & Practices: Each pillar includes a concept, a rule (e.g., avoid Inter, Roboto, and system-ui defaults), and actionable practices such as CSS variable systems and staggered reveals. - Adherence Checklist: A five-point verification checklist to run before completing any UI task. - Use Case: When building a landing page or dashboard, apply the pillars to choose a distinctive display font, commit to a bold dominant color with sharp accents, orchestrate one high-impact animation, and layer textures or gradient meshes for depth. ## Quick Start Apply the frontend philosophy skill to redesign this page with distinctive typography, bold colors, and layered visual depth.

Frequently Asked Questions about frontend-philosophy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated UI designs look less generic?

Apply the 5 Pillars of Intentional UI: choose distinctive fonts instead of system defaults, commit to bold dominant colors, orchestrate one high-impact animation, use asymmetric or grid-breaking layouts, and layer textures or gradients for depth.

What fonts should I avoid in frontend design?

Avoid Inter, Roboto, Arial, and system-ui defaults, as they produce generic, forgettable interfaces. Instead, pair a dramatic display font with a refined, readable body font to give the interface character.

How should animations be used in UI design?

Use one well-orchestrated, high-impact animation rather than many scattered micro-interactions. Use CSS animations for plain HTML and the Motion library for React, prioritizing staggered reveals and surprising hover states.

Does this design philosophy work with React projects?

Yes, the philosophy applies to any UI composition work. For React specifically, it recommends the Motion library for animations, while plain HTML projects should rely on CSS animations.

What are the limitations of a design philosophy checklist?

The checklist guides aesthetic judgment but does not enforce accessibility, performance, or responsiveness requirements. It addresses visual character only, so pair it with technical review for contrast ratios, load performance, and mobile layouts.