The dog card had two intentions living in the same space.
Hovering the card meant "open this dog." Hovering the "Right for you?" action should have meant "ask about fit." Instead, the whole card moved in a way that made both actions feel too similar.
The nested action
I gave the fit CTA its own hover state.
When the pointer moves onto it, the card yields and the action becomes more chip-like. The goal is subtle, but the meaning is clearer: this is a different path from opening the listing.
The touch version
Touch devices get the quieter version at rest.
There is no hover to teach the distinction there, so the action needs to read clearly without waiting for a pointer state that will never happen.
The principle
Motion is part of information architecture.
If two gestures lead to different outcomes, they should not animate like the same object. This was a small polish pass, but it makes the card feel more precise.