design-taste-frontend-v1

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

1|Updated Jan 10, 2024
One-click install
npx skills add https://github.com/noemdb/cfla --skill design-taste-frontend-v1-noemdb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/noemdb/cfla/tree/main/.agents/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/noemdb/cfla --skill design-taste-frontend-v1-noemdb

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 avoid common AI design patterns. ## Core Features & Use Cases - Design Constraint Engine: Applies tunable dials (DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY) that control layout asymmetry, animation intensity, and information density. - Anti-Pattern Enforcement: Bans Inter font, purple/blue gradients, centered heroes, 3-column card rows, emojis, generic placeholder names, and Unsplash links. - Motion & Bento Specs: Provides Framer Motion spring physics, staggered orchestration, perpetual micro-interactions, and a 5-card Bento grid architecture for SaaS dashboards. - Use Case: Ask for a SaaS pricing page or analytics dashboard, and receive Tailwind-styled React components with asymmetric layouts, skeleton loaders, empty states, and spring-based micro-animations instead of a generic centered hero. ## Quick Start Ask the AI to build a Next.js dashboard landing page using this design skill with high motion intensity and asymmetric layout.

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 accent colors to one desaturated hue, force asymmetric layouts instead of centered heroes, and require loading, empty, and error states in every component.

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 to prevent parent re-renders.

Does this work with Tailwind CSS v3 and v4?▼

Yes, but the configuration differs. Check package.json first: v4 projects must use @tailwindcss/postcss or the Vite plugin instead of the tailwindcss PostCSS plugin, and v4 syntax must not be used in v3 projects.

Can I use shadcn/ui components with these design rules?▼

Yes, shadcn/ui is allowed but never in its default state. You must customize border radii, colors, and shadows to match the project's aesthetic before shipping the components.

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

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