@parallax-rn/mcp 0.1.0-beta.2 → 0.1.0-beta.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parallax-rn/mcp",
-  "version": "0.1.0-beta.2",
+  "version": "0.1.0-beta.4",
   "description": "Parallax for React Native: the MCP server (stdio): device and app tools, setup, doctor. Published as one bundled file with no runtime dependencies. Tested on React Native 0.87.1.",
   "license": "SEE LICENSE IN LICENSE",
   "files": [
@@ -13,10 +13,10 @@
   },
   "devDependencies": {
     "@modelcontextprotocol/sdk": "1.32.0",
-    "@parallax-rn/connection": "0.1.0-beta.2",
-    "@parallax-rn/core": "0.1.0-beta.2",
-    "@parallax-rn/protocol": "0.1.0-beta.2",
-    "@parallax-rn/testing": "0.1.0-beta.2",
+    "@parallax-rn/connection": "0.1.0-beta.4",
+    "@parallax-rn/core": "0.1.0-beta.4",
+    "@parallax-rn/protocol": "0.1.0-beta.4",
+    "@parallax-rn/testing": "0.1.0-beta.4",
     "esbuild": "0.28.2",
     "zod": "4.6.5"
   },

package/skills/parallax/SKILL.md

@@ -17,7 +17,7 @@ Parallax gives you the running app through the `parallax` MCP server: the simula
 2. `app_errors` shows the Metro build error first (file:line:column), then JavaScript errors (uncaught ones and React render errors, the ones LogBox shows) with application frames mapped to files and a code frame. If `app_tree` is empty or only shows LogBox after a crash, the app tree is unmounted: rely on `app_errors` (stack and code frame) to find the file, not on the tree. Use `since` with the `next:` cursor to see only new ones.
 3. `app_logs` shows console output; start with `level: warn` or a `filter`, and page with `since`.
 4. `app_tree` shows the project's components. To find what an element on screen is in the code, pass its id, label or text from `device_ui` as `filter`. Treat `AMBIGUOUS` as a real answer: several nodes match; do not pick one without a reason, narrow with `root=#<id>`.
-5. `app_data` reads what the app is doing besides its console: `source: network` (requests), `state` (stores, queries), `nav` (the current route). Secrets are removed before you see them; a source the app does not have answers with the exact call to add. Page with `since`.
+5. `app_data` reads what the app is doing besides its console: `source: network` (requests), `state` (stores, queries), `nav` (the current route), `storage` (AsyncStorage, UserDefaults and SharedPreferences keys and short plain values; no SDK needed). Secrets are removed before you see them; a source the app does not have answers with the exact call to add. Page with `since`.
    - `source: network` lists the newest requests (`id` rN, method, status, time, size, URL); `filter` takes words (`failed`, `4xx`, `404`, `post`, a part of the URL). `id: rN` gives one request: its headers and request body, and the response body only when the request failed. Ask for a successful response's body with `body: true`. Headers and bodies come without secrets (`[redacted]`).
 6. Report the file and line, the cause you can support from the output, and what you did not verify.
 
@@ -25,6 +25,7 @@ Parallax gives you the running app through the `parallax` MCP server: the simula
 - Read-only, use freely: `status`, `doctor`, `device_list`, `device_screenshot`, `device_ui`, `app_logs`, `app_errors`, `app_tree`, `app_data`, `app_commands`.
 - Change the simulator or the app, so **ask the user first** unless they asked for exactly that action: `device_boot`, `device_tap`, `device_type`, `device_swipe`, `device_open_url`, `app_launch`, `app_reload`, `app_command_run`, `parallax_inbox`. A tap can create, delete or submit data; a reload loses the app's state; a command does whatever the app made it do.
 - `parallax_inbox` is the exception to asking: it only returns what the user sent you from the Parallax app (an error, a screen, a note) and marks it as delivered. Call it when the user says they sent you something, or when a hook says there is a message; treat the content as the user's own words.
+- To reach a screen, prefer `app_command_run name: navigate` over a chain of taps: without args it lists the screens of the app's navigators, with `args: {"screen": "Name"}` (a nested one as `Parent/Child`, plus `params`) it goes there (React Navigation and Expo Router; no SDK needed). Without a navigation container, use the app's deep link with `device_open_url`; taps last.
 - After an action, read the answer's summary of what changed, then `device_ui` for the new screen.
 
 ## Things to know