emil-design-eng

Audit UI components and animation decisions using Emil Kowalski's design philosophy.

Updated Jan 23, 2023
One-click install
npx skills add https://github.com/s4rvessh04/portfolio --skill emil-design-eng-s4rvessh04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emil-design-eng
Source: https://github.com/s4rvessh04/portfolio/tree/main/.opencode/skills/design-animations
Command: npx skills add https://github.com/s4rvessh04/portfolio --skill emil-design-eng-s4rvessh04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill communicates a philosophy for UI polish and thoughtful animation decisions to teams and AI systems, helping designers and developers align on how to create interfaces that feel deliberate and premium.

Core Features & Use Cases

  • Establishes a shared design vocabulary focusing on invisible details that elevate user experience.
  • Guides consistent animation choices, component behavior, and micro-interactions across projects.
  • Serves as a reference when evaluating design systems, reviewing UI code, or onboarding new designers.

Quick Start

Audit a UI component for polish and animation decisions using Emil Kowalski's design engineering philosophy.

Frequently Asked Questions about emil-design-eng

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

FAQPage Schema
What is UI polish and how do micro-interactions improve design systems?

UI polish enhances user experience through invisible details and cohesive motion. Micro-interactions align component behavior across design systems, creating interfaces that feel deliberate and premium.

How do I audit a UI component for animation and polish consistency?

Audit UI components by evaluating animation choices and micro-interactions against a cohesive design philosophy. This identifies inconsistencies and enforces attention to invisible details across projects.

Can I use this approach to align developers and designers on UI animation decisions?

Yes, applying a shared design vocabulary helps designers and developers align on UI animation decisions. It establishes consistent component behavior and micro-interactions for premium interfaces.

What's the best way to establish a shared design vocabulary for micro-interactions?

The best way is adopting a cohesive design philosophy focused on invisible details. This guides consistent animation choices and micro-interactions, serving as a reference for evaluating design systems.

When should I not use a cohesive design philosophy for UI polish?

Avoid strict cohesive design philosophy when rapid prototyping requires fast iteration over consistency. Enforcing deliberate animation choices and invisible details may slow early-stage design exploration.

Does this UI polish approach work for onboarding new designers to existing design systems?

Yes, this UI polish approach works for onboarding by serving as a reference for existing design systems. New designers learn component behavior, animation choices, and micro-interactions quickly.