design-taste-frontend

Builds React/Next.js interfaces with metric-based design and Tailwind CSS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires framer-motion, tailwindcss, zustand, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating high-agency interfaces by providing a framework for enforcing metric-based design rules, ensuring a balance between visual aesthetics and functional performance.

Core Features & Use Cases

  • Metric-Based Design: Implements a strict set of design parameters for variance, motion, and visual density.
  • Architecture Conventions: Defines standards for dependency verification, framework choice, and state management.
  • Design Engineering Rules: Enforces specific typography, color, layout, and interaction patterns to counteract LLM biases.
  • Creative Proactivity: Implements advanced UI techniques like liquid glass, magnetic micro-physics, and perpetual micro-interactions.
  • Performance Guardrails: Ensures optimal performance through DOM cost optimization, hardware acceleration, and z-index management.
  • Technical Reference: Provides detailed guidance on dial definitions, visual density levels, and AI tells.
  • Creative Arsenal: Offers a collection of high-end UI inspirations, including navigation, layout, cards, scroll-animations, galleries, and typography effects.
  • Motion-Engine Bento Paradigm: Outlines a "Bento 2.0" architecture for modern SaaS dashboards and feature sections with perpetual motion and layout transitions.
  • Final Pre-Flight Check: Validates the output against a set of criteria for global state, mobile layout, full-height sections, useEffect animations, and other critical considerations.

Quick Start

Use the design-taste-frontend skill to generate a high-agency frontend interface that adheres to your specified design parameters and performance guidelines.

Frequently Asked Questions about design-taste-frontend

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

FAQPage Schema
What is high-agency UI design in React and how does it improve frontend development?

High-agency UI design in React focuses on precision design engineering, enforcing metric-based rules for motion and visual density to balance aesthetics with functional performance. It counteracts generic AI biases by enforcing specific typography, color, and interaction patterns.

Do I need Tailwind CSS and Next.js to build interfaces with metric-based design rules?

Yes, you need Tailwind CSS for styling and a React or Next.js framework. The architecture conventions also require specific dependencies like framer-motion for advanced UI techniques and zustand for state management to ensure performance guardrails.

How do I implement perpetual motion and micro-interactions in a Tailwind CSS interface?

You implement perpetual motion and micro-interactions using framer-motion alongside Tailwind CSS. The skill provides a creative arsenal of high-end UI inspirations, including magnetic micro-physics, liquid glass effects, and a motion-engine Bento paradigm for modern SaaS dashboards.

What's the best way to optimize frontend performance when using advanced UI techniques like liquid glass?

The best way to optimize frontend performance is through strict performance guardrails, including DOM cost optimization, hardware acceleration, and z-index management. A final pre-flight check validates global state, mobile layout, full-height sections, and useEffect animations.

How does this approach differ from standard Tailwind CSS component styling?

Unlike standard Tailwind CSS component styling, this approach enforces strict design engineering rules and architecture conventions. It counteracts LLM biases by defining specific visual density levels, dial definitions, and layout transition standards rather than relying on generic patterns.

Why does my React interface look generic and how can I enforce better design engineering rules?

Your React interface looks generic due to standard LLM biases in typography, color, and layout. You can enforce better design engineering rules by applying strict metric-based design parameters for variance, motion, and visual density to counteract these biases.