design-taste-frontend-v1

Generates React and Next.js frontend code following opinionated design, motion, and typography rules.

2|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/myrson2/eMSME --skill design-taste-frontend-v1-myrson2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/myrson2/eMSME/tree/main/.agents/.agents/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/myrson2/eMSME --skill design-taste-frontend-v1-myrson2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code often looks generic, with cliché layouts, default fonts, purple gradients, and missing loading or error states. This Skill enforces a strict set of design engineering rules so generated React and Next.js interfaces look distinctive, polished, and production-consistent. ## Core Features & Use Cases - Design Dial System: Configurable DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY levels (default 8/6/4) that drive layout asymmetry, animation richness, and information density. - Anti-Slop Rules: Bans Inter font, purple/blue AI gradients, centered hero sections, 3-column card rows, emojis, and generic placeholder content like "John Doe" or Unsplash links. - Motion & Bento Patterns: Provides Framer Motion spring physics specs, perpetual micro-interactions, staggered orchestration, and five Bento grid card archetypes with infinite-loop animations. - Use Case: Ask the AI to build a SaaS dashboard landing page, and it will produce an asymmetric hero, Geist typography, liquid-glass cards with spring-physics micro-animations, and complete loading/empty/error states instead of a generic template. ## Quick Start Ask the AI to build a React dashboard or landing page and it will apply these design rules, motion specs, and typography constraints automatically.

Frequently Asked Questions about design-taste-frontend-v1

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

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

Apply explicit design constraints: ban default fonts like Inter in favor of Geist or Satoshi, forbid centered hero layouts and 3-column card rows, limit accents to one desaturated color, and require loading, empty, and error states in every component.

What animation library should I use for React micro-interactions?▼

Use Framer Motion with spring physics (stiffness 100, damping 20) for UI interactions, and useMotionValue with useTransform for cursor-tracking effects to avoid re-render performance issues. Reserve GSAP or Three.js for isolated scroll-driven or canvas scenes.

Does this work with Tailwind CSS v3 and v4?▼

Yes, but you must check package.json first and never mix syntax versions. For Tailwind v4, use @tailwindcss/postcss or the Vite plugin instead of the legacy tailwindcss PostCSS plugin.

Why should I avoid h-screen for hero sections on mobile?▼

h-screen causes layout jumping on mobile browsers like iOS Safari because the viewport height changes as browser chrome hides. Use min-h-[100dvh] instead for stable full-height sections.

When should I use this v1 skill instead of the v2 version?▼

Use this v1 install only when a project depends on its exact behavior and you need backward compatibility. The default design-taste-frontend v2 is a substantial rewrite and is the recommended current version.