emil-design-eng

Apply Emil Kowalski's design philosophy to UI polish and component decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/philipp08/talo-webapp --skill emil-design-eng-philipp08
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emil-design-eng
Source: https://github.com/philipp08/talo-webapp/tree/main/git_upload/.agents/skills/emil-design-eng
Command: npx skills add https://github.com/philipp08/talo-webapp --skill emil-design-eng-philipp08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams codify and apply Emil Kowalski's design engineering philosophy to UI polish, component decisions, and subtle interaction details, ensuring interfaces feel refined.

Core Features & Use Cases

  • Principles-based guidance for tasteful defaults, unseen details, and cohesive motion across interfaces.
  • Use it to critique UI code, specify animation decisions, and guide design reviews for improved consistency and polish.
  • Example: When reviewing a component, reference Emil's guidelines on motion, defaults, and origin-aware interactions.

Quick Start

Provide a concise critique of a UI prototype focusing on polish, animation decisions, and invisible details to make it feel cohesive.

Frequently Asked Questions about emil-design-eng

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

FAQPage Schema
How do I apply UI polish principles to improve component design aesthetics?

UI polish principles improve component design aesthetics by guiding tasteful defaults, unseen details, and cohesive motion. This approach ensures interfaces feel refined through consistent animation decisions and origin-aware interactions across all reviewed components.

What is the best way to critique UI animation decisions and invisible details?

Critiquing UI animation decisions involves referencing principles for tasteful defaults, cohesive motion, and origin-aware interactions. This method prioritizes subtle high-quality details and invisible polish to achieve consistency across interface components during design review sessions.

Does this design philosophy work for reviewing UI prototypes and onboarding designers?

This design philosophy works for UI reviews, design critique sessions, and onboarding materials for designers. It provides principles-based guidance to help teams codify tasteful defaults and subtle interaction details for consistent component decisions.

How do I ensure consistency in motion and interaction defaults across UI components?

Consistency in motion and interaction defaults is achieved by applying principles-based guidance during UI reviews. This approach codifies tasteful defaults, unseen details, and cohesive animation decisions to ensure interfaces feel refined and polished across all components.

What are the limitations of using principles-based guidance for UI polish?

Principles-based guidance for UI polish focuses on subtle details, animation decisions, and tasteful defaults rather than structural layout or functional logic. It guides reviewers to prioritize invisible details and origin-aware interactions but does not define specific component code implementations.