emil-design-eng

Encode Emil Kowalski's design engineering philosophy into UI review guidelines and animation criteria.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/misty-step/harness-kit --skill emil-design-eng-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emil-design-eng
Source: https://github.com/misty-step/harness-kit/tree/main/skills/.external/emil-emil-design-eng
Command: npx skills add https://github.com/misty-step/harness-kit --skill emil-design-eng-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies and communicates Emil Kowalski's design engineering philosophy to help teams craft polished, cohesive interfaces that feel intentional.

Core Features & Use Cases

  • Establishes a philosophy of unseen details, tasteful motion, and cohesive component design to guide UI decisions.
  • Provides practical guidelines for animation decisions, defaults, and consistency across products.
  • Used during design reviews, component audits, and UI handoffs to ensure a cohesive user experience.

Quick Start

Describe the UI you want polished, and I will apply Emil Kowalski's design engineering principles to polish it.

Frequently Asked Questions about emil-design-eng

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

FAQPage Schema
How do I polish UI components for better visual consistency?

To polish UI components for visual consistency, apply codified design engineering guidelines that enforce cohesive design language, tasteful motion, and unseen interaction details across web and mobile interfaces.

What are the best guidelines for UI animation and transitions?

The best guidelines for UI animation and transitions establish practical rules for motion decisions, default behaviors, and consistency, ensuring that animations feel intentional and cohesive throughout the product.

Can I use this for UI design reviews and component audits?

Yes, you can use this during design reviews, component audits, and UI handoffs. It provides practical evaluation criteria to enforce cohesive design language, motion guidelines, and accessibility considerations.

When do I need design engineering principles for UI handoffs?

You need design engineering principles for UI handoffs when you want to ensure a cohesive user experience by codifying interaction details, motion guidelines, and component consistency before final development.

Does this work for both web and mobile interface design?

Yes, this applies to UI components, animations, transitions, and interaction details across both web and mobile interfaces, ensuring a cohesive design language and consistent accessibility considerations.