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

test-studio-app

Skill4 starsChanged 12 days agoMITView on GitHub

Test SpecWithCode'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-studio-mobile for native mobile verification.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use Studio's built-in Browser panel for verification.

    line 8
  2. Distinctive:

    Do not install or switch to another automation system.

    line 10
  3. Very specific:

    Never run against ~/.specweave-studio/userdata or set VITE_HTTP_URL or VITE_WS_URL.

    line 18
  4. Distinctive:

    Test with meaningful project and thread data.

    line 20
  5. Very specific:

    Call preview_status, then preview_open if the Browser panel is closed.

    line 26
  6. Very specific:

    If the token was consumed or expired, run node apps/server/src/bin.ts pair for a fresh one.

    line 29
  7. Very specific:

    When sharing is requested, start with vp run dev --share and give the user a fresh complete pairing URL that you have not consumed.

    line 39

≈ “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 web and desktop

Use Studio's built-in Browser panel for verification. If its tools are absent or the panel reports unavailable, explain the blocker and stop verification. Do not install or switch to another automation system. For native mobile testing, use test-studio-mobile.

Start the app

Reuse this task's healthy dev server. Otherwise run vp run dev from the repository root and retain its terminal session. Use the worktree's ignored .specweave-studio state and read the actual ports and pairing URL from the dev-runner output. Never run against ~/.specweave-studio/userdata or set VITE_HTTP_URL or VITE_WS_URL.

Test with meaningful project and thread data. Read references/sqlite-fixtures.md only when inspecting or seeding SQLite. Stop the test server before direct fixture writes.

Use the Browser panel

Call preview_status, then preview_open if the Browser panel is closed. Navigate to the complete startup pairing URL once with preview_navigate, then use preview_snapshot and Studio's interaction tools. If the token was consumed or expired, run node apps/server/src/bin.ts pair for a fresh one. Keep using the same tab.

Verify and retain

Exercise the affected flow and capture the state that proves it works. Keep the server, state, and panel available while the user inspects or iterates. An assistant turn ending is not teardown. Stop only processes you started, using retained terminal sessions or captured PIDs.

When sharing is requested, start with vp run dev --share and give the user a fresh complete pairing URL that you have not consumed. Keep other credentials out of screenshots, commits, and replies.

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.