How do I install the Run UI Debug skill?

Run npx skillmds@latest add tomevault-io/run-ui-debug in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Run UI Debug safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Run UI Debug?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Run UI Debug free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Run UI Debug?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Run UI Debug by tomevault-io — Agent Skill

Name: Run UI Debug
Author: tomevault-io

Run UI Debug

Start the RV webserver UI in development/debug mode — Python backend (uvicorn, port 8000) plus React dev server with hot reload (port 3000) — following webserver/Makefile's server_start and client_start targets. Use when the user asks to "run the UI in debug mode", "start the dashboard for development", or "launch the webserver locally". Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Run Webserver UI in Debug Mode

Launches the webserver/ app the way the Makefile intends for active development: the Python backend first, then the React dev server with hot reload. This is not the production build (make build) — both processes stay in the foreground with live logs and auto-reload on save.

Paths below are relative to /home/tblank/code/tblank1024/rv/webserver/.

Pre-flight

Confirm venv/ exists (created by make setup). If missing, tell the user to run make setup first — don't create it yourself, it installs ~600MB of dependencies.
Confirm client/node_modules/ exists. If missing, the user needs make setup (it runs npm install --legacy-peer-deps).

Start the backend (must come up first)

Run in the background so you can keep working and stream its log:

cd webserver/server && ../venv/bin/python ./server.py

Use run_in_background (Bash) and watch the output for:

<ip> 8000 — printed constants confirming it bound to port 8000
Server startup: Current internet connection is '...'
any traceback — surface it to the user immediately rather than continuing

The backend serves on http://0.0.0.0:8000 (uvicorn, single worker, log_level=warning).

Start the client (only after the backend is up)

cd webserver/client && npm start

Also run in the background. react-scripts start opens the CRA dev server on http://localhost:3000 with hot module reload — code edits in client/src apply live without a restart.

Report back to the user

Backend: http://localhost:8000
Frontend (open this in a browser): http://localhost:3000
Both processes are running in the background; mention how to stop them (Ctrl-C in their terminals, or TaskStop if launched as background tasks).

Notes

If the user changed client/src/constants.js, remind them to run make constants_copy (or make build, which includes it) — the dev server does not regenerate server/constants.json automatically.
Don't run make build for this — that's the production bundle path and shuts down the dev hot-reload workflow.

Source: tblank1024/rv — distributed by TomeVault.

---name: run-ui-debugdescription: Start the RV webserver UI in development/debug mode — Python backend (uvicorn, port 8000) plus React dev server with hot reload (port 3000) — following webserver/Makefile's server_start and client_start targets. Use when the user asks to "run the UI in debug mode", "start the dashboard for development", or "launch the webserver locally". Use when this capability is needed.---# Run Webserver UI in Debug ModeLaunches the `webserver/` app the way the Makefile intends for active development:the Python backend first, then the React dev server with hot reload. This is**not** the production build (`make build`) — both processes stay in theforeground with live logs and auto-reload on save.Paths below are relative to `/home/tblank/code/tblank1024/rv/webserver/`.## Pre-flight1. Confirm `venv/` exists (created by `make setup`). If missing, tell the user to run `make setup` first — don't create it yourself, it installs ~600MB of dependencies.2. Confirm `client/node_modules/` exists. If missing, the user needs `make setup` (it runs `npm install --legacy-peer-deps`).## Start the backend (must come up first)Run in the background so you can keep working and stream its log:```cd webserver/server && ../venv/bin/python ./server.py```Use `run_in_background` (Bash) and watch the output for:- `<ip> 8000` — printed constants confirming it bound to port 8000- `Server startup: Current internet connection is '...'`- any traceback — surface it to the user immediately rather than continuingThe backend serves on `http://0.0.0.0:8000` (uvicorn, single worker, `log_level=warning`).## Start the client (only after the backend is up)```cd webserver/client && npm start```Also run in the background. `react-scripts start` opens the CRA dev server on`http://localhost:3000` with hot module reload — code edits in `client/src`apply live without a restart.## Report back to the user- Backend: `http://localhost:8000`- Frontend (open this in a browser): `http://localhost:3000`- Both processes are running in the background; mention how to stop them (Ctrl-C in their terminals, or `TaskStop` if launched as background tasks).## Notes- If the user changed `client/src/constants.js`, remind them to run `make constants_copy` (or `make build`, which includes it) — the dev server does not regenerate `server/constants.json` automatically.- Don't run `make build` for this — that's the production bundle path and shuts down the dev hot-reload workflow.---> Source: [tblank1024/rv](https://github.com/tblank1024/rv) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions