/radon-mcp
Best practices for using Radon IDE's MCP tools when developing, debugging, and inspecting React Native and Expo apps. Use when interacting with a running app through Radon IDE - viewing screenshots, reading logs, inspecting the component tree, debugging network requests,
$ npx -y skills add software-mansion-labs/skills --skill radon-mcp --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/radon-mcp
Context preview
The summary Claude sees to decide when to auto-load this skill.
Best practices for using Radon IDE's MCP tools when developing, debugging, and inspecting React Native and Expo apps. Use when interacting with a running app through Radon IDE - viewing screenshots, reading logs, inspecting the component tree, debugging network requests,
SKILL.md
radon-mcp.SKILL.mdname: radon-mcp
description: "Best practices for using Radon IDE's MCP tools when developing, debugging, and inspecting React Native and Expo apps. Use when interacting with a running app through Radon IDE - viewing screenshots, reading logs, inspecting the component tree, debugging network requests, reloading the app, or querying React Native documentation and library info. Trigger on: 'debug React Native', 'fix UI', 'network issues', 'build issues', 'Radon IDE', 'view screenshot', 'app logs', 'component tree', 'network inspector', 'reload app', 'React Native docs', 'library description', 'emulator', 'development viewport', 'view_screenshot', 'view_application_logs', 'view_component_tree', 'reload_application', 'view_network_logs', 'view_network_request_details', 'query_documentation', 'get_library_description', and every request involving live app inspection, debugging or development in a Radon IDE session."
Radon IDE MCP Tools
Best practices for Radon IDE's MCP tools for live React Native / Expo app inspection and debugging.
Read the relevant reference for the tool at hand. All references are in `references/`.
References
| File | When to read | | -------------------------------------------- | -------------------------------------------------------------------------------------------------- | | `references/view-application-logs.md` | When debugging any issues - call `view_application_logs` first for build, native, and runtime logs | | `references/view-screenshot.md` | Inspecting the current visual state of the app, fixing visual bugs, making UI changes | | `references/view-component-tree.md` | Understanding mounted component structure, resolving layout issues, finding context providers | | `references/view-network-logs.md` | Inspecting network requests - paginated list of all HTTP traffic coming from and into the app | | `references/view-network-request-details.md` | Drilling into a specific network request's headers, body, and metadata | | `references/reload-application.md` | Reloading the app - choosing between JS reload, process restart, or full rebuild | | `references/query-documentation.md` | Looking up React Native / Expo API docs from a curated knowledge base | | `references/get-library-description.md` | Evaluating what an npm library does and whether it fits the task |
Read more
name: radon-mcp description: "Best practices for using Radon IDE's MCP tools when developing, debugging, and inspecting React Native and Expo apps. Use when interacting with a running app through Radon IDE - viewing screenshots, reading logs, inspecting the component tree, debugging network requests, reloading the app, or querying React Native documentation and library info. Trigger on: 'debug React Native', 'fix UI', 'network issues', 'build issues', 'Radon IDE', 'view screenshot', 'app logs', 'component tree', 'network inspector', 'reload app', 'React Native docs', 'library description', 'emulator', 'development viewport', 'view_screenshot', 'view_application_logs', 'view_component_tree', 'reload_application', 'view_network_logs', 'view_network_request_details', 'query_documentation', 'get_library_description', and every request involving live app inspection, debugging or development in a Radon IDE session."
Radon IDE MCP Tools
Best practices for Radon IDE's MCP tools for live React Native / Expo app inspection and debugging.
Read the relevant reference for the tool at hand. All references are in `references/`.
References
| File | When to read | | -------------------------------------------- | -------------------------------------------------------------------------------------------------- | | `references/view-application-logs.md` | When debugging any issues - call `view_application_logs` first for build, native, and runtime logs | | `references/view-screenshot.md` | Inspecting the current visual state of the app, fixing visual bugs, making UI changes | | `references/view-component-tree.md` | Understanding mounted component structure, resolving layout issues, finding context providers | | `references/view-network-logs.md` | Inspecting network requests - paginated list of all HTTP traffic coming from and into the app | | `references/view-network-request-details.md` | Drilling into a specific network request's headers, body, and metadata | | `references/reload-application.md` | Reloading the app - choosing between JS reload, process restart, or full rebuild | | `references/query-documentation.md` | Looking up React Native / Expo API docs from a curated knowledge base | | `references/get-library-description.md` | Evaluating what an npm library does and whether it fits the task |
Software Mansion's set of skills for AI-assisted React Native development.
Repo: software-mansion-labs/skills
Other skills on software-mansion-labs-skills.
- /detour-onboarding
Complete onboarding guide for developers who are new to Detour, the open-source deferred deep linking SDK by Software Mansion. Use this skill whenever a user asks what Detour is, how to get started with Detour, how to set up deep linking with Detour, how to install the Detour
Open skill - /migrate-to-detour
Use when the user mentions migrating deep links, switching away from Branch or AppsFlyer, replacing their deep linking SDK, setting up Detour deep linking for the first time, or asks how Branch/AppsFlyer concepts map to Detour. Covers the complete migration end to end - Detour
Open skill - /expo-horizon
Software Mansion's guide for migrating Expo SDK apps to Meta Quest using expo-horizon packages. Use when adding Meta Quest or Meta Horizon OS support to an existing Expo or React Native project. Trigger on: Meta Quest, Horizon OS, Quest 2, Quest 3, Quest 3S, VR app,
Open skill - /fishjam
Software Mansion's Fishjam — hosted WebRTC platform for video, audio, and one-to-many livestreaming. MUST USE before writing, reviewing, or debugging ANY code that talks to a Fishjam instance from a backend (Node, Python) or a client (React web, React Native / Expo). Routes to
Open skill - /js-server-sdk
Node.js / TypeScript server SDK for Fishjam — backends that create rooms, mint peer tokens, listen to server notifications, and run agents. Use when writing a Node.js / Express / Fastify / Hono / NestJS backend that talks to Fishjam, sets up a webhook receiver, runs an AI agent,
Open skill - /platform
Fishjam platform fundamentals — domain model and auth shared by all SDKs. Covers glossary (room, peer, track, agent, streamer, viewer), the four room types (conference / audio_only / livestream / audio_only_livestream), two-tier auth (management vs peer tokens), Sandbox vs
Open skill

