Przejdź do treści
Biblioteka skilli
Programowanie · Testowanie

verify

/verify

Prowadzi klienta desktopowego lobby-rs jak członek i zbiera dowody bez przejmowania pulpitu użytkownika.

Repozytorium
lobby-rs ↗
Licencja
AGPL-3.0
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
9
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/doctor.ps1

Co robi i kiedy

Prowadzi klienta desktopowego lobby-rs jak członek i zbiera dowody bez przejmowania pulpitu użytkownika.

Oryginalny opis (EN)

Drive the lobby-rs desktop app (the `lobby` GPUI client against a real `lobby-server`) the way a Member does and capture proof, headless and without touching the person's desktop. Use to prove a UI change, reproduce a desktop bug, user-test or critique a change, or check the small window, before calling desktop work done.

Jak działa

  1. Launch
  2. Doctor
  3. Drive
  4. Evidence
  5. Cleanup
  6. Helpers
  7. Feature map
Sekcje z nagłówków SKILL.md, w oryginale · 98 linii, 1 239 słów
Podgląd SKILL.md
---
name: verify
description: Drive the lobby-rs desktop app (the `lobby` GPUI client against a real `lobby-server`) the way a Member does and capture proof, headless and without touching the person's desktop. Use to prove a UI change, reproduce a desktop bug, user-test or critique a change, or check the small window, before calling desktop work done.
---

# Verify lobby-rs

The surface is the Windows desktop app `lobby` (crate `lobby-desktop`) talking to `lobby-server`. You drive it with JSONL scenarios through the app's automation channel. That works in two places: in process (Layer 3) and against the real binaries (Layer 4). The scenario language is the header comment of `crates/lobby-desktop/src/automation/scenario.rs`. This skill is the short path and the rules.

Hard rules (the person uses this PC while you work):

- Never use SendInput, move the mouse, take the focus, or raise a window. The harness never does. Do not add tools that do.
- Never sleep or wait out a real timer (idle after 10 min, toast expiry, backoff). Wait for something the person would see. Prove timers on Layer 3 with `{"advance": ms}`, or in a unit test with `advance_clock`.
- Kill only processes you started, by PID. Never by image name: another agent's drive or the person's own `lobby` may be running.
- Check the UI at 680×480 (default) and at 480×400 (minimum).

## Launch

There is no long-lived instance to start. Each run starts and stops its own server and clients.

- **Layer 3, in process (default, fastest).** `LOBBY_SCENARIO=<part of a name> cargo nextest run -p lobby-desktop --test e2e_ui`. Each scenario runs a real in-process `lobby-server` behind a chaos proxy with an SMTP sink, plus one real `Shell` per client. Ready means the test started; there is nothing to poll. Add `LOBBY_RENDER_TESTS=1` for pictures, which needs a Vulkan or GL driver. It supports everything, including `network`, `advance`, `freeze`/`thaw` and `{code:<email>}`.
- **Layer 4, real binaries.** `cargo xtask drive <name-or-path> [--instances a,b] [--no-build] [--visible]`. It builds `lobby-server` and `lobby --features automation` into `./target` unless `--no-build` is given. It starts the server on free ports with scratch data, then one `lobby` per client with instance id `tV-drive-<driver pid>-<client>`. Each window opens off screen without activation. Ready is the line `drive <name>: server http://127.0.0.1:<port>, clients a, b (pipes tV-drive-<pid>-*)`. Each step then prints `ok` or `FAIL` with its line number. Use Layer 4 for DirectX and DirectWrite pixels, real Quit and restart, Credential Manager, window resizes and real window sizes. Its servers mail into the driver's own SMTP sink, so `{code:<email>}` works there too. It does not support `freeze`/`thaw`, `network`, `advance` or `paste`, and it refuses a scenario whose header has `layer3_only`, `history`, `sent_files` or `own_paths`. It fills only `{lobby}`, `{lobby2}`, `{host}`, `{host2}` and the codes. It drives only a server of its own: a deployed Lobby's mail is out of its reach, so nothing could sign in there.
- **Teardown** is automatic. The driver quits each client through the Quit flow, stops the server, and removes its Credential Manager entries. The next run removes entries left by drivers that died.

