emil-design-eng

Reviews and guides UI animation, easing, and interaction design for React and CSS interfaces.

3|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Javeria-Javaid/Alkhidmat_foundation_lahore --skill emil-design-eng-javeria-javaid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: emil-design-eng
Source: https://github.com/Javeria-Javaid/Alkhidmat_foundation_lahore/tree/main/Users/Javeria/Desktop/Alkhidmat_foundation_lahore/.agents/skills/emil-design-eng
Command: npx skills add https://github.com/Javeria-Javaid/Alkhidmat_foundation_lahore --skill emil-design-eng-javeria-javaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend interfaces often feel sluggish or unpolished because of poor animation choices: wrong easing curves, excessive durations, scale-from-zero entrances, and non-interruptible keyframes. This Skill provides concrete design engineering rules, inspired by Emil Kowalski's craft philosophy, to review and build UI motion that feels responsive and intentional. ## Core Features & Use Cases - Animation Decision Framework: Determines whether an element should animate at all based on usage frequency, then selects the correct easing curve and duration (UI animations under 300ms, custom cubic-bezier curves). - Structured UI Code Review: Produces a mandatory Before/After/Why markdown table flagging issues like transition: all, ease-in on UI elements, scale(0) entries, and missing :active press states. - Component Craft Guidance: Covers springs, popover transform-origins, tooltip delay skipping, clip-path reveals, drag gestures with velocity-based dismissal, and performance rules (transform/opacity only, hardware acceleration caveats in Framer Motion). - Use Case: When reviewing a React dropdown component, the Skill flags a 400ms ease-in transition and recommends a 200ms custom ease-out curve with origin-aware scaling, explaining the perceived-performance reasoning. ## Quick Start Ask the assistant to review your React or CSS component's animations and interaction states using the design engineering review checklist.

Frequently Asked Questions about emil-design-eng

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

FAQPage Schema
How do I make UI animations feel more responsive?▼

Use ease-out curves so movement starts immediately, keep durations under 300ms, and add scale(0.97) press feedback on :active states. Custom cubic-bezier curves like cubic-bezier(0.23, 1, 0.32, 1) feel stronger than built-in CSS easings.

How to review frontend code for animation quality?▼

Check for transition: all, scale(0) entrances, ease-in on UI elements, centered transform-origin on popovers, and durations over 300ms. This Skill outputs findings in a Before/After/Why markdown table with the reasoning for each fix.

Should I use CSS transitions or keyframes for UI animations?▼

Use CSS transitions for dynamic, rapidly-triggered UI like toasts because they can be interrupted and retargeted mid-animation. Keyframes restart from zero on interruption, which causes visible jumps in interactive elements.

Does Framer Motion hardware accelerate x and y props?▼

No. Framer Motion's shorthand x, y, and scale props run via requestAnimationFrame on the main thread. For hardware acceleration, animate the full transform string like transform: "translateX(100px)" instead.

When should I not animate a UI element?▼

Never animate keyboard-initiated actions or elements seen 100+ times per day, such as command palettes. Frequent animations make interfaces feel slow; reserve animation for occasional elements like modals, toasts, and rare delight moments.

How do I handle animations for users with reduced motion preferences?▼

Use the prefers-reduced-motion media query to remove transform-based movement while keeping opacity and color transitions that aid comprehension. Reduced motion means gentler animation, not zero animation.