Skip to content

Commit 16a748f

Browse files
docs(skills): Separate web and mobile testing workflows
1 parent db802f8 commit 16a748f

4 files changed

Lines changed: 33 additions & 23 deletions

File tree

‎.agents/skills/test-t3-app/SKILL.md‎

Lines changed: 8 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
11
---
22
name: test-t3-app
3-
description: Test T3 Code through its built-in Browser and Device panels against isolated development state. Use for UI verification, pairing recovery, and test fixtures.
3+
description: Test T3 Code's web and desktop UI through its built-in Browser panel against isolated development state. Use for browser verification, browser pairing recovery, and test fixtures. Use test-t3-mobile for native mobile verification.
44
---
55

6-
# Test T3 Code
6+
# Test T3 web and desktop
77

8-
Use T3's built-in panels for verification. If the required T3 tools are absent
9-
or the panel reports unavailable, explain the blocker and stop verification.
10-
Do not install or switch to another automation system.
8+
Use T3's built-in Browser panel for verification. If its tools are absent or
9+
the panel reports unavailable, explain the blocker and stop verification.
10+
Do not install or switch to another automation system. For native mobile
11+
testing, use [test-t3-mobile](../test-t3-mobile/SKILL.md).
1112

1213
## Start the app
1314

@@ -20,21 +21,14 @@ Test with meaningful project and thread data. Read
2021
[references/sqlite-fixtures.md](references/sqlite-fixtures.md) only when
2122
inspecting or seeding SQLite. Stop the test server before direct fixture writes.
2223

23-
## Use the T3 panels
24+
## Use the Browser panel
2425

25-
For web, call `preview_status`, then `preview_open` if the Browser panel is
26+
Call `preview_status`, then `preview_open` if the Browser panel is
2627
closed. Navigate to the complete startup pairing URL once with
2728
`preview_navigate`, then use `preview_snapshot` and T3's interaction tools.
2829
If the token was consumed or expired, run `node apps/server/src/bin.ts pair`
2930
for a fresh one. Keep using the same tab.
3031

31-
For mobile, call `device_list`, then `device_open` with the selected host and
32-
device IDs. T3 boots the device and shows its live stream in the Device panel.
33-
Follow the returned `quickStart`, using the exact `agentDevice.command` and
34-
all `targetArgs` on every command. Use `device_screenshot` to inspect the screen.
35-
See [test-t3-mobile](../test-t3-mobile/SKILL.md) for launching and pairing T3 Code
36-
Dev. T3 owns device tooling and connections.
37-
3832
## Verify and retain
3933

4034
Exercise the affected flow and capture the state that proves it works. Keep
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
interface:
22
display_name: "T3 App Testing"
3-
short_description: "Test through T3's built-in panels"
4-
default_prompt: "Use $test-t3-app to verify the affected flow through T3's built-in panels."
3+
short_description: "Test web and desktop in T3's Browser panel"
4+
default_prompt: "Use $test-t3-app to verify the affected web or desktop flow through T3's Browser panel."

‎.agents/skills/test-t3-mobile/SKILL.md‎

Lines changed: 21 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,30 @@
11
---
22
name: test-t3-mobile
3-
description: Launch and pair T3 Code Dev for mobile verification through T3's Device panel and returned AgentDevice command.
3+
description: Test T3 Code'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.
44
---
55

66
# Test T3 Mobile
77

8-
Follow [test-t3-app](../test-t3-app/SKILL.md) for the T3 panel workflow and
9-
isolated backend. Keep the device visible in the Device panel and use the
10-
executable and target arguments returned by `device_open` for every operation.
11-
If T3 device access is unavailable, report the blocker and stop verification.
8+
## Open the device
9+
10+
Call `device_list`, then `device_open` with the selected host and device IDs.
11+
T3 boots the device and shows its live stream in the Device panel. Follow its
12+
returned `quickStart`, using the exact `agentDevice.command` and all `targetArgs`
13+
on every operation. Use `device_screenshot` to inspect the screen.
14+
15+
If T3 device tools or the selected device are unavailable, report the blocker
16+
and stop verification. Do not install or switch to another automation system.
17+
18+
## Use an isolated backend
19+
20+
Reuse this task's healthy backend. Otherwise run `vp run dev` from the
21+
repository root, retain its terminal session, and read the actual backend port
22+
from the dev-runner output. Use the worktree's ignored `.t3` state. Never run
23+
against `~/.t3/userdata`. The Browser panel is not required for this workflow.
24+
25+
Test with meaningful project and thread data. Read the shared
26+
[SQLite fixture reference](../test-t3-app/references/sqlite-fixtures.md) only
27+
when inspecting or seeding SQLite. Stop the test server before fixture writes.
1228

1329
## Launch T3 Code Dev
1430

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
interface:
22
display_name: "Test T3 Mobile"
3-
short_description: "Launch T3 Code Dev in the Device panel"
4-
default_prompt: "Use $test-t3-mobile to launch and pair T3 Code Dev through T3's Device panel."
3+
short_description: "Test iOS and Android in T3's Device panel"
4+
default_prompt: "Use $test-t3-mobile to verify the affected native mobile flow through T3's Device panel and AgentDevice."

0 commit comments

Comments
 (0)