Use one shared target dir (`./target`).

## Doctor

Run this first whenever anything looks off (a pipe that will not open, a stuck drive, stale pictures):

```powershell
pwsh -NoProfile -File .claude/skills/verify/scripts/doctor.ps1
```

It changes no file and ends no process. It runs `cargo xtask check-toolchain`, which waits for the build lock. It reports:

- the toolchain check;
- whether the drive binaries are older than the newest source change;
- `lobby` and `lobby-server` processes running from this repo's `target`, with their PIDs, start times and command lines;
- running `xtask drive` processes;
- leftover `lobby-rs/tV-drive-*` Credential Manager entries.

A driven client shows `LOBBY_AUTOMATION` only in its environment, so the doctor cannot tell whose it is. A process you did not start is not yours to kill.

## Drive

1. Find the scenario that covers the behaviour: `features/README.md` here maps features to scenarios, and each scenario's header line says what it proves.
2. Run the existing scenario first (Layer 3, then Layer 4 if the change touches pixels, windows or process lifecycle).
3. For a new check, write a scenario.
   - A permanent one goes in `crates/lobby-desktop/tests/scenarios/<flow>-<behaviour>.jsonl`, whose header's `scenario` says what it proves. It then runs in every `cargo nextest run --workspace`.
   - A throwaway exploration goes in `target/verify/<name>.jsonl`. Never put it under `target/drive/`: a drive deletes `target/drive/<name>/` first.
   - Copy the sign-in prefix from `chat.jsonl`. A Member `alice` has the email `alice@lobby.test`, and the address field starts empty:

     ```json
     {"scenario": "…", "clients": ["a", "b"], "members": ["alice", "bob"]}
     {"on": "a", "type": "{lobby}", "into": "lobby-url"}
     {"press": "enter"}
     {"wait": {"path": "/auth/step", "eq": "Email"}}
     {"type": "alice@lobby.test", "into": "email"}
     {"press": "enter"}
     {"wait": {"path": "/auth/step", "eq": "Code"}, "timeout_ms": 5000}
     {"type": "{code:alice@lobby.test}", "into": "code-input"}
     {"wait": {"path": "/lobby/phase", "eq": "connected"}, "timeout_ms": 5000}
     ```
4. Handles are element ids, never coordinates. To see what exists, add `{"dump": "x"}`. The dump has `/elements/<id>` (bounds, visibility, accessible name) and the view model (`/route`, `/auth/step`, `/lobby/phase`, `/lobby/members/<name>/…`, `/lobby/chat/rows`, `/lobby/connection`, `/lobby/voice/controls`, `/issues`, `/lobbies`, `/window/width`, …). An element without an id needs `.test_support()` in its builder. Icon-only buttons need an `accessibility_label`, which is their name in the dump.
5. "Nothing moves" is `{"mark": "m"}` … `{"wait": {"unchanged": "<id>", "since": "m"}}`. Window size changes go through a header `"size": [480, 400]`, or on Layer 4 only `{"action": "resize:480x400"}`.

## Evidence

Where proof lands:

- **Layer 3.** `target/ui-shots/scenarios/<scenario>/`: `transcript.jsonl` (every step, client, time and failure), `<client>-failed.json` (the dump a failed wait saw), `<client>-<name>.png|json` for `shot` and `dump` steps.
- **Layer 4.** `target/drive/<scenario>/out/` holds `transcript.jsonl` and the `shot` and `dump` files. `target/drive/<scenario>/server/server.log` and `clients/<client>/logs/` hold the processes' logs.

What counts as proof:

