domains / families / design / emil-design-eng

emil-design-eng

combined

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great. Use when designing or reviewing polished product UI with Emil Kowalski-inspired animation, interaction, and component craft guidance.

When to use

• Use when the user asks for UI polish, product design critique, animation direction, or high-craft component decisions.
• Use when reviewing frontend code for motion quality, easing, duration, physicality, interaction feedback, or subtle interface details.
• Use when building or refining React, Tailwind, CSS, or Framer Motion interfaces where taste and perceived quality matter.

When not to use

• This skill provides design engineering judgment; it does not replace project-specific product requirements, accessibility testing, or real-device motion review.
• Verify framework versions, installed dependencies, and rendered behavior before treating animation or UI recommendations as production-ready.
• Do not apply these rules mechanically when an existing brand system, platform convention, or user requirement calls for a different interaction language.

Skill page

Conflict

The first copy is the actual procedure, containing the specific review format, animation decision framework, and easing curves. The second copy is a wrapper that delegates to a 'detailed guide' and adds usage constraints and limitations not present in the first. Because the second copy contains material constraints (limitations, when to use) that the first lacks, and the first contains the actual steps the second lacks, crowning one would hide a real alternative or lose critical context.