Reference specimen

SkipUI

Mobile cross-compile compatibility reference.

Many worlds. One workstream.

renderer Native compatibility maturity Compare only maintainer External upstream campus Campus maintainer candidate mode Native Swift reference npm No npm manifest observed setup Syntax specimen only import SkipUI

Shipping question

Can SwiftUI syntax aimed at Android/iOS portability teach the web lane anything about source constraints?

This specimen is generated by the wrkstrm homepage model. It does not prove the upstream framework is installed in the campus until a setup receipt lands here.

npm evidence: 2026-05-18 recursive GitHub tarball scan found Package.swift and no npm manifest or lockfile paths.

Package: https://github.com/skiptools/skip-ui

Homepage arc

candidate

Generate possible worlds

Agents and digikomas produce apps, documents, diagrams, releases, and decisions.

parallel

Compare timelines

Shipped, stalled, counterfactual, and next-best branches stay visible together.

proved

Select the executable path

Schemas, Swift packages, DocC, receipts, commits, and releases back the branch.

Adapter sketch

import SwiftUI
struct WrkstrmHome: View {
  var body: some View {
    VStack {
      Text("wrkstrm")
      Text("Many worlds. One workstream.")
    }
  }
}