design-taste-frontend

Generate React or Next.js frontend UI with Tailwind styling and interaction rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents generic, cliché frontend UI output by enforcing a consistent, metric-driven design system and interaction/animation rules that produce premium-feeling interfaces.

Core Features & Use Cases

  • Architecture & Guardrails: Enforces React/Next structural constraints (Server vs Client boundaries), Tailwind styling policy, and dependency verification so generated code fits your actual project.
  • Design Bias Correction: Applies calibrated rules for typography, layout variance, color constraints, and avoids forbidden patterns (for example, bad hero centering, oversaturated accents, and card overuse in dense dashboards).
  • Interaction & Performance Discipline: Requires complete UI state cycles (loading/empty/error/tactile feedback) and mandates performance-safe motion practices using isolated client components.

Quick Start

Ask the AI to design a premium dashboard page in Next.js with Tailwind, including loading, empty, and error states, and implementing motion micro-interactions that respect Server/Client component boundaries.

Frequently Asked Questions about design-taste-frontend

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

FAQPage Schema
How do I build a premium UI in Next.js that avoids generic dashboard layouts?

Next.js UI implementation requires enforcing React Server and Client component boundaries to isolate interactive logic, applying structural constraints that separate data fetching from stateful UX patterns to maintain safe, performance-optimized frontend architecture.

How do I implement performance-safe motion micro-interactions using Framer Motion?

Performance-safe motion micro-interactions using Framer Motion require isolating animations within dedicated client components, enforcing strict boundaries between Server and Client components to prevent hydration issues and maintain optimal rendering performance.

Does this approach support complete UI state cycles including loading, empty, and error states?

Yes, this approach supports complete UI state cycles by requiring loading, empty, error, and tactile feedback states for all generated components, ensuring stateful UX patterns are fully covered and preventing incomplete interaction designs.

What is the best way to enforce a consistent Tailwind styling policy across a React design system?

The best way to enforce a consistent Tailwind styling policy is to apply calibrated rules for typography, layout variance, and color constraints while actively avoiding forbidden patterns like oversaturated accents, ensuring a metric-driven design system output.