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 }}
This repository was archived by the owner on Oct 10, 2026. It is now read-only.
Repository navigation
Commit f7cc776
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
+21-3Lines changed: 21 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: test-t3-app
3
-
description: Launchand test the T3 Code web app in isolated development environments, including first-try browser authentication with one-time pairing URLs, pairing-token recovery, worktree-safe state directories, dev server lifecycle, and direct SQLite inspection or fixture seeding. Use when an agent needs to run T3 locally, test UI behavior in a browser, recover from an expired or consumed pairing token, isolate dev state, or prepare test data in state.sqlite.
3
+
description: Launch, retain, and test the T3 Code web app in isolated development environments, including first-try browser authentication with one-time pairing URLs, pairing-token recovery, worktree-safe state directories, cross-turn dev server lifecycle, and direct SQLite inspection or fixture seeding. Use when an agent needs to run T3 locally, iteratively test UI behavior with a human, recover from an expired or consumed pairing token, isolate dev state, or prepare test data in state.sqlite.
4
4
---
5
5
6
6
# Test T3 App
@@ -20,6 +20,16 @@ Treat a base directory as disposable only when it was created or deliberately se
20
20
21
21
The dev runner disables browser auto-open by default. Do not pass `--browser` during automated testing: an automatically opened page can consume the one-time bootstrap token before the controlled browser uses it.
22
22
23
+
## Preserve the environment while iterating
24
+
25
+
Treat the overall testing or implementation loop—not an assistant turn or one verification pass—as the environment lifecycle boundary.
26
+
27
+
- Keep the dev process, base directory, selected ports, authenticated browser tab, registered projects, and seeded fixtures alive while the user may inspect the result or request follow-up changes.
28
+
- Do not stop the server merely because one verification pass completed or because you are yielding a response to the user.
29
+
- Before starting another environment, check whether the existing process and browser tab still serve the task. Reuse them when healthy instead of discarding useful state.
30
+
- On a later turn, verify that the existing process is alive and reuse its printed ports and base directory. If it exited, restart with the same base directory; create a new pairing token only when the browser session is no longer valid.
31
+
- Tell the user when a test environment remains available, including its non-secret web URL when useful. Never include a pairing token.
32
+
23
33
## Authenticate the browser on the first navigation
24
34
25
35
1. Wait for the server log that says authentication is required and includes a URL ending in `/pair#token=...`.
@@ -58,9 +68,17 @@ Read [references/sqlite-fixtures.md](references/sqlite-fixtures.md) before chang
58
68
59
69
The helper refuses to write to the shared `~/.t3` directory by default and creates a database backup before each mutation.
60
70
61
-
## Finish the test
71
+
## Tear down only when the testing loop is finished
72
+
73
+
Tear down when the user explicitly asks, confirms the iteration is finished, or the overall task is genuinely complete with no pending human review. Do not infer completion from the end of an assistant turn.
74
+
75
+
When teardown is appropriate:
76
+
77
+
1. Stop the dev process with its terminal interrupt.
78
+
2. Preserve the isolated base directory when it contains useful reproduction evidence or state for a likely follow-up.
79
+
3. Otherwise remove only a path created for this test after resolving and verifying the exact target.
62
80
63
-
Stop the dev process with its terminal interrupt. Preserve the isolated base directory when it contains useful reproduction evidence; otherwise remove only a path that was created for this test after resolving and verifying the exact target. A fresh isolated base directory is the safest reset when authentication, migrations, or fixture state becomes ambiguous.
81
+
If completion is uncertain, keep the environment alive and mention that it is retained for further iteration. A fresh isolated base directory remains the safest reset when authentication, migrations, or fixture state becomes ambiguous.
0 commit comments