LIFEHUBBER
Choose theme

AI Resources

Emil Kowalski Skills

GitHub stars: 42.6K GitHub forks: 2.4K Declared license: MIT: MIT Last pushed September 23, 2026: Pushed 7d ago
Stats from GitHub

Emil Kowalski Skills gives AI coding agents practical guidance for building and refining interfaces, especially their motion and small interaction details.

You can ask for a new animation, a review of existing motion, or help naming an effect you cannot quite describe. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

Instructions your coding agent can use

These are skill files for design and engineering work. They supply guidance to an agent working on your interface; they are not a standalone visual editor.

Why it stands out

Deciding where motion earns its place

The collection includes a skill that looks for worthwhile animation opportunities and rejects ones that would get in the user's way.

Availability

Browse a skill or install the collection

The public repository provides an installation command and individual skill files. Its scope also includes React Native and Expo, Swift, interface prototyping, and UI-library selection.

Why it matters

What makes it useful

If a menu feels slow or a transition feels awkward, asking an agent to make it smoother leaves much undecided. These skills bring easing, duration, and the purpose of the movement into the task so the request can become specific.

Notable points

What stands out

The opportunity-finding skill considers how often an action happens before suggesting motion. It rejects animation on repeatedly used keyboard actions and requires a purpose such as feedback or making a state change understandable. A successful result can therefore be a shorter animation wishlist.

Before using

What to review

The opportunity finder is read-only: it proposes changes rather than implementing them. Choose a build skill separately when you want code changed.

The vocabulary skill names effects; it does not design the animation. Its glossary can distinguish, for example, a fade between two images from a shape that transforms.

The author's guidance supports design judgment. The resulting interface still needs to be tried in its actual context.

Reader fit

Who may find it relevant

Frontend developers and design engineers who can inspect an agent's changes will get the clearest use from the collection. Designers can also browse the vocabulary when preparing a motion brief for a developer.

Editorial note

Why LifeHubber lists it

The useful discovery here is that an animation problem may begin before any code is written: choosing the effect, deciding whether it belongs, and implementing it are separate jobs. The collection gives each of those jobs an explicit starting point.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Compare a broader set of visual build skills.

Emil Kowalski Skills focuses on motion and interface judgment. Continue with a wider collection when the work also needs screenshots, WebGL, landing pages, frontend systems, or other reusable design workflows.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving