Start a local preview of the app for the user and share an HTTPS link to it. Use when asked for a local preview, to "run it", "spin it up", "show me", or for a link to try a change on this machine (not Cursor Cloud; that is the run-app skill).
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Two ways to preview, from running locally. Pick one, start it, and hand the user an HTTPS hostname link.
| Preview | Runs | Use when |
|---|---|---|
| Web app only | Vite in apps/web against hosted *-dev services | The change is frontend-only (apps/web, packages/) |
| Full stack | Docker infra, local Rust services, Caddy proxy, frontend | The change touches crates/, services/, migrations, or needs private data |
git diff --name-only $(git merge-base HEAD origin/main)
plus uncommitted ones). Only frontend paths: web app. Only backend paths, or
both: full stack (it includes the frontend).Web app only
lsof -nP -iTCP:<port> -sTCP:LISTEN -t. Reuse a running Vite only if its cwd
(lsof -p <pid> | awk '$4=="cwd"') is this worktree.apps/web, inside the Nix shell, run PORT=<port> bun run dev in the
background. The first run may build wasm for a few minutes.App: https://<hostname>:<port>/app/.Full stack
--instance <worktree-name>. Never stop, reset, or destroy an instance you
didn't start.just stack up --instance <name> (add
--no-doppler if Doppler isn't authenticated). It serves a static build of
the frontend; after frontend edits run just stack update --frontend --instance <name>, after Rust edits just stack update --instance <name>.
If the user wants live reload, run just run_local --instance <name>
attached in a terminal they can see instead.just stack status --json --instance <name>, and
build the link from hostname, even if a URL is printed with localhost.just seed-scenario --instance <name> apply --file seed/scenarios/team-perms.json prints persona login links.If startup fails, run just doctor-local --instance <name>; for running-stack
problems use the live-debug skill. Don't wipe volumes to recover.
Always share the HTTPS URL on the machine's hostname, never localhost, an IP
address, or plain HTTP:
https://<hostname>:<port>/app/https://<hostname>:<proxy-port>/app/The certificate is issued from the repo's development CA for the output of
hostname (plus localhost and loopback); an IP address isn't in it, so an IP
link fails TLS. Tell the user, once:
infra/local/certs/ca.pem on the viewing machine (see
infra/local/certs/README.md).https://<hostname>:<proxy-port>/mailpit/ by a headless stack (with
attached run_local, use the Mailpit URL it prints).Public links: only if the user explicitly asks to share outside their network.
Then the stack needs just run_local --instance <name> --with-cf-tunnel, which
prints a https://….trycloudflare.com/app/ URL. Say first that it publishes a
passwordless-login stack to the internet.
One short message: which preview and why, the HTTPS link, how to sign in, how to
stop it (q in an attached run_local, just stop_local --instance <name> for
headless, or the background Vite process), and anything that failed or was
skipped.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Wrap a new backend endpoint in the TypeScript SDK (packages/sdk), or record it as skipped. Use when `just coverage` fails, or after adding an endpoint to a Rust service.
The English summary is being prepared. Showing the original description.
Add or change an in-app feature tour (a view's guided flyover) in the web app. Use when adding a tour to a view, adding or editing tour steps, pointing a step at a new control, or when a step's target needs something opened first.
The English summary is being prepared. Showing the original description.
Post-change checks before handing off. Works out which checks apply from the files changed (directory AGENTS.md Checks sections and matching .agents/rules), runs or verifies each, and reports pass/fail/skipped. Use before saying work is done, before pushing, or when asked to audit or verify a change.
The English summary is being prepared. Showing the original description.
Enforce hexagonal architecture in the Rust backend. Use before modifying crates/ or Rust services, especially inbound axum/tool/listener adapters, domain services/ports, outbound adapters, authorization, permissions, database access, or external clients.
The English summary is being prepared. Showing the original description.
Use when adding collaborative markdown, notes, or descriptions to a feature with collab surfaces. Covers parent entities, service entry points, authorization, content storage, and lifecycle.
The English summary is being prepared. Showing the original description.
Build a new AI tool end-to-end — Rust implementation, toolset wiring, infra, schema generation, and frontend UI.
The English summary is being prepared. Showing the original description.