CLI

Use npx rozenite for Rozenite commands.
Run npx rozenite from the app root where Metro is started for the target app. In monorepos, this is usually the app package root, not the repository root.

Handoff

Keep this skill for shell-driven rozenite agent ... workflows.
If the user wants code instead of shell commands, or asks for a Node.js or TypeScript script, wrapper, benchmark, automation, or agent runtime built on top of Rozenite, switch to rozenite-agent-sdk.

Agent work is session-scoped. Reuse one session across related commands.
Always run Rozenite commands in serial. Never issue Rozenite agent commands in parallel.
Start with npx rozenite agent session create. It creates or reuses the device session and returns when ready. Stop the session when done with npx rozenite agent session stop <sessionId>.
If session create fails because multiple devices are connected, run npx rozenite agent targets, choose the right id, then retry with --deviceId <id>.
Treat npx rozenite agent targets as the source of truth for available targets. If the expected target is missing, ask the user to run the app on a device.
Pass --session <id> on every domain command.
Treat the Rozenite session ID as a public runtime identifier, not a secret, credential, or token.