菜单
Start the dev-dashboard web server and display the URL. Detects if the server is already running, finds an available port if needed. Use when the user wants to open, start, or launch the dev-dashboard.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | dev-dashboard |
| description | Start the dev-dashboard web server and display the URL. Detects if the server is already running, finds an available port if needed. Use when the user wants to open, start, or launch the dev-dashboard. |
| allowed-tools | Bash(bash:*) |
Start the dev-dashboard server (or reuse an existing instance) and display the URL.
The dashboard runs entirely from the bundled launcher in this skill — there is no
~/.local/bin install step and no command shims to manage.
Run the bundled start script directly by absolute path:
bash "$SCRIPTS/start.sh" --open
Where $SCRIPTS is the absolute path to scripts/ within this skill's directory. Use $HOME instead of literal home paths.
start.sh resolves the bundled server relative to its own location, reuses an
already-running instance if one is found (matched across plugin versions), or
starts a fresh one on the configured port (falling back to a nearby free port).
--open also opens the dashboard in the browser. The server binds to 127.0.0.1
(localhost only) by default.
To stop the server, run the bundled stop script:
bash "$SCRIPTS/stop.sh"
The launch command outputs one of:
running:<port> — server was already runningstarted:<port> — new server startederror:<message> — something went wrongOn success, display:
Dev Dashboard: http://localhost:<port>
If it was already running, add "(already running)".
On error, show the error message.
If the error came from the launch command, suggest checking /tmp/dev-dashboard.log.
Save progress and generate a continuation prompt. Updates PRD status markers, captures git state, and writes checkpoint.md for the next session. Use at the end of a session or before switching context.
Plan a new feature with structured PRD documentation. Researches codebase patterns, designs implementation phases, and writes PRD files to .dev/. Use when starting a new feature, spike, or major task.
Resume work from a previous session checkpoint. Uses `resume-context` CLI to load feature, checkpoint, git state, and session history in a single call, then synthesizes a focused resumption summary before continuing. Use at the start of a new session to restore context from a previous checkpoint.
Generate a concise, scannable alignment report (tables + bullets) comparing a feature's PRD against the actual implementation. Spawns a fresh reporter subagent that explores the codebase and reports deviations, future-affecting constraints, and untested areas — then offers to apply the doc corrections it surfaces back to the PRD/checkpoint. Use when implementation is finished (or nearly), before final testing.
Generate and browse the cross-project wiki index. Creates a navigable markdown wiki from .dev/ and .dev-archive/ PRDs, ready for Obsidian or any markdown viewer.
Review the current session for learnings and self-improvement signals. Surfaces memory candidates and improvement opportunities for user-confirmed application. Use after completing work to review the session for learnings and improvement signals.