site-launch
Quality checks before a website goes live, or for auditing one that already is — "is this ready to ship", "why does my link look blank when I share it", "the site has no analytics", "add an RSS feed". The checklist of things a site needs that aren't visible on the page itself.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- site-launch
- description
- Quality checks before a website goes live, or for auditing one that already is — "is this ready to ship", "why does my link look blank when I share it", "the site has no analytics", "add an RSS feed". The checklist of things a site needs that aren't visible on the page itself.
- allowed-tools
- Read, Grep, Glob, Bash
- user-invocable
- true
02 资源文件 4
- 脚本scripts/site_launch_cli.py25.1 KB
- 脚本scripts/site-launch486 B
- 脚本scripts/test_site_launch_wrapper.py2.0 KB
- 脚本scripts/test_site_launch.py23.5 KB
03 SKILL.md 正文
Site Launch
Everything a site needs that you can't see by looking at it: what happens when someone shares
it, subscribes to it, or searches for it. ui-designer owns how it looks. None of these break
the build, so none get noticed until someone links the site somewhere.
Stack-agnostic: implement each item with whatever the project already uses before reaching for a new dependency.
Run the checker
skill-tree site-launch ./dist # the built output, not src/; `check` is implied
skill-tree site-launch ./dist --json # same verdicts, machine-readable
If skill-tree isn't on PATH:
"${CLAUDE_PLUGIN_ROOT:-${SKILL_TREE_DIR:-$HOME/projects/skill-tree}}/skills/site-launch/scripts/site-launch".
Claude: delegate the run to the checker-summarizer subagent. No subagents: run it
yourself.
Exit 0 = nothing failed, 1 = a FAIL, 2 = nothing to check. Each item is PASS, FAIL,
NA, or MANUAL (5, 8, 9 need the deployed origin; it prints the command to run). Every FAIL
and MANUAL item carries a fix: block (guidance in JSON) — the requirement, the why, and how
to confirm it. That is the checklist; act on it.
The checker proves absence, not adequacy: it can say og:image is missing, not that the image
is any good. Every confirmation runs against the deployed origin — the dev server hides
broken absolute URLs, missing build-time assets, and redirect misconfiguration.
The items
- Absolute base URL · 2. Titles and descriptions · 3. Share card · 4. Feed · 5. Analytics ·
- robots.txt and sitemap · 7. Favicon and 404 · 8. Security headers · 9. Works before announcing
Applying this to an existing site
Report what's missing before changing anything, in order — 1 and 2 are upstream of most of the rest, and fixing 3 before 1 produces share cards pointing at relative paths. When an item is already satisfied, say so and move on; don't swap a working implementation for one you'd prefer.
04 同仓库更多 Skills
wait-what
Stop. Your plan/idea did not land. Re-pitch it.
verify
Verify before answering whether something works, still passes, is gone, is used, or is correct — and whenever the user says "can you confirm", "are you sure", "did that actually work", or reports something is "still" broken. Produces the answer plus the evidence that would have falsified it. A failed GitHub Actions run is skill-tree:debug-ci instead.
ui-designer
Design or restyle a web UI — landing pages, dashboards, docs sites, app chrome — or when the user asks why a site "looks generic", "looks like a template", or wants it to feel intentional. A running list of design lessons learned, applied as rules rather than suggestions.
two-axis-review
Two-axis review of changes since a fixed point (commit, tag, HEAD~N, or default HEAD~1): Standards (does the code follow this repo's conventions?) and Spec (does the code do what it should?). Axes run as parallel sub-agents so neither masks the other. Use when the user says "review against the spec", "does this follow our conventions", "standards and spec review", or "two-axis review". Not a correctness bug hunt — that's the built-in `/code-review`.
tui-screenshots
Use for generating or refreshing TUI screenshots for docs — "regenerate the screenshots", "the README screenshots are stale". Drives a Textual/TUI app headlessly and exports SVG. Not for reading a user's screenshot — that is `screenshot`.
to-tickets
Break a spec, plan, or conversation into tracer-bullet vertical-slice tickets with blocking edges — "turn this into tickets", "break this down", "what's the work?". Pairs with skill-tree:to-spec upstream and skill-tree:handoff downstream.