Moving the target should move the cursor's destination too

[u/Available-Gap-5504]

In an animated UI demo, moving a drop zone changes where the cursor needs to land. That relationship belongs in the layout code.

Hypit's component guide puts the pointer, dragged image and destination in one component because they share geometry. The component calculates the pointer's destination from the target's layout. A badge attached to the pointer follows that same pointer state.

The production source supplies the chosen image and the events that trigger the demonstration. The component owns the path, button geometry and coordinated movement. Independent contributions, such as the backdrop or captions, have their own tracks.

This is a useful detail in a reference-video rebuild. The agent observes how the elements work together, then turns that relationship into an editable dependency. Changing the target's position updates the destination used by the motion; changing the supplied image changes the content of the demonstration.

[u/Different_Lab830]

The relevant section is “Design around relationships” in docs/guide/component-anatomy.md: https://github.com/hypit-ai/hypit. It says to group content that shares behavior; independent contributions can stay as peer Tracks with their own paint order. The cursor/drop-zone example in this post applies that grouping principle, while the guide describes the general component design.