design-taste-frontend-v1

Generates React and Tailwind frontend code following opinionated design, motion, and layout rules.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill design-taste-frontend-v1-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/frontend-product-design/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/firstsun-dev/skills --skill design-taste-frontend-v1-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to fall into generic visual clichés such as centered hero sections, purple gradients, Inter font, and three-column card rows. This Skill enforces a strict set of design engineering rules so generated React and Tailwind interfaces look distinctive, polished, and consistent. ## Core Features & Use Cases - Design Bias Correction: Bans common AI tells like neon glows, pure black, generic names, and 3-column card layouts while enforcing typography, color, and spacing standards. - Tunable Design Dials: Configures DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY levels that drive layout asymmetry, animation behavior, and information density. - Motion & Bento Patterns: Provides Framer Motion spring physics, perpetual micro-interactions, and a five-card Bento grid paradigm for SaaS dashboards. - Use Case: Ask your agent to build a Next.js SaaS dashboard and receive code with asymmetric layouts, skeleton loading states, staggered reveals, and customized shadcn/ui components instead of default-looking output. ## Quick Start Ask your agent to build a React dashboard or landing page using the design-taste-frontend-v1 skill with your preferred variance and motion levels.

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 constraints such as banning centered hero layouts, limiting accent colors, and forbidding default fonts like Inter. This Skill encodes those rules so generated React and Tailwind output uses asymmetric grids, curated font stacks, and realistic content.

How to add Framer Motion animations to a Next.js app?▼

Extract interactive components into isolated Client Components with 'use client' at the top, then use Framer Motion's useMotionValue and useTransform for continuous animations. Apply spring physics with stiffness 100 and damping 20, and use layout and layoutId props for smooth transitions.

Does this work with Tailwind CSS v3 and v4?▼

Yes, but the Skill requires checking package.json first to lock the Tailwind version. For v4 projects it forbids the tailwindcss PostCSS plugin and requires @tailwindcss/postcss or the Vite plugin instead.

Can I use shadcn/ui components with this design system?▼

Yes, shadcn/ui is allowed but never in its default state. You must customize border radii, colors, and shadows to match the project's aesthetic before shipping the components.

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

The h-screen utility 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 GSAP instead of Framer Motion?▼

Use Framer Motion for UI and Bento interactions by default. Reserve GSAP or Three.js for isolated full-page scrolltelling or canvas backgrounds, and never mix them with Framer Motion in the same component tree.