emilkowalski
15 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
emilkowalskiemil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
- instalaciones
- 343,1 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskireview-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
- instalaciones
- 217,6 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskianimation-vocabulary
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.
- instalaciones
- 203,3 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskiapple-design
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
- instalaciones
- 203 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskiimprove-animations
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
- instalaciones
- 187 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskifind-animation-opportunities
Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.
- instalaciones
- 173 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskipick-ui-library
Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.
- instalaciones
- 151,8 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskiprototype
Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.
- instalaciones
- 140,8 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskianimate
Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.
- instalaciones
- 134,4 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskiask-sonner
Guide to Sonner, the React toast library — install and wire up the Toaster, pick the right toast() call, promise and loading toasts, updating, dismissing and persisting toasts, styling, theming and icons, positioning and multiple toasters. Use when working with Sonner or troubleshooting it — toasts that don't appear, appear twice, lose their styles, ignore Tailwind classes, sit behind a modal, or don't follow dark mode.
- instalaciones
- 108,3 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskianimate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web a
- instalaciones
- 100 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskiwrite-swift
How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.
- instalaciones
- 87,6 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskibreak-ui
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use r
- instalaciones
- 3,8 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskimobile-native
Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed. Covers sticky hover states, tap highlight flashes, the 100vh bug, inputs that zoom the page, laggy taps, pull-to-refresh hijacking scroll, content under the notch, long-press selecting button text, carousels that scroll the wrong way, mismatched status bars, and the rule that you test on real hardware. Use when a web app is being built for or review
- instalaciones
- 2,1 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct
emilkowalskianimation-performance
Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Covers the layout/paint/composite pipeline, cheaper property swaps, CSS vs WAAPI vs requestAnimationFrame, Framer Motion's hardware-accelerated path, React re-rendering per frame, inherited CSS variable recalculation, blur cost, and when will-change actually helps. Use when an animation is janky, choppy, stutter
- instalaciones
- 1,2 mil
- GitHub Stars
- 45,4 mil
- Actualizado
- 11 oct