design-taste-frontend-v1

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill design-taste-frontend-v1-danieliudi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill design-taste-frontend-v1-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to look generic: centered heroes, purple gradients, Inter font, three-card rows, and missing loading or error states. This Skill enforces a detailed set of design engineering rules so generated React and Next.js interfaces avoid those clichés and follow consistent typography, color, layout, and motion standards. ## Core Features & Use Cases - Tunable design dials: DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY baselines drive layout asymmetry, animation level, and information density per generation. - Bias-correction rules: Bans Inter font, purple glows, pure black, 3-column card rows, generic names, and fake data; mandates dependency checks against package.json, Tailwind version guards, and min-h-[100dvh] viewport safety. - Motion and Bento patterns: Specifies Framer Motion spring physics, staggered orchestration, perpetual micro-interactions, and five animated Bento card archetypes for SaaS dashboards. - Use Case: Ask for a SaaS analytics dashboard and receive a Bento-grid layout with infinite-loop micro-animations, isolated client components, skeleton loaders, and empty states instead of a static card page. ## Quick Start Ask the AI to build a React dashboard or landing page and it will apply these design, motion, and anti-cliché rules to the generated code.

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, limit accent colors, forbid centered hero layouts and 3-column card rows, and require asymmetric grids. This Skill encodes those rules plus motion and state requirements for every generation.

What animation library should I use for React micro-interactions?▼

Use Framer Motion with spring physics (stiffness 100, damping 20) and layoutId for shared element transitions. For magnetic hover effects, use useMotionValue and useTransform instead of useState to avoid re-render performance problems.

Does this work with both Tailwind CSS v3 and v4?▼

Yes, but you must check 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 does my mobile hero section jump when the page loads?▼

Using h-screen for full-height sections causes layout jumps on mobile browsers like iOS Safari because the viewport height changes with the URL bar. Use min-h-[100dvh] instead for stable full-height layouts.

Can I mix GSAP and Framer Motion in the same component?▼

No. Never mix GSAP or ThreeJS with Framer Motion in the same component tree. Use Framer Motion for UI and Bento interactions, and reserve GSAP or ThreeJS for isolated full-page scrolltelling or canvas backgrounds with strict useEffect cleanup.