js-sdk

Extend this cloned HappyOyster example app - add worlds, controls, or UI on top of the typed `@reactor-models/happy-oyster` without breaking the patterns the existing code uses. Covers the per-session mode (adventure vs directing), the connect → createWorld/attachWorld → startTravel lifecycle, the authoritative world_state snapshot, the Adventure held-input model and Directing transport, and the getJwt auth route.

Extend this cloned Helios example app — add new controls, scenes, knobs, image flows, or features on top of `@reactor-models/helios` (pinned to ^0.9.0) without breaking the patterns the existing code already uses. Covers the SDK's connection / events / messages model, the phase-based UI architecture, the state snapshot pattern, the atomic `setConditioning({ prompt, image })` command for image-to-video flows, mid-stream prompt switching, the curated scene library, and prompt design rules for smooth continuous video generation.

Extend this cloned Lingbot example app — add new controls, scenes, knobs, or features on top of `@reactor-models/lingbot` without breaking the patterns the existing code already uses. Covers the SDK's connection / events / messages model, the phase-based UI architecture, the state snapshot pattern, the image-required preconditions and the `image_accepted` wait, the WASD + arrow-key driving model, and prompt design rules for coherent continuous generation.

Extend this cloned LingBot World 2 example app — add new controls, scenes, motion patterns, or knobs on top of `@reactor-models/lingbot-world-2` without breaking the patterns the existing code uses. Covers the SDK's connection / events / messages model, the layered prompt system and its override store, the per-chunk `set_camera_pose` motion channel, the WASD + mouse-look driving model, the auth route, and clip capture.

Extend this cloned XMAX X2 example app — add new controls, sources, or knobs on top of the Reactor JS SDK without breaking the patterns the existing code uses. Covers the typed @reactor-models/x2 client, the connection / commands / messages / tracks model, the single-owner source publish, the state_update reducer, the reference-image upload path, the pointer protocol, the auth route, and clip capture.

Extend this cloned SANA-Streaming example app — add controls, presets, or stage features on top of `@reactor-models/sana-streaming` without breaking the patterns the existing code uses. Covers the SDK connection / events / messages model, the two input sources (webcam and a streamed video clip) that both feed the `camera` track, the single model-driven reducer fed by the typed `state` hook, mid-stream re-prompting (~1 chunk latency), and the behaviors to preserve — the camera publish hint and streaming a clip in rather than uploading it.

Extend this cloned LongLive 2 example app — add controls, presets, timeline features, or directing affordances on top of `@reactor-models/longlive-v2` without breaking the patterns the existing code uses. Covers the SDK connection / events / messages model, the phase-based UI (setup composer vs live director), the shot-vs-cut grammar, the per-scene 48-chunk budget and how cuts extend length, scheduling against session_chunk, the storyboard store, and the read-only timeline.