What problem does it solve? Developers who clone the HappyOyster example app risk breaking its established patterns when adding worlds, controls, or UI, because the app relies on subtle rules like per-session mode locking, phase-driven lifecycle orchestration, and held-state input handling. ## Core Features & Use Cases - Architecture Map: Documents the single client surface (useHappyOysterClient()), the connect → createWorld/attachWorld → startTravel lifecycle, and why orchestration must be phase-driven and idempotent. - Input & Transport Rules: Explains the Adventure held-input model (hold/release with key stacks and blur clearing) and the Directing transport (instruct, pause, resume, rewind with 4s snapping). - Auth & World Management: Covers the server-side API key to JWT exchange route, world creation vs instant attach via saved encryptedWorldId, and adding featured worlds via JSON entries. - Use Case: You cloned the repo and want to add a new control panel for a Directing world; the skill tells you to consume useHappyOysterClient(), gate on streaming, render instructions from travelState, and avoid rebuilding the world. ## Quick Start Ask the AI to add a new featured world or a new control component to the cloned HappyOyster app while following the patterns in this guide.
