design-taste-frontend-v1

Generates opinionated React and Tailwind frontend code following anti-generic design and motion rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look generic: centered heroes, purple gradients, Inter font, three-card feature rows, and missing loading or error states. This Skill encodes a strict set of design engineering rules so generated React/Next.js interfaces avoid those clichés and follow consistent typography, color, layout, and motion standards. ## Core Features & Use Cases - Tunable design dials: DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY baselines (8/6/4) drive layout asymmetry, animation richness, and spacing density, overridable per user request. - Anti-slop rulebook: Bans Inter font, neon glows, pure black, 3-column card rows, generic names like "John Doe", Unsplash links, and filler copy such as "Elevate" or "Seamless". - Motion and Bento specs: Prescribes Framer Motion spring physics, staggered orchestration, perpetual micro-interactions, and a 5-card Bento grid paradigm for SaaS dashboards, plus GSAP/Three.js guidance for scrolltelling. - Use Case: Ask for a landing page or dashboard and receive code with split-screen heroes, skeleton loaders, empty/error states, magnetic buttons, and min-h-[100dvh] mobile-safe layouts instead of default AI output. ## Quick Start Ask the AI to build a pricing page or analytics dashboard for your React app and let the skill's baseline configuration drive the design.

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, limit accents to one desaturated color, forbid centered heroes and 3-column card rows, and require loading, empty, and error states. This Skill encodes those rules as enforceable generation directives.

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

Use Framer Motion with spring physics (stiffness 100, damping 20) and layout/layoutId props for UI interactions. 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.

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.

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

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

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 look like a stock component library install.