emil-design-eng

Review UI code for animation, interaction responsiveness, and polish.

Updated May 19, 2026
One-click install
npx skills add https://github.com/anilveersingh1308/copilot-skills --skill emil-design-eng-anilveersingh1308
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emil-design-eng
Source: https://github.com/anilveersingh1308/copilot-skills/tree/main/.github/skills/emil-design-eng
Command: npx skills add https://github.com/anilveersingh1308/copilot-skills --skill emil-design-eng-anilveersingh1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents UI polish and animation decisions from becoming inconsistent or purely aesthetic by grounding them in Emil Kowalski’s design engineering philosophy.

Core Features & Use Cases

  • Taste-led component engineering: Guides interface decisions toward cohesive, high-taste outcomes using trained principles rather than arbitrary preference.
  • Animation decision framework: Helps you choose whether to animate, pick easing/durations intentionally, and ensure animations feel responsive and purposeful.
  • Production-quality UI review rules: Enforces a disciplined review format and specific implementation guidelines (e.g., transitions over keyframes, origin-aware popovers, and accessibility-aware motion).
  • Use case: When redesigning an existing product UI, use the skill to systematically improve interaction feel—especially motion, micro-interactions, and component behavior—without breaking consistency.

Quick Start

Invoke the skill with /emil-design-eng and then ask it to review your UI code for animation, interaction responsiveness, and polish using its required Before/After table format.

Frequently Asked Questions about emil-design-eng

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

FAQPage Schema
How do I review and polish frontend UI animations for better interaction feel?

To polish frontend UI animations, evaluate component interaction behavior using a structured code review format that checks transitions, easing curves, and transform origins. This ensures production-ready motion patterns feel responsive and purposeful rather than purely aesthetic.

What is the best way to decide whether to animate a component interaction?

Deciding whether to animate a component interaction requires a stepwise animation decision framework that evaluates if the motion is necessary, then selects intentional easing and durations. This ensures frontend animations remain purposeful and accessibility-aware.

How do I fix inconsistent CSS transitions and micro-interactions during a UI redesign?

To fix inconsistent CSS transitions during a UI redesign, apply production-quality UI review rules using a structured Before/After table format. This enforces disciplined choices like origin-aware popovers and taste-led component engineering for cohesive outcomes.

When should I use CSS transitions instead of keyframes for frontend animations?

You should use CSS transitions instead of keyframes for frontend animations when you need responsive, state-driven component interaction behavior. Transitions provide smoother, more maintainable production-ready motion patterns for UI polish compared to rigid keyframe sequences.

Does design engineering support accessibility-aware motion for frontend components?

Yes, design engineering supports accessibility-aware motion by mandating specific implementation guidelines for frontend animations. It ensures component interaction behavior and CSS transitions respect accessibility needs while maintaining high-taste UI polish.

Why do my UI popovers and transforms feel visually broken during state changes?

Your UI popovers and transforms feel broken during state changes due to incorrect transform origin usage. Applying origin-aware component review ensures frontend animations and CSS transitions calculate their transform origin correctly for smooth visual behavior.