agentleFS
anton-abyzovanton-abyzov/specwithcode/.agents/skills/test-studio-mobile/SKILL.md

test-studio-mobile

Skill4 starsChanged 12 days agoMITView on GitHub

Test SpecWithCode's native iOS and Android app through its Device panel and returned AgentDevice command. Use for mobile verification, native-client builds, Metro launch, and mobile pairing against isolated development state.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call device_list, then device_open with the selected host and device IDs.

    line 10
  2. Distinctive:

    If Studio device tools or the selected device are unavailable, report the blocker and stop verification.

    line 15
  3. Distinctive:

    Test with meaningful project and thread data.

    line 25
  4. Very specific:

    Start vp run dev:client from apps/mobile, or reuse a healthy Metro belonging to this checkout.

    line 40
  5. Very specific:

    Use the helper from the repository root, with the returned executable and target arguments stored in agent_device_command and the Bash …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Studio Mobile

Open the device

Call device_list, then device_open with the selected host and device IDs. Studio boots the device and shows its live stream in the Device panel. Follow its returned quickStart, using the exact agentDevice.command and all targetArgs on every operation. Use device_screenshot to inspect the screen.

If Studio device tools or the selected device are unavailable, report the blocker and stop verification. Do not install or switch to another automation system.

Use an isolated backend

Reuse this task's healthy backend. Otherwise run vp run dev from the repository root, retain its terminal session, and read the actual backend port from the dev-runner output. Use the worktree's ignored .specweave-studio state. Never run against ~/.specweave-studio/userdata. The Browser panel is not required for this workflow.

Test with meaningful project and thread data. Read the shared SQLite fixture reference only when inspecting or seeding SQLite. Stop the test server before fixture writes.

Launch SpecWithCode Dev

From the checkout being tested on the selected device host, run:

node scripts/mobile-native-client.ts ensure <ios|android> <device-id>

This reuses a matching native client or builds and installs one. Authorized mobile verification includes that build step unless the user prohibits it.

Start vp run dev:client from apps/mobile, or reuse a healthy Metro belonging to this checkout. Open its printed development-client URL with AgentDevice open com.specweave.studio.dev <url> and all returned target arguments. The device must be able to reach both Metro and the isolated backend. Append &disableAutoLaunch=1&disableFab=1 to the development-client URL query when developer chrome would obscure screenshots or taps; the SDK 58 dev client applies these preferences before the app loads.

Pair and verify

Use the helper from the repository root, with the returned executable and target arguments stored in agent_device_command and the Bash array agent_device_target_args:

.agents/skills/test-studio-mobile/scripts/pair-client.sh \
  <server-port> <base-dir> <device-reachable-backend-origin> \
  "$agent_device_command" "${agent_device_target_args[@]}"

It issues a fresh credential and opens SpecWithCode Dev's existing pairing route through AgentDevice. For a backend on the device host, use http://127.0.0.1:<server-port> on iOS or http://10.0.2.2:<server-port> on Android. For a remote backend, use its reachable origin.

Confirm the intended projects appear, exercise the affected flow, and capture evidence. Retain the app and environment while iterating. At teardown, remove the disposable connection, close the AgentDevice session, call device_close, and stop only your backend and Metro processes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.