with one click
explain-swiftasb
// Explain SwiftASB in user-facing terms, including what it does, what it does not do, adoption tradeoffs, licensing, and when it is or is not the right foundation for a Swift app or package.
// Explain SwiftASB in user-facing terms, including what it does, what it does not do, adoption tradeoffs, licensing, and when it is or is not the right foundation for a Swift app or package.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | explain-swiftasb |
| description | Explain SwiftASB in user-facing terms, including what it does, what it does not do, adoption tradeoffs, licensing, and when it is or is not the right foundation for a Swift app or package. |
| license | Apache-2.0 |
| compatibility | Designed for Codex and compatible Agent Skills clients working with SwiftASB v1.3.1 or newer, Swift 6, SwiftPM, SwiftUI, AppKit, and local Codex app-server integrations. |
| metadata | {"owner":"gaelic-ghost","repo":"socket","package":"SwiftASB","category":"swiftasb-explanation"} |
| allowed-tools | Read Bash(rg:*) Bash(git:*) |
Help a user understand whether SwiftASB is the right foundation for their Swift app, tool, or package before implementation starts.
Start with the real job: SwiftASB lets Swift code drive the local Codex app-server through a Swift-native API. It owns the local Codex subprocess, typed request and response conversion, app-wide stored-thread library state, stable worktree groups, repository/worktree filters, selected-worktree Git status, project identity and thread-source facts, app-server-owned worktree snapshots, app-server-routed filesystem/config/extension/MCP-resource reads, workspace permission facts, SwiftASB feature policy, feature-operation events, thread and turn handles, interactive request handling, diagnostics, local history reads, and SwiftUI-friendly observable companions.
Before giving exact API claims, inspect the current SwiftASB source of truth:
README.mdSources/SwiftASB/SwiftASB.docc/Sources/SwiftASB/SwiftASB.docc/FeaturePermissionPolicy.mdSources/SwiftASB/Public/As of SwiftASB v1.3.1, the supported public surface centers on:
CodexAppServer, the owner of the local Codex subprocess, one-call startup, stored-thread operations, app-wide library creation, MCP resource reads, diagnostics, feature-operation-event streams, and capability readsCodexAppServer.start(_:), CodexAppServer.StartupRequest, CodexAppServer.StartupSession, CodexAppServer.StartupCompatibilityPolicy, and CodexAppServerStartupError for normal startup, reviewed support-window validation, initialization, selected-CLI diagnostics, and typed startup failure handlingCodexAppServer.Library, the app-wide observable companion for stored-thread lists, cwd or repository grouping, stable worktree groups, repository/worktree filters, selected worktree or repository context, selected-worktree Git status, CodexWorkspace.ProjectInfo project identity, CodexAppServer.ThreadSource source badges, and model/MCP/hook snapshotsCodexAppServer.fs, CodexAppServer.config, and CodexAppServer.extensions for app-server-owned filesystem reads, effective config reads, app/skill/plugin/collaboration-mode inventory, plugin detail reads, and already-configured marketplace upgradesCodexAppServer.readMcpResource(_:) for app-wide or thread-scoped MCP resource contents advertised by configured serversSwiftASBFeaturePolicy, SwiftASBFeatureCategory, SwiftASBHostAccess, and SwiftASBFeatureOperationEvent for app-wide feature-category defaults, host-access declarations, mutation visibility, and quiet read-only observabilityCodexWorkspace for app-server-owned cwd, worktree snapshots, project identity, Git repository facts, selected Git status snapshots, filesystem, network, and permission-profile facts on thread sessions and requestsCodexThread, the handle for one Codex conversation threadCodexTurnHandle, the handle for one active turnCodexAppServer.ThreadListQD, CodexFS.FileDiscoveryQD, CodexThread.HistoryWindowQD, CodexThread.RecentFilesQD, and CodexThread.RecentCommandsQDCodexAppServer.ThreadListSourceKind and CodexAppServer.ThreadSourceCodexThread.Dashboard, CodexTurnHandle.Minimap, RecentTurns, RecentFiles, and RecentCommandsGenerated CodexWire... models are internal scaffolding, not the recommended app-facing API.
v1.3.1, verify behavior against Codex CLI 0.130.x before assuming a newer schema family is publicSwiftASB is a good fit when the user needs a Swift app or package to:
SwiftASB is probably not the right first choice when the user needs:
Answer in this order:
Recommendation: one direct fit call.What SwiftASB would do here: plain-language role.What the app would own: UI, product behavior, persistence choices, and user policy.What SwiftASB would own: app-server process, app-wide library state, worktree groups and filters, selected Git status, project identity, thread source, filesystem/config/extension/MCP-resource/workspace reads, feature policy, feature-operation events, typed thread and turn API, events, requests, diagnostics, query descriptors, and companions.Tradeoffs: runtime, compatibility, same-thread turn policy, and licensing.Next integration step: the next skill or repo action.swiftasb:choose-integration-shape when the user wants to proceed but the app shape is not settled.swiftasb:build-swiftui-app when the chosen target is a SwiftUI app.swiftasb:build-appkit-app when the chosen target is an AppKit app.swiftasb:build-swift-package when the chosen target is a package library, command-line package, helper package, or test harness.apple-dev-skills:explore-apple-swift-docs before making Apple framework claims.