菜单
Use when launching, starting, running, or driving the Panda desktop app (Tauri shell + Vite viewer) — to see a change live, smoke-test the chat/CAD UI, or keep the app running across steps. Covers cargo-not-on-PATH, the blank-window dev port footgun, and detached/persistent launch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to create, edit, or print a parametric 3D model from a natural-language description — "phone stand", "wall mount", "honeycomb tray", "GoPro adapter", "vase" — or to tweak, re-render, or fix an existing CadQuery `.py` part for hobbyist 3D printing.
Enrich a short or vague 3D-object prompt into a detailed, print-ready design brief before modeling. Use when the user asks for an object in a few words — "phone stand", "wall hook", "pen holder", "planter", "GoPro mount" — and the request lacks dimensions, features, style, or ergonomic detail. Analyzes the intended shape and returns a structured brief with popular, well-considered defaults so the generated object comes out refined and appealing rather than generic.
Use when the user asks to develop, build, implement, or add a new FEATURE end-to-end in the Panda desktop app and wants it taken all the way to a pull request. Triggers on "build/add/implement a feature", "ship this", "take it to a PR" for multi-step work touching the viewer / cadpy / cadjs / tauri / skills layers. NOT for one-line fixes, bug triage, questions, or edits with no PR.
Start or reuse CAD Viewer and return review links for explicit CAD, robot-description, and G-code files. Use when visually reviewing `.step`, `.stp`, `.stl`, `.3mf`, `.gcode`, `.dxf`, `.urdf`, `.srdf`, or `.sdf` files, especially when handed off from CAD, URDF, SRDF, or SDF generation skills.
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers, bearings, standoffs, and other catalog components. Use when Codex needs to search the hosted step.parts catalog before creating simplified placeholder geometry, resolve fuzzy part names, standards, aliases, or dimensions, choose a matching part, fetch a canonical .step file, verify checksums, or use the step.parts API/OpenAPI/catalog endpoints for standard part discovery.
| name | running-panda |
| description | Use when launching, starting, running, or driving the Panda desktop app (Tauri shell + Vite viewer) — to see a change live, smoke-test the chat/CAD UI, or keep the app running across steps. Covers cargo-not-on-PATH, the blank-window dev port footgun, and detached/persistent launch. |
Panda is a Tauri 2 desktop app: a Rust shell (desktop/src-tauri/) that loads a
Vite + React frontend (viewer/). "Running it" means both halves up at once:
Vite serving the frontend, the Rust binary showing a window pointed at it.
.claude/skills/running-panda/launch.sh
This builds (incremental), starts Vite on the shell's devUrl port, launches the
app detached so it survives the calling shell, waits, and prints the pid.
Logs: ~/.panda-run/{vite,app}.log. It only recycles a prior instance of this
dev build and refuses to start if another Panda app is already running (see
Safety below). Stop the instance it started with its printed pid:
kill <printed-pid> # the app pid launch.sh reported
A chat turn is a child process of the app. The Rust driver spawns the
claude turn (and its Python cadcode generator) as children — they are NOT
detached. Kill the app process and you abort the user's in-flight turn; nothing
keeps running in the background, and the UI freezes waiting on an event stream
from a process that's gone. The on-disk session is preserved (Panda --resumes
the same per-project session), so the user can re-send their last message to
continue — but the running turn itself is lost.
Therefore: never pkill -f panda-desktop or pkill -f vite. On a shared box
that also matches a packaged Panda.app and other users' dev servers. Target a
specific pid, or the exact dev-build path, or the Vite port — which is what
launch.sh does.
scripts/dev.sh?scripts/dev.sh is the repo's hand-launch path and it works — but it runs
cargo run in the foreground, so when the caller ends (an agent Bash task, a
CI step), its EXIT trap stops Vite and the window dies with it. launch.sh
nohup/disowns both halves so the app keeps running across turns. Use dev.sh
when you'll babysit it in a real terminal; use launch.sh to leave it running.
| Symptom | Cause | Fix |
|---|---|---|
cargo: command not found | cargo is rustup-installed, not on a non-login shell's PATH | export PATH="$HOME/.cargo/bin:$PATH" (cargo 1.96 lives there) |
| Window opens blank | bare npm run dev serves Vite on its own default 4178; the shell loads build.devUrl = 5173 → nothing to load | start Vite with VIEWER_PORT=5173 (parsed from tauri.conf.json) |
permission denied writing logs | shared box has stale /tmp/<fixed-name> owned by another user (e.g. nhat) | write logs under ~/.panda-run/ (a dir you own) |
| App exits right after launch | cargo run torn down with the parent foreground task (the IMKCFRunLoopWakeUpReliable line is benign) | launch the binary detached (nohup … & disown) |
The binary staying alive proves the entrypoint resolved — it does not prove the window rendered. Check all three:
pgrep -fl panda-desktop # process alive
lsof -iTCP:5173 -sTCP:LISTEN -n -P | grep -c LISTEN # Vite serving (expect 1)
osascript -e 'tell application "System Events" to get name of every process whose name contains "panda"' # GUI process registered
A blank window = launch failure (almost always the port footgun). Check
~/.panda-run/app.log and ~/.panda-run/vite.log.
scripts/build/build-app.sh needs the Tauri CLI (not a project dep) plus ~1 GB
of bundled CPython + OrcaSlicer sidecars (scripts/build/build-all-sidecars.sh).
That's a shipping build, not a dev launch. Only go there when the ask is
specifically for a packaged .app.
The user-facing loop is chat → CAD → slice → print. To exercise a change,
type a CAD ask in the chat input (e.g. "phone stand"): plan → approve → build.
Watch the turn land via ~/.claude/projects/<encoded-workspace>/<uuid>.jsonl
(if it's never created, the launch-PATH footgun ate claude/node — but that
only bites the packaged .app, not this dev launch). The 3D viewer previews the
generated .stl.