@swmansion/argent 0.32.1-next.0 → 0.32.1-next.2

package/skills/argent-device-interact/references/gesture-examples.md

@@ -1,114 +0,0 @@
-# Gesture Examples
-
-Detailed sequences and parameters for the gesture tool family. All coordinates, distances, and radii are **normalized 0.0–1.0** (fractions of screen width/height, not pixels); same coordinate space across all gesture tools.
-
-## gesture-pinch: Two-finger pinch
-
-Pinch out (zoom in):
-
-```json
-{ "udid": "<UDID>", "centerX": 0.5, "centerY": 0.5, "startDistance": 0.2, "endDistance": 0.6 }
-```
-
-Pinch in (zoom out):
-
-```json
-{ "udid": "<UDID>", "centerX": 0.5, "centerY": 0.5, "startDistance": 0.6, "endDistance": 0.2 }
-```
-
-Vertical pinch (angle = 90):
-
-```json
-{
-  "udid": "<UDID>",
-  "centerX": 0.5,
-  "centerY": 0.5,
-  "startDistance": 0.2,
-  "endDistance": 0.6,
-  "angle": 90
-}
-```
-
-## gesture-rotate: Two-finger rotation
-
-Clockwise 90 degrees:
-
-```json
-{
-  "udid": "<UDID>",
-  "centerX": 0.5,
-  "centerY": 0.5,
-  "radius": 0.15,
-  "startAngle": 0,
-  "endAngle": 90
-}
-```
-
-Counter-clockwise 45 degrees:
-
-```json
-{
-  "udid": "<UDID>",
-  "centerX": 0.5,
-  "centerY": 0.5,
-  "radius": 0.15,
-  "startAngle": 0,
-  "endAngle": -45
-}
-```
-
-## gesture-custom: Custom touch sequences
-
-### Long Press (800ms hold)
-
-```json
-{
-  "udid": "<UDID>",
-  "events": [
-    { "type": "Down", "x": 0.5, "y": 0.5 },
-    { "type": "Up", "x": 0.5, "y": 0.5, "delayMs": 800 }
-  ]
-}
-```
-
-### Pinch Out (zoom in): manual events
-
-```json
-{
-  "udid": "<UDID>",
-  "events": [
-    { "type": "Down", "x": 0.4, "y": 0.5, "x2": 0.6, "y2": 0.5 },
-    { "type": "Move", "x": 0.2, "y": 0.5, "x2": 0.8, "y2": 0.5 },
-    { "type": "Up", "x": 0.2, "y": 0.5, "x2": 0.8, "y2": 0.5 }
-  ]
-}
-```
-
-### Pinch Out with interpolation: smooth version
-
-```json
-{
-  "udid": "<UDID>",
-  "events": [
-    { "type": "Down", "x": 0.4, "y": 0.5, "x2": 0.6, "y2": 0.5 },
-    { "type": "Up", "x": 0.2, "y": 0.5, "x2": 0.8, "y2": 0.5 }
-  ],
-  "interpolate": 15
-}
-```
-
-### Drag and Drop
-
-```json
-{
-  "udid": "<UDID>",
-  "events": [
-    { "type": "Down", "x": 0.3, "y": 0.4 },
-    { "type": "Move", "x": 0.3, "y": 0.4, "delayMs": 500 },
-    { "type": "Move", "x": 0.7, "y": 0.6 },
-    { "type": "Up", "x": 0.7, "y": 0.6 }
-  ]
-}
-```
-
-Add a `delayMs` on the first `Move` to simulate a hold before dragging; this is required for some drag-and-drop implementations that only activate after a sustained press.

package/skills/argent-device-interact/references/secrets.md

