taste

Enforce metric-driven UI/UX rules for React and Next.js interfaces.

110|14|Updated May 12, 2026
One-click install
npx skills add https://github.com/EliasOulkadi/shokunin --skill taste-eliasoulkadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taste
Source: https://github.com/EliasOulkadi/shokunin/tree/main/.pack/skills/taste
Command: npx skills add https://github.com/EliasOulkadi/shokunin --skill taste-eliasoulkadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Taste helps you avoid sloppy, templated UI decisions by enforcing metric-based layout, typography, motion, accessibility, and dependency-verified frontend engineering rules.

Core Features & Use Cases

  • Bias-correct UI architecture: Drives consistent component structure (interactive motion isolated as leaf client components), deterministic styling rules, and layout diversity (anti-center bias when variance is high).
  • Performance-first motion & accessibility: Mandates GPU-safe animation constraints (transform/opacity), requires prefers-reduced-motion handling, and defines loading/empty/error/success UI states.
  • Palette and typography calibration: Enforces neutral tinted neutrals, single controlled accent, OKLCH preference, and bans display-font/typography anti-patterns for dashboards.

Quick Start

Ask the agent to produce a React/Next.js UI design and implementation plan that follows the taste rules, including dependency verification, metric-based spacing, and all required UI states for the specified screen.

Frequently Asked Questions about taste

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

FAQPage Schema
How do I prevent AI generated React components from looking like generic templates?

Bias-resistant UI design enforces metric-driven layout rules, anti-center bias variance, and deterministic styling to prevent generic templated React component outputs. It isolates interactive motion as leaf client components for consistent frontend architecture.

What's the best way to manage motion and accessibility in a Next.js design system?

Performance-safe motion in a Next.js design system requires GPU-safe transform and opacity constraints, strict prefers-reduced-motion handling, and complete loading, empty, error, and success UI states. This ensures accessible frontend architecture.

How do I calibrate typography and color palettes for a dashboard interface?

Typography and color calibration for dashboards uses OKLCH preference, neutral tinted neutrals, and a single controlled accent. This approach bans display-font anti-patterns to ensure clear, accessible interface rendering.

Do I need to verify dependencies before adding libraries to my React UI architecture?

Dependency verification is required before importing libraries into your React UI architecture. This process enforces version-safe Tailwind styling and prevents performance degradation or conflicts within your design system.

Why does my AI generated UI lack proper loading and error states?

Complete UI state design requires explicitly defining loading, empty, error, and success states. AI generated UI often lacks these states unless strictly mandated by metric-driven frontend architecture rules.