design-taste

Defines canonical interface taste values governing visual, layout, motion, and interaction design decisions.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-taste-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/design-taste
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-taste-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI models make inconsistent, tasteless design choices — dense layouts, bouncy animations, gimmicky interactive widgets, and arbitrary accent colors. This Skill provides a single source of truth for one designer's interface taste so every visual, layout, motion, and interaction decision follows the same standard. ## Core Features & Use Cases - Taste tokens as law: Seven verbatim commitments covering minimalism, generous whitespace, larger type, cut-don't-shrink layout, accessibility-first, single restrained accent, and white/airy defaults. - Motion governance: A locked four-curve cubic-bezier system with 0% overshoot and fixed duration tiers, split into a presentation register (system-driven) and a gesture register (spring physics for direct manipulation). - Calibration cases and decision procedure: Real rejected design cases plus an ordered decision checklist and anti-pattern table for evaluating any proposed UI. - Use Case: Before building a landing page hero animation, load this Skill to confirm the motion stays small and content-shaped, uses the locked settle curve, and avoids any user-operated gimmick widget. ## Quick Start Load the design-taste skill before making any visual, layout, motion, or interaction decision and check the proposal against its taste tokens and decision procedure.

Frequently Asked Questions about design-taste

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

FAQPage Schema
How do I apply consistent design taste when building UI with an AI model?

Load this Skill before any visual, layout, motion, or interaction decision. It provides seven taste tokens, an ordered decision procedure, and a quick self-check checklist that the model applies to every design choice.

What motion curves and durations should UI animations use?

Presentation motion uses four locked cubic-bezier curves with 0% overshoot: entrances use cubic-bezier(.22,1,.36,1), exits cubic-bezier(.4,0,1,1), with durations tiered at 150-250ms, 350-450ms, and 550-800ms. Direct-manipulation gestures use critically-damped springs instead.

When are spring animations allowed in interface design?

Springs are allowed only in the gesture register, when the user directly manipulates a surface with a pointer or gesture, such as dragging a sheet or swiping a card. System-driven presentation motion must use the locked curves with zero overshoot.

Does this Skill replace motion implementation or token system skills?

No. It is the single source of truth for taste values only. Sibling skills like craft-motion own animation technique and build-token-system encodes values as tokens; they reference this file and must never restate its values.

Why are interactive widgets and draggable elements flagged as risky?

User-operated widgets whose purpose is cleverness read as gimmicks and shift the register from presentation to playground. The Skill requires proposing a narrated, system-driven version instead, except for genuinely real interactions like a live AI or working product embed.