You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 16a748f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/test-t3-app/SKILL.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,14 @@
1
1
---
2
2
name: test-t3-app
3
-
description: Test T3 Codethrough 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.
4
4
---
5
5
6
-
# Test T3 Code
6
+
# Test T3 web and desktop
7
7
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).
11
12
12
13
## Start the app
13
14
@@ -20,21 +21,14 @@ Test with meaningful project and thread data. Read
20
21
[references/sqlite-fixtures.md](references/sqlite-fixtures.md) only when
21
22
inspecting or seeding SQLite. Stop the test server before direct fixture writes.
22
23
23
-
## Use the T3 panels
24
+
## Use the Browser panel
24
25
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
26
27
closed. Navigate to the complete startup pairing URL once with
27
28
`preview_navigate`, then use `preview_snapshot` and T3's interaction tools.
28
29
If the token was consumed or expired, run `node apps/server/src/bin.ts pair`
29
30
for a fresh one. Keep using the same tab.
30
31
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
-
38
32
## Verify and retain
39
33
40
34
Exercise the affected flow and capture the state that proves it works. Keep
Copy file name to clipboardExpand all lines: .agents/skills/test-t3-mobile/SKILL.md
+21-5Lines changed: 21 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,30 @@
1
1
---
2
2
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.
4
4
---
5
5
6
6
# Test T3 Mobile
7
7
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.
0 commit comments