Loading...
Loading...
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.
npx skill4agent add software-mansion-labs/skills radon-mcpreferences/| File | When to read |
|---|---|
| When debugging any issues - call |
| Inspecting the current visual state of the app, fixing visual bugs, making UI changes |
| Understanding mounted component structure, resolving layout issues, finding context providers |
| Inspecting network requests - paginated list of all HTTP traffic coming from and into the app |
| Drilling into a specific network request's headers, body, and metadata |
| Reloading the app - choosing between JS reload, process restart, or full rebuild |
| Looking up React Native / Expo API docs from a curated knowledge base |
| Evaluating what an npm library does and whether it fits the task |