菜单
Start or stop the skymap Vite dev server in the current worktree. Use when the user types `/dev` or `/dev-stop`, or asks to "start the dev server", "spin up dev", "kill the dev server", or similar. Backgrounds `npm run dev` and reports the URL; reuses the running server if one exists in this session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when measuring, claiming, or investigating anything about render performance — before AND after any renderer/shader/perf change, or when asked "why is this slow?". Runs the headless GPU-timing harness and interprets it correctly.
Use when a feature substantial enough for a spec/plan has converged in brainstorming and the spec is about to be written — or standalone, when the user asks "I'm about to add X, what should move first?". Triggers like "/refactor-ground", "add <capability>" (a new source, layer, effect, POI category, tour primitive, settings group), or any ask where existing structure must grow to host new functionality. Skymap-specific; complements entanglement-radar (finds existing knots) — this asks whether the joints the feature needs exist at all.
Use when performing a mechanical code refactor in skymap. Rename a symbol repo-wide, extract a symbol into its own file, inline or delete a passthrough wrapper, find who uses a symbol, or move/reorganize `.ts`/`.tsx` files. Triggers like "/refactor", "rename this function everywhere", "extract X into its own file", "inline this wrapper", "delete this unused helper", "who uses this symbol", "move X to Y", "rename this file", "update all the imports", "reorganize the utils folder", "shift these renderers into a subfolder", "folder reorg".
Use when adding a new data source or featured category to skymap — a new survey catalog feeding the point cloud, or (the common case) a new featured structure category / POI type rendered as marker rings + labels (cluster / supercluster / void / group are the existing four). Triggers like "add a data source", "add a new structure category", "add galaxy groups / walls / a new POI layer", "wire up a new survey". Maps the full edit surface so no parallel site is missed.
Audit a plan against the Definition-of-Done gate before marking it complete. Use when the user types `/feature-done`, asks to "verify the plan is done", "check DoD on <plan>", or is about to close out a feature. Runs the static checks (tests, typecheck, TODO scan, modified-file inventory) and reports a pass/fail summary so unfinished business doesn't get rubber-stamped.
Create OR change a React component in `src/components/` following skymap's conventions — own folder, `<Name>.tsx` + `<Name>.module.css`, single-component-per-file, `function Name() {}` + `export default Name`, top-level `.root` class, shared vocabulary in a minimal shared module via `composes` (never `:global`). Use when the user types `/create-component`, asks to "make a component", "add a component", "extract this into a component", or "split this component up" — and, just as important, load it BEFORE editing, refactoring, restructuring, or restyling ANY existing `src/components/**` file (changing its props, markup, exports, or CSS), to check the change against the conventions. Also use proactively whenever a component file is growing past ~120 lines or starts handling more than one concern — the *right* time to create a new component is before the parent gets messy, not after.
| name | dev |
| description | Start or stop the skymap Vite dev server in the current worktree. Use when the user types `/dev` or `/dev-stop`, or asks to "start the dev server", "spin up dev", "kill the dev server", or similar. Backgrounds `npm run dev` and reports the URL; reuses the running server if one exists in this session. |
This skill defines two slash commands for managing the Vite dev server in the
current worktree. Worktrees can run multiple servers simultaneously because
Vite's port (5173 in vite.config.ts) is non-strict — collisions auto-increment
to the next free port.
The skill leans entirely on the Claude Code harness's run_in_background Bash
behavior — output streams to the harness footer, is readable via BashOutput,
and the shell can be killed via KillShell. No PID files, no /tmp logs, no
lsof discovery.
/dev — start (or report) the dev serverCheck for an existing shell. If you started a dev server in this session
and remember the shell ID, call BashOutput on it. If it's still running
and its output contains a Local: http://localhost:<port>/ line, report
that URL and exit. Do not spawn a duplicate.
Launch. Run npm run dev with run_in_background: true. Capture the
returned shell ID.
Wait for the Local: line. Poll BashOutput on the new shell. Vite
normally prints Local: http://localhost:<port>/ within 1–2 s, but cold
starts (first WESL compile, fresh tsx) can take longer. Allow up to 15 s.
Report. Extract the port with a regex like Local:\s+http://localhost:(\d+)/.
Print one line: Dev server: http://localhost:<port> (shell <id>).
On timeout (no Local: line within 15 s): dump the last ~30 lines of
BashOutput so the failure is visible (WESL linker error, missing
dependency, port range exhausted, etc.). Do not retry automatically.
/dev-stop — kill the dev serverIf a shell ID is known, call KillShell on it. Read the recorded port
from earlier and report: Stopped dev server (was on <port>).
If no shell ID is known (fresh session, or you've forgotten it), tell
the user — don't go hunting via lsof or pkill. Session-scoped lifecycle
means a forgotten shell will be reaped when the session ends anyway.
/tmp logs, and
lsof discovery were considered and rejected as unnecessary state./tmp/skymap-dev-*.log or .claude/dev-pid file. The
harness's BashOutput is the log; the shell ID is the handle.--port <N> flag to npm run dev. Vite's auto-increment is
what makes multiple worktrees coexist without coordination.vite.config.ts's port: 5173 to strictPort: true. That
would break the auto-increment behavior this skill relies on.