design-taste-frontend-v1

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

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill design-taste-frontend-v1-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/taste-skill-v1
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill design-taste-frontend-v1-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code often looks generic, uses clichéd layouts, and ignores performance and mobile constraints. This Skill enforces a strict set of design engineering rules so generated React/Next.js interfaces avoid common AI design patterns. ## Core Features & Use Cases - Design Baseline Configuration: Drives output through three tunable dials (DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY) that control layout asymmetry, animation level, and information density. - Anti-Pattern Enforcement: Bans common AI tells such as Inter font, purple gradients, centered heroes, 3-column card rows, emojis, and generic placeholder data. - Motion & Bento Specs: Provides concrete Framer Motion patterns including spring physics, layoutId transitions, staggered reveals, and five perpetual-motion Bento card archetypes. - Use Case: Ask the AI to build a SaaS dashboard landing page, and it will produce an asymmetric layout with Geist typography, a single desaturated accent color, skeleton loading states, and mobile-safe min-h-[100dvh] sections. ## Quick Start Ask the AI to build a pricing page or dashboard for your React app and it will apply these design 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 frontend code look less generic?

Apply explicit design constraints: ban default fonts like Inter, limit the palette to one desaturated accent color, forbid centered hero layouts, and replace 3-column card rows with asymmetric grids. This Skill encodes those rules as enforceable generation directives.

How to add Framer Motion animations without hurting React performance?

Use useMotionValue and useTransform 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 to lock the version. For v4 projects it forbids the tailwindcss PostCSS plugin and mandates @tailwindcss/postcss or the Vite plugin instead.

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.

When should I use this v1 skill instead of the v2 version?

Use this v1 install only when a project depends on its exact behavior for backward compatibility. The description states the current default is design-taste-frontend v2, which is a substantial rewrite.