argent-react-native-app-workflow
Agent workflowssoftware-mansion/argentskills.sh ↗
Installs
14,940
deduplicated, at the last sync
Since we started
+4.7%
40 readings, about 2 hours apart. Not a live curve.
Our category
Agent workflows
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill provides comprehensive, step-by-step workflows for developing and debugging React Native applications on both iOS simulators and Android emulators. It guides users through starting the Metro server, running the app, handling build failures, and diagnosing runtime errors using various specialized tools.
- A running React Native application
- Debugging logs or component tree structure
- Project's build and run configuration (from `argent-environment-inspector`)
not detected
The evidence does not contain any information regarding paid services, pricing, or required credentials.
not detected
The evidence does not mention any requirement for user registration to use the skill.
It cannot decide if a build failure is due to environment variables, custom build configurations, monorepo-specific setups, or external services. It also requires the user to manually ask for guidance after 2-3 failed build or run attempts and when the project structure is convoluted.
Evidencepackages/skills/skills/argent-react-native-app-workflow/SKILL.md:1-165
--- name: argent-react-native-app-workflow description: Step-by-step workflows for developing or debugging React Native apps on iOS simulator or Android emulator. Use when starting the app, debugging Metro, fixing builds, diagnosing runtime errors, or running tests. --- Physical iPhone (`kind: "device"`): Metro debugging and profiling tools reject it. Use a simulator. ## 1. Starting the React Native App ### 1.1 Explore Configuration (MANDATORY — Do This First) **Before running commands**, read the project's build and run configuration from the `argent-environment-inspector` subagent result. Do NOT default to `npx react-native start` or `npx react-native run-ios` without first checking for custom scripts and workflows. **Manual fallback** (if neither the agent nor the tool is available): read ALL `package.json` scripts — look for custom scripts like `start:local`, `start:dev`, `ios`, `build:ios`, flavors, etc. Custom scripts take priority over default commands. Also check `metro.config.js` for non-default port or watchFolders. For iOS builds, prefer opening `.xcworkspace` over `.xcodeproj` (CocoaPods generates the workspace). **If the project structure is convoluted, ask the
Read 1 of 1 text files in the skill.
Installfrom the directory
npx skills add https://github.com/software-mansion/argentInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
1 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 14.4k, not zero — the range is 14.4k to 14.9k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
For JavaScript/React changes, you should use the `debugger-reload-metro` tool. If you changed native code or ran `pod install`, you will need to rebuild the app.
Yes, before starting anything, you must check for and prioritize any project-specific start or run scripts. These custom scripts take precedence over default commands.