--- name: run- description: Build, run, and drive . Use when asked to start , run its tests, build it, take a screenshot of its UI, or interact with the running app. --- /driver.mjs` under xvfb" for a desktop app, or "start the dev server then drive it via `chromium-cli`" for a web app — so an agent knows where to look first.> All paths below are relative to `/`. ## Prerequisites ```bash sudo apt-get update sudo apt-get install -y ``` ```bash # Example: Node 20 via nvm, Python 3.12 via uv, etc. ``` ## Setup ```bash ``` ```bash export FOO_API_KEY=... # required — get from export BAR_MODE=dev # optional — default is prod ``` ## Build ```bash ``` ## Run (agent path) ```bash ``` ```bash tmux new-session -d -s app -x 200 -y 50 tmux send-keys -t app '' Enter timeout 30 bash -c 'until tmux capture-pane -t app -p | grep -q ""; do sleep 0.2; done' tmux send-keys -t app '' Enter tmux capture-pane -t app -p ``` Screenshots → `/tmp/shots/`. Logs → `/tmp/.log`. | command | what it does | |---|---| | `` | | ## Run (human path) ```bash # → . . ``` ## Test ```bash ``` --- ## Gotchas - **** — → ## Troubleshooting - ****: . . <--- NOTE ON THE FRONTMATTER ABOVE: - Replace in both `name:` and `description:`. The `name:` becomes the slash command (/run-) and must match the directory name. - The `description:` is what Claude scans to decide whether to load this skill automatically. Keep the verbs — "start," "run," "build," "test," "screenshot" — they're what an asking agent will actually type. NOTE ON THE DRIVER: - If you wrote a driver script, it lives in this same directory (next to this file) by default. Reference it from the Run section. - For a web app there's usually no driver file — the `chromium-cli` heredoc in the Run section is the harness. - If the driver grows into something the project's test suite wants — shared launch helpers, a real e2e harness — move it to scripts/ or e2e/ in the unit, and update the paths here. The skill stays put. Delete everything from `---` above onwards before committing. --->