emil-design-eng

Convert Emil Kowalski's UI design philosophy into practical component and motion guidelines.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/rattamnoon/our-third-story --skill emil-design-eng-rattamnoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emil-design-eng
Source: https://github.com/rattamnoon/our-third-story/tree/main/.agents/skills/emil-design-eng
Command: npx skills add https://github.com/rattamnoon/our-third-story --skill emil-design-eng-rattamnoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams codify Emil Kowalski's philosophy of UI polish, component design, and motion decisions to create software that feels deliberate and refined.

Core Features & Use Cases

  • Philosophy-driven guidelines for taste, unseen details, and the leverage of beauty in software.
  • Explicit frameworks and checklists (Animation Decision Framework, review formats, cohesion principles) to guide design and implementation.
  • Real-world workflows for applying these principles to UI components, animations, and accessibility considerations.

Quick Start

Apply Emil Kowalski's design engineering philosophy to audit and refine your UI components for polish and motion.

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 does intentional motion improve component design?

UI polish involves refining unseen details and timing to make software feel deliberate. Intentional motion elevates component design by adding purposeful animations that enhance user experience while maintaining accessibility and performance standards.

How do I audit existing UI components for polish and motion consistency?

Audit UI components by applying an animation decision framework and cohesion principles to assess timing, polish, and invisible details. Use review formats to evaluate whether motion decisions align with your cohesive design language and accessibility requirements.

When should I use animations in my UI and when do they hurt accessibility?

Animations should be used when they add purposeful intent to UI interactions. Evaluate motion decisions against accessibility guidelines to ensure animations do not hinder users, maintaining performance and cohesive design language across products.

What is the best way to establish a consistent UI design language across product teams?

Establish consistent UI design by codifying philosophy-driven guidelines for taste and unseen details. Apply explicit frameworks, cohesion principles, and review formats to guide teams in creating deliberate, refined software with unified motion decisions.

Does this UI design philosophy work for teams building accessible web applications?

Yes, the UI design philosophy explicitly aligns with accessibility, performance, and cohesive design language. It provides practical guidelines ensuring teams adopt component design and motion decisions that elevate software feel without excluding users.