design-taste-frontend-v1

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

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/kaitoartz/dotfiles --skill design-taste-frontend-v1-kaitoartz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/kaitoartz/dotfiles/tree/main/dot_agents/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/kaitoartz/dotfiles --skill design-taste-frontend-v1-kaitoartz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to fall into generic patterns: centered heroes, purple gradients, Inter font, three-column card rows, and missing loading or error states. This Skill enforces a strict set of design engineering directives so generated UI code avoids these clichés and follows consistent architecture conventions. ## Core Features & Use Cases - Tunable Design Dials: Three global variables (DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY) drive layout asymmetry, animation intensity, and information density across all generated components. - Bias-Correction Rules: Bans common AI tells such as neon glows, pure black, generic names, Unsplash links, and default shadcn/ui styling, while enforcing dependency verification against package.json. - Motion & Bento Specs: Provides Framer Motion spring physics, staggered orchestration, perpetual micro-interactions, and a five-card Bento grid archetype for SaaS dashboards. - Use Case: Ask for a pricing page or analytics dashboard and receive React/Tailwind code with asymmetric layouts, skeleton loaders, empty states, and mobile-safe viewport handling instead of a generic centered template. ## Quick Start Use the design-taste-frontend-v1 skill to build a Next.js SaaS dashboard with a bento grid layout and animated status cards.

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 generate a non-generic React landing page with AI?▼

Apply bias-correction rules that ban centered heroes, Inter font, purple gradients, and three-column card rows. Use asymmetric split-screen layouts, fonts like Geist or Satoshi, a single desaturated accent color, and staggered reveal animations instead.

What Framer Motion patterns work best for dashboard animations?▼

Use spring physics with stiffness 100 and damping 20, layoutId for shared element transitions, and staggerChildren for list reveals. Keep perpetual animations in isolated memoized client components and never drive continuous motion with React useState.

Can I use Tailwind CSS v4 syntax in a v3 project?▼

No, check package.json first and match the installed Tailwind version. For v4, do not use the tailwindcss plugin in postcss.config.js; use @tailwindcss/postcss or the Vite plugin instead.

Why does my full-height hero section jump on mobile Safari?▼

The h-screen utility uses 100vh, which changes as mobile browser chrome appears and disappears, causing layout jumps. Use min-h-[100dvh] instead so the section tracks the dynamic viewport height.

When should I use GSAP instead of Framer Motion in React?▼

Use Framer Motion for UI and bento interactions, and reserve GSAP or ThreeJS for isolated full-page scrolltelling or canvas backgrounds. Never mix GSAP or ThreeJS with Framer Motion in the same component tree, and wrap them in useEffect cleanup blocks.