design-taste-frontend-v1

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill design-taste-frontend-v1-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/design/design-taste-frontend-v1
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill design-taste-frontend-v1-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code often looks generic, uses clichéd layouts, and ignores performance pitfalls. This Skill enforces a strict set of design engineering rules so generated React/Next.js interfaces avoid common AI design tells and follow consistent typography, color, layout, and motion standards. ## Core Features & Use Cases - Tunable Design Dials: DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY parameters (default 8/6/4) drive layout asymmetry, animation richness, and information density. - Bias-Correction Rules: Bans Inter font, purple gradients, centered heroes, 3-column card rows, pure black, and generic placeholder data to avoid AI slop patterns. - Motion & Bento Specs: Defines Framer Motion spring physics, perpetual micro-interactions, staggered orchestration, and a 5-card Bento grid archetype for SaaS dashboards. - Use Case: Ask your agent to build a SaaS landing page or dashboard; it will produce Tailwind-styled React components with asymmetric layouts, liquid glass effects, and performance-safe animations instead of a generic template. ## Quick Start Ask your agent to build a modern SaaS dashboard with a bento grid layout using this frontend design skill.

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 frontend code look less generic?

Apply explicit design rules that ban common AI tells: no Inter font, no purple gradients, no centered heroes, no 3-column card rows, and no generic placeholder names. This Skill encodes those bans plus asymmetric layout and motion defaults for React and Tailwind output.

What do DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY control?

They are 1-10 dials driving generation behavior. DESIGN_VARIANCE controls layout asymmetry, MOTION_INTENSITY controls animation richness from static to scroll choreography, and VISUAL_DENSITY controls spacing from airy gallery style to packed cockpit dashboards. Defaults are 8, 6, and 4.

Can I use Framer Motion and GSAP together in one component?

No. The rules forbid mixing GSAP or Three.js with Framer Motion in the same component tree. Use Framer Motion for UI and bento interactions, and reserve GSAP or Three.js for isolated full-page scrolltelling or canvas backgrounds wrapped in useEffect cleanup.

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. The Skill mandates min-h-[100dvh] for full-height sections to keep layouts stable.

Does this work with both Tailwind CSS v3 and v4?

Yes, but you must check package.json first and not mix syntax. For v4, do not use the tailwindcss plugin in postcss.config.js; use @tailwindcss/postcss or the Vite plugin instead.