Menu
Understand how much of a Swift framework runtime implements, by framework and type. Use when the user asks about Foundation/SwiftUI/stdlib coverage, what APIs are implemented/missing/verified, or which framework APIs to build next.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
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".
Baseado na classificação ocupacional SOC
| name | framework-coverage |
| description | Understand how much of a Swift framework runtime implements, by framework and type. Use when the user asks about Foundation/SwiftUI/stdlib coverage, what APIs are implemented/missing/verified, or which framework APIs to build next. |
Use the top-down coverage workflow:
cargo test -p tswift-std dump_registered_keyscargo test -p tswift-foundation dump_registered_keyspython3 tools/framework-inventory/coverage.py --framework foundationpython3 tools/framework-inventory/coverage.py --framework stdlibpython3 tools/framework-inventory/coverage.py --framework foundation DataArtifacts:
tools/framework-inventory/frameworks.tomlframeworks/<name>/scope.tomlframeworks/<name>/inventory.md (docs/swift-runtime/stdlib-inventory.md for stdlib)frameworks/<name>/registered_keys.txtcrates/tswift-cli/tests/fixtures/<framework>_*.swift