design-taste-frontend-v1

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

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill design-taste-frontend-v1-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/divinaarmuela/Content --skill design-taste-frontend-v1-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look generic: centered heroes, purple gradients, Inter font, three-card rows, 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 - Tunable Design Dials: DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY baselines drive layout asymmetry, animation richness, and information density across every generation. - Anti-Slop Rulebook: Bans common AI tells such as Inter font, neon glows, pure black, generic names, fake metrics, Unsplash links, and default shadcn/ui styling. - Motion & Bento Specs: Provides Framer Motion spring physics, perpetual micro-interactions, staggered orchestration, and five Bento grid card archetypes for SaaS dashboards. - Use Case: Ask for a SaaS analytics dashboard and receive a Tailwind-styled Next.js layout with asymmetric grids, Geist typography, skeleton loaders, empty states, and spring-animated Bento cards instead of a generic template. ## Quick Start Generate a modern SaaS dashboard landing page in Next.js with Tailwind and Framer Motion following the design taste rules.

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: ban default fonts like Inter in favor of Geist or Satoshi, limit accents to one desaturated color, forbid centered heroes and three-card rows, and require loading, empty, and error states. This Skill encodes those rules as mandatory generation directives.

How to add Framer Motion animations without hurting React performance?

Use useMotionValue and useTransform instead of useState for continuous animations like magnetic hover, animate only transform and opacity, and isolate perpetual loops in memoized client components. Never animate top, left, width, or height.

Does this work with both Tailwind CSS v3 and v4?

Yes, but the configuration differs. The Skill requires checking package.json first: v4 projects must use @tailwindcss/postcss or the Vite plugin instead of the tailwindcss PostCSS plugin, and v4 syntax must not be used in v3 projects.

Can I use shadcn/ui components with these design rules?

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 so the output does not resemble the stock component library look.

Why should hero sections use min-h-[100dvh] instead of h-screen?

h-screen causes layout jumping on mobile browsers like iOS Safari because the viewport height changes as toolbars show and hide. Using min-h-[100dvh] tracks the dynamic viewport and keeps full-height sections stable.