- **Drive the user path.** Clicks, typing and key presses on the real views. No internal setters and no test-only endpoints.
- **Capture the action and the state it produced.** Use a `wait`/`expect` on the model, plus a `shot` of the region, not just the last screen.
- **Check side effects on the other client.** For anything a Member shares, the second client must see it: wait on client `b` too.
- **Read the shots.** Open the PNGs. Layer 3 draws with the bundled Figtree in all four weights, on wgpu and Cosmic text, with motion reduced; judge motion, and how text weight and hierarchy come out on the real DirectWrite, on Layer 4 shots.
- **Name the exact command, the scenario file and the output folder** in your report.

A run is a pass only if every step printed `ok` (Layer 4) or the test passed (Layer 3). "Inconclusive" or a check on the wrong layer is not a pass.

## Cleanup

- A finished drive cleans up after itself. After a drive you interrupted, run the doctor. End only the `lobby`/`lobby-server` PIDs your run started: `Stop-Process -Id <pid>`. The next drive removes stale Credential Manager entries.
- Evidence survives cleanup. A rerun of the same scenario name replaces `target/drive/<name>/`. Before re-running, copy `out/` to `target/verify/evidence/<name>-<label>/` if you need the earlier pictures.
- Delete throwaway scenarios in `target/verify/` when done. Keep the evidence.

## Helpers

- `.claude/skills/verify/scripts/doctor.ps1`: the health check, see Doctor.
- `xtask/scripts/focus-watch.ps1`: logs the foreground window and cursor during a run, to prove nothing took the focus.
- `xtask/scripts/resize-check.ps1 -ProcessId <pid of a client you started>`: resizes the window through a list of sizes and captures each with PrintWindow; `-Stress 200` adds rapid resizes. `-Maximize` activates the window, so use it only with the person's leave. Run it after changes near the window, the renderer or gpui-kit's version.

## Feature map

`features/README.md` indexes the user-facing features with their recipes and gotchas. Keep it honest with `/maintain-verification-skill`.

What still needs the person, not this skill: hearing audio and a real microphone, a real sleep and resume, IME input, the OS idle signal, a VPS and a second network.
Pliki w paczce (9)
  • SKILL.md 9 KB
  • features/README.md 3 KB
  • features/chat.md 3 KB
  • features/connection-and-presence.md 3 KB
  • features/lobbies-and-window.md 6 KB
  • features/settings-and-appearance.md 10 KB
  • features/sign-in-and-admission.md 3 KB
  • features/voice-and-screen-share.md 8 KB
  • scripts/doctor.ps1 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · frisksitron/lobby-rs100AGPL-3.0
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
NolwennD/gabier100Apache-2.0
ericrisco/rsc-harness100MIT
sentimony/agentic-workflow100MIT
JoDi-27/JoDi-SDD100MIT
marcel-bich/marcel-bich-claude-marketplace100MIT
kdlbs/kandev100AGPL-3.0

Migawka bazy z 13.11.2026 · wersja paczki d39fb06d5a98 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100dedicated-server
    Pomaga budować serwery dedykowane do gier: eksport headless, architekturę serwera, zarządzanie lobby i wdrożenie.
  • 100dedicated-server
    Pomaga budować serwery dedykowane do gier: eksport bez interfejsu, architekturę serwera, zarządzanie lobby i wdrożenie.
  • 100gpui-screenshots
    Uruchamia klienta GPUI w ukrytym oknie na testowych danych, by zobaczyć, kliknąć i zrobić zrzut ekranu zmiany w interfejsie.
  • 100verification-skill
    Tworzy i utrzymuje skill weryfikacji dla projektu, który uruchamia prawdziwą aplikację i zbiera dowody działania.
  • 95engineering-matchmaking-system
    Projektuje dobieranie graczy w grach: dobór według umiejętności, kolejki, lobby, ranking i ELO.
  • 100matchmaking-lobby
    Projektuje dobieranie graczy i lobby: ranking umiejętności, tworzenie meczów, poszerzanie kolejki, routing regionów i przekazanie serwera.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.