design-taste-frontend-v1

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

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill design-taste-frontend-v1-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill design-taste-frontend-v1-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to fall into recognizable clichés: centered heroes, purple gradients, Inter font, generic three-card layouts, and static components with no loading or error states. This Skill encodes a strict set of design engineering rules that force the model to produce distinctive, polished React/Next.js interfaces instead of default-looking output. ## Core Features & Use Cases - Tunable design dials: DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY baselines (8/6/4) drive layout asymmetry, animation richness, and information density, and adapt to explicit user requests. - Bias-correction rules: Bans Inter, purple/blue AI gradients, pure black, 3-column card rows, emojis, and generic placeholder content, while enforcing dependency verification, Tailwind version checks, and RSC/client-component isolation. - Motion and Bento patterns: Specifies Framer Motion spring physics, staggered orchestration, perpetual micro-interactions, and five animated Bento card archetypes for SaaS dashboards, plus a creative arsenal of advanced UI concepts (magnetic buttons, scroll choreography, glassmorphism). - Use Case: Ask for a landing page or dashboard and receive code with asymmetric layouts, skeleton loaders, empty/error states, spring-physics animations, and curated typography rather than a generic template. ## Quick Start Ask the assistant to build a React dashboard or landing page and mention that it should follow the design-taste-frontend-v1 rules for layout, motion, and typography.

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 mandatory generation instructions.

How to add Framer Motion animations without hurting React performance?

Use useMotionValue and useTransform outside the React render cycle instead of useState for continuous animations, animate only transform and opacity, and isolate perpetual loops in memoized client components. Never mix GSAP or ThreeJS with Framer Motion in the same component tree.

Does this work with both Tailwind CSS v3 and v4?

Yes, but the Skill requires checking package.json first and never using v4 syntax in v3 projects. For v4, it mandates @tailwindcss/postcss or the Vite plugin instead of the legacy tailwindcss PostCSS plugin.

Can I use this with Next.js Server Components?

Yes. The Skill defaults to React Server Components and requires any interactive or animated UI to be extracted into isolated leaf components with 'use client' at the top. Global state providers must also be wrapped in a client component.

When should I use design-taste-frontend-v1 instead of the v2 version?

Use v1 only when a project depends on its exact behavior and you need backward compatibility. The current default is design-taste-frontend (v2 experimental), which is a substantial rewrite of this original skill.