design-taste-frontend-v1

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-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 directives that force React/Next.js and Tailwind output toward distinctive, high-end interfaces with correct motion, typography, and layout decisions. ## Core Features & Use Cases - Design Bias Correction: Enforces rules against AI clichés such as neon glows, pure black, Inter font, generic names, and 3-column card layouts, with concrete replacements (Geist/Satoshi fonts, zinc bases, asymmetric grids). - Tunable Design Dials: Drives output through three configurable baselines — DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY — that control layout asymmetry, animation depth, and information density. - Motion & Bento Specifications: Provides Framer Motion spring physics, staggered orchestration, perpetual micro-interactions, and a five-archetype Bento grid pattern for SaaS dashboards, plus performance guardrails (transform-only animation, isolated client components). - Use Case: Ask for a SaaS landing page or dashboard and receive Next.js code with split-screen heroes, liquid-glass cards, magnetic buttons, skeleton loaders, and mobile-safe min-h-[100dvh] layouts instead of a generic template. ## Quick Start Ask the AI to build a React dashboard or landing page for your product and it will apply these design directives, dependency checks, and motion rules automatically.

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 directives that ban common AI patterns: no Inter font, no purple gradients, no centered heroes, no 3-column card rows. Replace them with asymmetric grids, fonts like Geist or Satoshi, neutral zinc palettes with one accent, and staggered motion reveals.

How to add Framer Motion animations without hurting performance?

Animate only transform and opacity, never top, left, width, or height. Use useMotionValue and useTransform for cursor-tracking effects instead of useState, and isolate perpetual animations in memoized client components so parent layouts never re-render.

Does this work with both Tailwind CSS v3 and v4?

Yes, but the version must be checked in package.json first. v4 syntax must not be used in v3 projects, and v4 projects must use @tailwindcss/postcss or the Vite plugin rather than the tailwindcss PostCSS plugin.

Can I use GSAP or Three.js together with Framer Motion?

Never mix them in the same component tree. Framer Motion handles UI and Bento interactions, while GSAP or Three.js are reserved for isolated full-page scrolltelling or canvas backgrounds wrapped in useEffect cleanup blocks.

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 hide. min-h-[100dvh] tracks the dynamic viewport height and keeps full-height sections stable.