@@ -1,23 +0,0 @@
-# Typing Secrets
-
-Where a `{{secret:<NAME>}}` placeholder gets its value, and the rules for using one. See the `keyboard` section of SKILL.md for the placeholder syntax itself.
-
-## Where the value comes from
-
-The placeholder is resolved on the machine running the tool-server, from the first of these that defines the name:
-
-| #   | Source                                        | Which keys it exposes                                                |
-| --- | --------------------------------------------- | -------------------------------------------------------------------- |
-| 1   | `ARGENT_SECRET_<NAME>` environment variable   | prefixed vars only; the CI-native path                               |
-| 2   | `<project>/.argent/secrets.env`               | every key (`APP_PASSWORD=…`); gitignore this file                    |
-| 3   | `<project>/.env.local`, then `<project>/.env` | only `ARGENT_SECRET_`-prefixed keys, so app config stays unreachable |
-| 4   | `~/.argent/secrets.env`                       | every key, per-user, works in any project                            |
-
-Over `argent link` or `ARGENT_TOOLS_URL` the tool-server can be another machine. With `argent enable forward-secrets` on the client, the client resolves each placeholder of a call with these same sources on its own machine and sends the values with the call; the tool-server's sources resolve only the names the client lacks.
-
-## Rules
-
-- The result echoes the placeholder, never the value. An unknown name fails with the list of available secret _names_ and every source the tool-server looked in, with paths; read that list before asking the user anything. A client that forwards secrets does not add its own sources to it; `argent secrets` on the client lists those. When the failure says the required secret was not provided, the client forwards secrets and has no value for the name, so it belongs on the client's machine.
-- The auto-screenshot after the call is skipped so the typed value cannot re-enter your context as pixels. Do **not** `describe` or `screenshot` a non-secure field you just filled with a secret; submit or navigate away first, then verify the resulting screen. To submit, put the text step and the Enter step in **one `run-sequence`**. The skip covers a whole batch that contains the placeholder, but a second bare `keyboard` call gets its own screenshot of the filled field.
-- Nothing outside those sources is reachable; never ask the user to paste a secret value into the conversation. Ask them to put it in a secrets file instead: a file edit applies to the next call, while an exported env var only reaches a tool-server (or, for a forwarded secret, a client) started afterwards.
-- The project sources are found by walking up from the tool-server's working directory. If a project file is not being picked up, the failure's source list shows the paths actually consulted; `~/.argent/secrets.env` needs no project and always applies.

package/skills/argent-metro-debugger/references/failure-scenarios.md

@@ -1,14 +0,0 @@
-# Failure Scenarios: Recovery Steps
-
-When a debugger tool fails, use **`debugger-status`** first to diagnose. Note: `debugger-status` and `debugger-log-registry` do **not** fail when the debugger is simply unreachable: they return `{ status: "not_connected", reason, detail, guidance }` (the `detail` field carries the same error text other tools throw). Do not retry the same failing tool repeatedly without following the recovery steps.
-
-| Scenario                           | Error or situation                                                                                                                                 | What to do                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **Metro not running**              | Error (or `not_connected` `detail`) contains: `Metro at port 8081 is not running (got: ...)`                                                       | `debugger-status` / `debugger-log-registry` return `{ status: "not_connected", reason: "metro_not_running", guidance }` here instead of erroring; other debugger tools still throw. **Start Metro yourself** unless the user asked you not to: scan the workspace configuration and run the appropriate command to start Metro in the background (by default `npx react-native start` or `npx expo start`). Wait for Metro to be ready, then retry `debugger-connect` or `debugger-status` once, not in a loop. If you cannot determine the project root, ask the user. A non-Metro server occupying the port lands here too; the `got:` text shows what answered. |
-| **No source locations**            | `projectRoot` is `""` and source lookups report no file:line                                                                                       | Not a failure. Legacy Metro (RN 0.72 and older, e.g. Vega) sends no `X-React-Native-Project-Root` header, so paths cannot be resolved against a project root. `debugger-evaluate`, console logs and the network inspector work regardless; do not restart Metro to "fix" it.                                                                                                                                                                                                                                                                                                                                                                                       |
-| **App not connected**              | Error (or `not_connected` `detail`) contains: `Metro at port 8081 has no CDP targets — is a React Native app connected?`                           | `debugger-status` / `debugger-log-registry` return `{ status: "not_connected", reason: "no_app_connected", guidance }` here instead of erroring; other debugger tools still throw. 1) Confirm the app is running on the device. 2) Use `restart-app` with the app's device id and bundleId to relaunch so it connects to Metro. 3) Wait a few seconds for the bundle to load. 4) Retry `debugger-status` once. Do **not** use `debugger-reload-metro` to fix this; it also requires at least one target.                                                                                                                                                           |
-| **Wrong device id**                | `debugger-status` / `debugger-log-registry` return `reason: "device_mismatch"`, or `debugger-connect` fails with `DEBUGGER_TARGET_DEVICE_MISMATCH` | The `device_id` matches no debugger target on this Metro. Re-target with the `logicalDeviceId` listed in the `detail` / error message, or give the device its own Metro port. Do not retry with the same `device_id`; the result will not change.                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| **Stale connection**               | `debugger-status` returns `reason: "stale_connection"`                                                                                             | The cached debugger connection was no longer open; `debugger-status` has already discarded it. Use `restart-app` if the app is not running, then call `debugger-connect`; the next call reconnects fresh.                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| **Reconnecting**                   | `debugger-status` / `debugger-log-registry` return `reason: "reconnecting"`                                                                        | A reconnect is in flight: the previous connection was just torn down, or (Chromium) a tab switch is in progress. Transient: wait a moment and retry once. Do **not** restart the app for this.                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| **Runtime unresponsive**           | `reason: "runtime_unresponsive"`, or another debugger tool fails with `DEBUGGER_CDP_REQUEST_TIMEOUT`                                               | Follow the `guidance` / error text; it explains the state and the recovery. Each attempt waits out the full CDP timeout, so never retry in a loop.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| **Was connected, then tool fails** | Any debugger tool fails with a connection or disconnect error after it was working                                                                 | The app may have crashed or been closed. Use `restart-app` to relaunch the app, then call `debugger-connect` again to pick up the fresh `logicalDeviceId` (may change for booted-fresh simulators), and use that new `device_id` on all subsequent calls.                                                                                                                                                                                                                                                                                                                                                                                                          |

