design-taste-frontend-v1

Generates premium React and Next.js frontend code with enforced design rules and motion patterns.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Jatinkrmahato993203/crime --skill design-taste-frontend-v1-jatinkrmahato993203
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/Jatinkrmahato993203/crime/tree/main/skills/taste-skill-v1
Command: npx skills add https://github.com/Jatinkrmahato993203/crime --skill design-taste-frontend-v1-jatinkrmahato993203

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code often looks generic, with clichéd layouts, default fonts, purple gradients, and missing loading or error states. This Skill enforces a strict set of design engineering rules so generated React and Next.js interfaces look distinctive, polished, and production-grade. ## Core Features & Use Cases - Design Bias Correction: Bans common AI tells such as Inter font, neon glows, pure black, centered heroes, and generic 3-column card layouts, replacing them with asymmetric grids, curated font stacks, and calibrated color palettes. - Tunable Design Dials: Configures DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY levels that drive layout asymmetry, animation richness, and information density across all generated UI. - Motion & Bento Patterns: Provides concrete Framer Motion specifications including spring physics, layoutId transitions, staggered reveals, magnetic buttons, and perpetual micro-interactions for Bento-style dashboards. - Use Case: Ask for a SaaS analytics dashboard and receive a complete Next.js implementation with Tailwind styling, skeleton loading states, empty states, and animated Bento cards instead of a static generic layout. ## Quick Start Build a modern SaaS dashboard page in Next.js with Tailwind CSS, animated Bento cards, and full loading and empty states following the design taste rules.

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 to one desaturated accent color, avoid centered hero layouts, and replace 3-column card rows with asymmetric or Bento grids. This Skill encodes these rules as enforceable generation directives.

How to add Framer Motion animations to a Next.js dashboard?▼

Use spring physics with stiffness 100 and damping 20, layoutId for shared element transitions, and staggerChildren for list reveals. Interactive animated components must be isolated as Client Components with 'use client' since Server Components cannot hold motion state.

Does this work with Tailwind CSS v3 and v4?▼

Yes, but the version must be checked in package.json first. For v4, do not use the tailwindcss plugin in postcss.config.js; use @tailwindcss/postcss or the Vite plugin instead, and avoid mixing v4 syntax into v3 projects.

Why should I avoid h-screen for hero sections in mobile layouts?▼

h-screen causes layout jumping on mobile browsers like iOS Safari because the viewport height changes when browser chrome hides. Use min-h-[100dvh] instead, which tracks the dynamic viewport height and keeps full-height sections stable.

What are the limitations of this design rule approach?▼

The rules target React, Next.js, Tailwind, and Framer Motion stacks only, so other frameworks need manual adaptation. Highly opinionated bans, such as no serif fonts on dashboards, may conflict with existing brand guidelines that require different typography.