I Built a Pokémon UI with Opus 5.5, and the Comments Asked the Key Questions

A video just under half a minute long. Pokémon-style elemental color schemes, a card-based layout, hover and click transition animations — all running on a single screen. The interface isn't stitched-together screenshots; it's actually clickable.

The poster is Chetaslua, who put it up on X on October 24. The caption is only three sentences: the Poke UI animations were done by Opus 5.5, the Pokémon images were found online, and the UI was built by hand. The last sentence is the verdict: one month after release, Opus 5.5 is still the "undefeated king."

Opus is the highest-tier model in Anthropic's Claude lineup. According to this tweet, version 5.5 has been live for just one month.

The video itself is nice to look at. But the comments are more informative than the video.

The first reply just says "creativity maxed out," which isn't much use. The second reply asks two things: how many prompts did all these animations take in total, and was the implementation done in pure CSS, or did it call an animation library like Framer Motion?

These two questions hit exactly the crux of this kind of demo.

When AI writes UI animations, the hard part has never been getting a single component to move. The real difficulty is keeping an entire set of motion effects on one consistent rhythm: how to choose easing curves, how many milliseconds apart the enter and exit durations should be, who goes first and who goes after when layers switch. In real projects, these things are backstopped by a design system, and it's very hard for a model to align all of them from a single description. That's why the number of prompts is the key metric. Getting this result in three prompts versus grinding it out in fifty prompts are two fundamentally different things: the former means the model understood the motion system, the latter only means the human had a lot of patience.

The second question is the same story. Pure CSS means the output is a stylesheet you can drop straight into a project; using Framer Motion means it pulled in an external dependency and someone still has to wire up a layer in the codebase. For frontend developers, the value of these two outcomes differs by an order of magnitude.

The author hasn't replied yet.

So for now, this video can only prove one thing: Opus 5.5 can produce good-looking motion design. As for how much manual course-correction that "good-looking" cost, there's no answer yet. Once the reply comes in, the true quality of this demo will finally be settled.