design-taste-frontend

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

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill design-taste-frontend-joaopaulotr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/joaopaulotr/PesquiseMaisHealth/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill design-taste-frontend-joaopaulotr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs tend to produce generic, clichéd frontend code with centered layouts, purple gradients, Inter fonts, and static components. This Skill overrides those default biases with metric-based design rules, strict component architecture, and performance guardrails so generated UI code looks intentionally designed rather than auto-generated. ## Core Features & Use Cases - Bias-Corrected Design Rules: Enforces deterministic typography, single-accent color calibration, asymmetric layouts, and bans common AI tells like neon glows, pure black, and generic placeholder data. - Configurable Design Dials: Uses DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY baselines (8/6/4) that adapt dynamically to user requests to control layout asymmetry, animation richness, and information density. - Motion & Bento Architecture: Specifies Framer Motion spring physics, perpetual micro-interactions, staggered orchestration, and a five-card Bento grid paradigm for SaaS dashboards, with strict Client Component isolation for performance. - Use Case: Ask for a SaaS analytics dashboard and receive a Next.js implementation with a Bento grid, infinitely looping status indicators, skeleton loading states, and mobile-safe responsive collapse instead of a generic three-card layout. ## Quick Start Use the design-taste-frontend skill to build a modern SaaS dashboard landing page in Next.js with Tailwind and Framer Motion.

Frequently Asked Questions about design-taste-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a non-generic React dashboard UI?

Define layout variance, motion intensity, and visual density targets, then enforce rules like asymmetric grids, single accent colors, and Bento card architecture. The Skill applies these constraints automatically when generating Next.js dashboard code with Tailwind and Framer Motion.

What fonts and colors should I use instead of Inter and purple gradients?

Use Geist, Outfit, Cabinet Grotesk, or Satoshi instead of Inter, and pair neutral Zinc or Slate bases with one desaturated accent like Emerald or Deep Rose. Serif fonts are reserved for editorial designs and banned from dashboard UIs.

Does this work with both Tailwind CSS v3 and v4?

Yes, but you must check package.json first since v3 and v4 syntax differ. For v4, use @tailwindcss/postcss or the Vite plugin instead of the tailwindcss PostCSS plugin.

Can I mix Framer Motion with GSAP or Three.js in one component?

No, never mix them in the same component tree. Use Framer Motion for UI and Bento interactions, and reserve GSAP or Three.js for isolated full-page scrolltelling or canvas backgrounds wrapped in useEffect cleanup blocks.

Why does my mobile layout break with asymmetric desktop designs?

High-variance asymmetric layouts must collapse to a strict single-column structure below 768px using w-full, px-4, and py-8. Also use min-h-[100dvh] instead of h-screen to prevent layout jumping on iOS Safari.

How do I animate magnetic hover effects without performance issues?

Use Framer Motion's useMotionValue and useTransform outside the React render cycle instead of useState for cursor tracking. Isolate perpetual animations in memoized Client Components to avoid parent re-renders.