Loading video...
Video Failed to Load
One skill for all UI motion. The Transitions-dev skill uses content and knowledge from the entire Transitions library and applies it to your project wherever it makes sense, for a more polished and snappy UI.
216,394 views • 1 day ago •via X (Twitter)
34 Comments

Looks smooth 🙏

Thanks!

You're one of the best accounts to follow

thanks!

Love it

Thanks Nizam

saving it

motion polish is usually the last thing teams get to, so packaging it into a skill like this makes a lot of sense

Smooth. I am also thinking about developing animation skills for myself.

Subtle and smooth

A very creative idea

I like these smooth visual effects👍

The best motion systems make interaction feel obvious, not ornamental. A shared vocabulary for transitions is a lovely way to keep that quality consistent as a product grows.

The best part is the “wherever it makes sense” constraint. Motion feels useful when it follows hierarchy instead of decorating every state.

that ui difference is actually huge

The review command is a useful starting point. Seeing where motion helps before applying it makes this easier to judge. I would rather improve a few important interactions first than add movement across the whole app.

Very sexy. Nice work.

Looks really useful will look into this and use for my project!

🆒

how does the skill determine which transitions to apply in a project?

Generic looks faster and better

The skill: "Take whatever transition duration you would have originally used and divide it in half."

legend 🙌

Perfect 🙏

S tier!!!

Ho

Polish is not intelligence. It is a library with opinions.

consolidating skills from the entire library sounds like a smart move for efficiency

Nood question does skills is automatically apply when i install it in claude? Example make website/apps via Antigravity + Claude. Sorry I’m more of a creative person so codes/ai assisted development seems kinda new to me 😭

A great way to make polished motion more accessible across every project

packaging a whole motion library as one skill is the right granularity. skills should carry taste and defaults, not api docs

Auto-applying motion where it fits sounds useful, but the hard part is knowing when not to animate.

Nice. Are you going to add more animations?

how does the skill prioritize which transitions to apply to a project?