package/skills/argent-metro-debugger/references/source-maps.md

@@ -1,27 +0,0 @@
-# Source Resolution for `inspect-element`
-
-`debugger-inspect-element` tries to resolve each component in the hierarchy to its source file and line. It uses a fallback chain:
-
-1. **`_debugStack`** (React fiber property): a stack trace string from the bundled code. When available, the tool symbolicates it via Metro's `/symbolicate` endpoint to resolve to the original source file, then reads a code fragment from disk. Set `resolveSourceMaps: false` to skip symbolication and return raw bundled locations instead.
-2. **`_debugSource`** (React fiber property): contains `{ fileName, lineNumber, columnNumber }` pointing directly to the original source file. No symbolication needed. The tool reads the code fragment from disk automatically.
-3. **Neither available**: the tool returns the component hierarchy with `source: null` and `code: null` for all items. The hierarchy (component names) is still useful.
-
-## When Source Info Is Missing
-
-If `debugger-inspect-element` returns all items with `source: null`, the React Native project's Babel configuration does not inject source information into JSX elements. This is common with the **automatic JSX transform** (used by Expo SDK 50+ and React Native 0.73+).
-
-**To enable source resolution**, inform the user that they can add `@babel/plugin-transform-react-jsx-source` to their project's Babel config. For example, in `babel.config.js`:
-
-```js
-module.exports = function (api) {
-  api.cache(true);
-  return {
-    presets: ["babel-preset-expo"], // or 'module:@react-native/babel-preset'
-    plugins: [
-      "@babel/plugin-transform-react-jsx-source", // enables _debugSource on fibers
-    ],
-  };
-};
-```
-
-After adding the plugin, restart Metro (`npx react-native start --reset-cache` or `npx expo start --clear`) and reload the app. No extra `npm install` needed; the plugin ships with `babel-preset-expo` and `@babel/preset-env`.

package/skills/argent-react-native-profiler/references/diagnostic-tools.md

