メニュー
Understand how much of the Swift standard library the runtime implements, by section and by member. Use when the user asks about stdlib coverage, what's implemented/missing/verified, which APIs to build next, or when planning stdlib work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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".
| name | stdlib-coverage |
| description | Understand how much of the Swift standard library the runtime implements, by section and by member. Use when the user asks about stdlib coverage, what's implemented/missing/verified, which APIs to build next, or when planning stdlib work. |
Measures the runtime's Swift stdlib implementation against the full reference
surface (docs/swift-runtime/stdlib-inventory.md). Each member is classified:
tswift-std registry.Always go overall → section. Don't read the inventory by hand.
Refresh the registry snapshot (cannot drift — reads the live registry):
cargo test -p tswift-std dump_registered_keys
Check overall coverage first — list every targeted section with impl/verified/total counts and the overall roll-up:
python3 tools/stdlib-inventory/coverage.py
Use this to spot the lowest-coverage sections. Add --all to include
sections with no coverage yet.
Then drill into one section — member-by-member, grouped into verified / implemented / missing:
python3 tools/stdlib-inventory/coverage.py Array
python3 tools/stdlib-inventory/coverage.py "free functions"
The missing group is the concrete to-do list for that section.
tools/stdlib-inventory/README.md. Plan context:
docs/plan/stdlib-support.md §2/§4.2.