stdlib-coverage

Étoiles12

Forks0

Mis à jour27 juin 2026 à 08:11

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

siuying

siuying/tswift

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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.

Stdlib coverage

Measures the runtime's Swift stdlib implementation against the full reference surface (docs/swift-runtime/stdlib-inventory.md). Each member is classified:

missing — not in the tswift-std registry.
implemented — in the registry (declared coverage).
verified — in the registry and exercised by a passing CLI golden fixture.

Workflow — top-down, two steps

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.

Notes

Section names match inventory headings, case-insensitive; an unknown name prints close matches.
After registering a new stdlib intrinsic, re-run step 1 so the report is current.
Tooling details: tools/stdlib-inventory/README.md. Plan context: docs/plan/stdlib-support.md §2/§4.2.

Plus depuis ce dépôt

même dépôt

autoloop

siuying/tswift

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".

2026-07-0412

to-issues

siuying/tswift

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

2026-07-0212

to-prd

siuying/tswift

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.

2026-07-0212

triage

siuying/tswift

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

2026-07-0212

update-website

siuying/tswift

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.

2026-07-0112

pi-subagent

siuying/tswift

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".

2026-06-2812

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.

Stdlib coverage

Measures the runtime's Swift stdlib implementation against the full reference surface (docs/swift-runtime/stdlib-inventory.md). Each member is classified:

missing — not in the tswift-std registry.
implemented — in the registry (declared coverage).
verified — in the registry and exercised by a passing CLI golden fixture.

Workflow — top-down, two steps

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.

Notes

Section names match inventory headings, case-insensitive; an unknown name prints close matches.
After registering a new stdlib intrinsic, re-run step 1 so the report is current.
Tooling details: tools/stdlib-inventory/README.md. Plan context: docs/plan/stdlib-support.md §2/§4.2.