菜单
Keeps the tswift project website in sync with runtime implementation changes — coverage numbers, feature tables, WASM binary, and content. Use when features are implemented, coverage changes, the runtime is updated, or the user asks to update/sync/refresh the website.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Autonomous developer iteration loop driven by a thin orchestrator that dispatches coder/reviewer/diagnoser subagents. Pick a mode — fix (make tests green), feature (implement one or more features), optimize (push a metric), debug (root-cause a failure), ab-test (race candidate implementations), or prototype (explore design variants) — define a verification signal, confirm the plan with the user, then loop implement → verify → review → commit with all state kept in loop-log.md. Use when the user states a concrete engineering goal or says "keep iterating", "loop on this", "autoloop", or "iterate until fixed".
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Spawn a pi subagent to handle a specific task in a separate process. Use when the user asks to delegate work to a subagent, run a task in parallel, or says "spawn a subagent", "use a subagent", or "run this with pi".
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
| name | update-website |
| description | Keeps the tswift project website in sync with runtime implementation changes — coverage numbers, feature tables, WASM binary, and content. Use when features are implemented, coverage changes, the runtime is updated, or the user asks to update/sync/refresh the website. |
The website lives in website/. Content is in MDX — easy to edit. See FILE-MAP.md for the full map.
website/src/pages/status/language.mdxwebsite/src/pages/status/stdlib.mdxwebsite/src/pages/status/foundation.mdxhow-it-works/*.mdxIn each status MDX file, change the status column:
| Symbol | Meaning |
|---|---|
✅ | Fully done |
🟡 | Partial |
⬜ | Todo |
After updating the tables, recount done/total and update every <CoverageBar> that was affected. The bars appear in:
<CoverageBar label="Tier 0 — Lexical" done={N} total={M} />)website/src/pages/status/index.astro — the dashboard (update the matching bar and the .pct-big number in the status card)To count: grep the MDX file for | ✅ (done) and | 🟡 (partial counts as done for the bar), total is the row count.
npm run build now automatically rebuilds the WASM before the Astro build
(via the build:wasm pre-step), so no manual wasm-pack invocation is needed.
cd website
npm run build # runs wasm-pack + astro build; must complete with 0 errors, 11 pages
To rebuild WASM alone (e.g. to test the playground without a full site build):
cd website
npm run build:wasm
If the build fails, check for {#anchor} syntax in MDX headings — replace with plain headings (MDX parses {...} as JSX).
git add website/
git commit -m "docs(website): update coverage for <what changed>"
{#anchor-id} to MDX headings — the MDX JSX parser rejects them./* @vite-ignore */ — don't remove that comment.cd website && npm run dev (hot-reloads MDX changes instantly).