@@ -1,101 +0,0 @@
-# Diagnostic Tools
-
-These tools can be called independently without starting a profiling session.
-
-## Live render stats
-
-```json
-{ "port": 8081, "device_id": "<UDID>", "top_n": 20 }
-```
-
-Call `react-profiler-renders`. Returns render counts and durations per component, useful for spotting hot components before a full profile.
-
-## Component hierarchy
-
-```json
-{ "port": 8081, "device_id": "<UDID>", "max_depth": 10, "filter": "MyComponent" }
-```
-
-Call `react-profiler-fiber-tree`. Inspect `useMemoCache` presence to confirm React Compiler is active for a given component. If `useMemoCache` is absent, the compiler bailed out for that component; memoization hints are safe to propose.
-
-## Console logs
-
-```json
-{ "port": 8081, "device_id": "<UDID>" }
-```
-
-Call `debugger-log-registry`. When connected (`status: "connected"`) it returns a summary with entry counts by level, message clusters, and the log file path. Use `Grep` on the log file to filter by level or search for specific messages. When the debugger is unreachable it does not fail: it returns `{ status: "not_connected", reason, detail, guidance }` with no log file; follow the `guidance` (do not retry in a loop, and do not try to grep a file in this state).
-
----
-
-# Post-Analysis Query Tools
-
-These require a completed profiling session (`react-profiler-stop` + `react-profiler-analyze`).
-
-## CPU query
-
-```json
-{ "port": 8081, "device_id": "<UDID>", "mode": "top_functions", "top_n": 15 }
-```
-
-Call `profiler-cpu-query`. Modes:
-
-- `top_functions`: global CPU hotspots. Add `time_window_ms: { start, end }` to filter.
-- `time_window`: CPU breakdown for a specific time range (e.g. during a slow commit).
-- `call_tree`: callers and callees of a specific `function_name`.
-- `component_cpu`: aggregate CPU during all commits of a `component_name`.
-
-> **Component names:** pass the name exactly as the report shows it. The report strips
-> `Forget(...)` / `Memo(...)` / `ForwardRef(...)` wrappers and marks them with a
-> `[React Compiler]` / `[React.memo] `/ `[forwardRef]` tag; both that displayed name and the
-> underlying wrapped name resolve. If a name maps to several distinct fibers the tool lists
-> the exact names to retry with rather than merging them; a combined total would not describe
-> any real component.
-
-## Commit query
-
-```json
-{ "port": 8081, "device_id": "<UDID>", "mode": "by_component", "component_name": "AppNavigator" }
-```
-
-Call `profiler-commit-query`. Modes:
-
-- `by_component`: all commits where a component rendered.
-- `by_time_range`: commits in a `time_range_ms` window.
-- `by_index`: full detail of a single `commit_index`.
-- `cascade_tree`: parent-child re-render cascade for a commit.
-
-## iOS Instruments query
-
-```json
-{ "device_id": "<UDID>", "mode": "hang_stacks", "hang_index": 0 }
-```
-
-Call `profiler-stack-query` after `native-profiler-analyze`. Modes:
-
-- `hang_stacks`: full CPU context during a specific hang.
-- `function_callers`: who calls a specific native `function_name`.
-- `thread_breakdown`: CPU time split by thread, optionally filtered.
-- `leak_stacks`: memory leak details, optionally filtered by `object_type`.
-
-## Combined report
-
-```json
-{ "port": 8081, "device_id": "<UDID>" }
-```
-
-Call `profiler-combined-report` when both React Profiler and iOS Instruments ran in parallel. Automatically correlates iOS hangs with React commits using wall-clock time alignment.
-
-## Session reload
-
-```json
-{ "mode": "list" }
-```
-
-Call `profiler-load`. Modes:
-
-- `list`: show all saved profiling sessions (React + iOS) in `/tmp/argent-profiler-cwd/`.
-- `load_react`: reload a React profiler session by `session_id` + `device_id`. Populates the `port:device_id`-keyed in-memory cache for `profiler-cpu-query` and `profiler-commit-query` (which must be called with the same `device_id` afterward).
-- `load_native`: re-parse native profiler XML by `session_id` and `device_id`. Populates session for `profiler-stack-query`.
-
-Use this to revisit an earlier profiling session without re-profiling. Each `react-profiler-analyze` run saves raw data with a unique timestamp.