meteor-suit

As a visitor, I want to see an engaging landing page so that I can understand the Yatimi app and navigate to sign up, log in, or explore the animation experience.

As an animator or editor, I want to view and interact with the scene canvas so that I can place, select, and position suits within the scene layout.

As a viewer or creator, I want to browse a gallery of saved scenes and suits so that I can discover, preview, and select projects to open or replay.

As an animator, I want to preview the configured suit animation in a sandboxed environment so that I can verify motion behavior before publishing or saving the scene.

As an animator or editor, I want to configure proximity trigger zones and sensitivity settings so that the suit reacts accurately to viewer presence within defined spatial boundaries.

As a viewer, I want to watch the animated scene and trigger proximity interactions so that I can experience the suit moving in real time and replay the animation.

As an animator, I want to configure motion parameters, keyframes, and behavior settings for a selected suit so that its animation responds correctly to proximity triggers.

As a backend system, I want to expose REST API endpoints for creating, reading, updating, and deleting scenes so that the frontend can persist and retrieve scene layouts, suit placements, and metadata.

As a backend system, I want to expose API endpoints for saving and retrieving suit motion configurations and keyframe data so that animator settings persist across sessions and are available for playback.

As a backend system, I want a proximity trigger detection engine that evaluates real-time spatial input against configured trigger zones so that the correct animation sequences are dispatched when a viewer enters or exits a zone.

As a backend system, I want API endpoints that return paginated lists of published scenes and suit thumbnails so that the gallery page can display discoverable content to viewers and creators.

As an animator or editor, I want an Animation page that displays the current scene animation state and exposes controls for tuning proximity trigger zones and previewing suit motion so that I can interactively adjust and validate animation behavior before publishing.

As an editor or creator, I want an Export page that presents the finalized scene summary and provides controls to package, version, and publish the scene so that a shareable URL is generated upon successful export.

As an editor or creator, I want backend endpoints to export and publish a finalized scene so that the packaged scene bundle is stored, versioned, and made accessible to viewers via a shareable URL.

As a frontend developer, I want to connect the Canvas page to the Scene Management API so that suit placements and scene layouts are persisted and reloaded correctly across sessions.

As a frontend developer, I want to connect the Suit Editor page to the Suit Configuration API so that motion parameters and keyframes configured by the animator are saved and retrievable.

As a frontend developer, I want to connect the Proximity Settings page to the proximity trigger engine backend so that configured trigger zones are persisted and evaluated correctly at runtime.

As a frontend developer, I want to connect the Scene page to the animation engine so that proximity events received in real time drive the correct suit motion sequences rendered on the viewer's screen.

As a frontend developer, I want to connect the Preview page to the animation engine so that animators can test and validate suit motion behavior against live proximity trigger simulations before publishing.

As a frontend developer, I want to connect the Gallery page to the Gallery Data API so that published scenes and suit thumbnails are dynamically fetched and displayed with correct pagination.

As an editor or creator, I want the frontend export workflow to call the Export & Publish API so that a finalized scene is packaged, versioned, and a shareable link is returned upon successful publish.