Use Rozenite for Agents through CLI-driven `rozenite agent` commands to inspect React Native DevTools data and Rozenite plugins on a live app target. Trigger this skill for shell-based debugging and live session work. For Node.js or TypeScript scripts, wrappers, automations, or other programmatic SDK usage, use `rozenite-agent-sdk` instead.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use Rozenite for Agents through CLI-driven `rozenite agent` commands to inspect React Native DevTools data and Rozenite plugins on a live app target. Trigger this skill for shell-based debugging and live session work. For Node.js or TypeScript scripts, wrappers, automations, or other programmatic SDK usage, use `rozenite-agent-sdk` instead.
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.
Rules
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.
Use this skill and its domains/*.md references as the source of truth for workflow, tool choice, and tool arguments.
If this skill or a domain reference already identifies the expected domain, try it directly. If a reference already lists the exact tool and arguments you need, call it directly.
Discover domains from the live session with npx rozenite agent domains --session <id> only if a domain call fails, the expected domain is unclear, or you need to confirm what is currently registered.
Do not call npx rozenite agent <domain> tools or fetch tool schema when this skill or its references already provide the needed tool name and arguments.
Check npx rozenite agent <domain> tools --session <id> or npx rozenite agent <domain> schema --tool <name> --session <id> only when no matching reference exists, the references do not answer the question, a call fails, or the live domain exposes behavior that differs from the references.
Skip confirmation or discovery steps that do not add new information.
For live app inspection, Rozenite session data is the source of truth. Use the relevant live domain before exploring source code.
Trust that Rozenite is correctly installed. Do not explore the codebase for setup unless the Rozenite CLI fails.
Do not explore the codebase to infer live runtime state when Rozenite can answer directly.
Explore source code only when the user asks about implementation or setup, when no relevant domain is available, or when Rozenite shows the required plugin or domain is not registered and the task becomes setup or debugging.
If the expected plugin domain is missing from the live session, tell the user that the corresponding plugin must be installed and registered in the app.
When referring to plugin domains in user-facing output, use the plugin's pluginId instead of the domain token.
When making Rozenite calls against a discovered plugin domain, use the live domain token returned by Rozenite.
Built-in domains are console, network, react, performance, and memory.
Additional domains can appear at runtime from the app or installed plugins. Plugin domain tokens are short, derived names, not the npm package name: @rozenite/mmkv-plugin becomes mmkv, @avasapp/rozenite-plugin-ably becomes avasapp/ably.
Domain token shape tells you provenance: a bare word (mmkv) is a built-in or an official @rozenite/* plugin; scope/name (avasapp/ably) is a third-party scoped plugin; a verbatim rozenite-* name is a third-party unscoped plugin. evil/mmkv and mmkv are never the same plugin.
Calls
Do not pass domain tool names as direct CLI subcommands.
If a command fails with Unknown domain action, check the CLI syntax and retry with call --tool <toolName> --session <id>.
Flow
Run Rozenite commands one at a time.
Use npx rozenite agent targets as the source of truth for available targets when device selection matters. If the expected target is missing, ask the user to run the app on a device.
Run npx rozenite agent session create.
If a matching file exists under domains/*.md, read it.
If the reference already lists the needed tool and arguments for the expected domain, call it directly.
Run npx rozenite agent domains --session <id> only if the call fails, the expected domain is unclear, or you need to confirm what is currently registered.
If the expected plugin domain is missing, tell the user to install and register the corresponding plugin in the app.
Check npx rozenite agent <domain> tools --session <id> or npx rozenite agent <domain> schema --tool <name> --session <id> only if the reference is insufficient, the call fails, or you need to confirm a live mismatch.
Fall back to source-code exploration only if no relevant domain exists or the task is about implementation or setup.
When no further Rozenite calls are needed, stop the session with npx rozenite agent session stop <sessionId>.
