run
Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- License 许可
- CC0-1.0
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- run
- description
- Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
02 资源文件 6
- 参考文档examples/cli.md1.5 KB
- 参考文档examples/electron.md14.0 KB
- 参考文档examples/library.md2.0 KB
- 参考文档examples/playwright.md3.5 KB
- 参考文档examples/server.md3.2 KB
- 参考文档examples/tui.md3.0 KB
03 SKILL.md 正文
Running means launching the actual app and interacting with it -
not the test suite, not an import of an internal function and a
console.log. The app as a user (human or programmatic) would meet
it: the CLI at its command, the server at its socket, the GUI at its
window.
First: does a project skill already cover this?
A project skill that launches this app is the repo's verified path -
its author already cold-started from a Linux container and committed
what worked: the exact apt-get line, the env vars, the patches, the
driver. Use it instead of rediscovering.
d=$PWD; while :; do
grep -Hm1 '^description:' "$d"/.claude/skills/*/SKILL.md 2>/dev/null
[ -e "$d/.git" ] || [ "$d" = / ] && break
d=$(dirname "$d")
done
- One describes launching/driving this app -> read that SKILL.md and follow it verbatim. Don't paraphrase; don't skip the patches.
- Mega-repo, several plausible, no clear match -> ask the user which unit to run.
- Stale (fails on mechanics unrelated to your task) -> tell the
user; offer to refresh it via
/run-skill-generator. - Nothing about running -> fall back to the patterns below.
Otherwise: match the shape, use the pattern
Pick the row closest to your project. Each example walks through launch + first interaction; ignore any trailing "write the skill" section - you're using the recipe, not authoring one.
| Project type | Handle | Example |
|---|---|---|
| CLI tool | direct invocation, exit code, stdin/stdout | examples/cli.md |
| Web server / API | background launch + curl smoke |
examples/server.md |
| TUI / interactive terminal | tmux send-keys / capture-pane |
examples/tui.md |
| Electron / desktop GUI | Playwright _electron REPL under xvfb |
examples/electron.md |
| Browser-driven | dev server + chromium-cli script |
examples/playwright.md |
| Library / SDK | import-and-call smoke script at the package boundary | examples/library.md |
If nothing fits, start from the closest match and adapt. For a web
app, examples/playwright.md - drive it with
chromium-cli, no custom driver needed. For a desktop app,
examples/electron.md - it has the _electron
REPL driver skeleton and the tmux wrapping.
Drive it, don't just launch it
Launching with no interaction proves the entrypoint resolves. That's not running the app - it's typechecking with extra steps. Drive it to a point where a user would see something:
- CLI -> type a representative command, check the exit code and output.
- Server -> hit the route the diff touches with
curl, read the body. - TUI ->
send-keysa navigation,capture-panethe result. - GUI -> click the button, screenshot the window. Look at the screenshot. A blank frame is a failure to launch.
If the fallback pattern didn't work out of the box - you had to
install packages, set env vars, patch config, or write a driver -
recommend /run-skill-generator in your report so that work gets
captured as a project skill. If it just worked, don't.
04 同仓库更多 Skills
model-council
暂无简介
writing-style
Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.
write-page
Create or edit requested Page/Space content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.
software-engineering
For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work, not a general programming explanation.
slides-artifact
Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation advice or a chat-only outline.
slack
Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.