idumych/beos-app-platforms

A Claude Code skill (also usable from opencode) for building, packaging, testing and releasing BeOS-style apps, that is, C++ written against the Be/Haiku API, on two platforms from one source tree:
| Platform | Package | Tested in |
| Haiku R1/beta6 | .hpkg, x8664 only: Haiku has no arm64 release or arm64 package repository yet | Haiku R1/beta6 (hrev59866) in a VirtualBox VM, which also builds the package |
| Linux, through Hokku (a fork of Cosmoe) | AppImage, x8664 and aarch64 (X11 and Wayland), built natively per architecture in GitHub CI | x8664: Xvfb + Openbox, full test; both architectures: started under X11 and Wayland (headless sway) in CI, aarch64 on GitHub's arm64 runners |
Where upstream bugs are reported. Packages are built and tested on Haiku R1/beta6, but platform bugs found along the way are submitted to Renku OS, a Haiku fork that explicitly accepts AI-assisted contributions. They are never sent to the Haiku project, because Haiku doesn't welcome AI-generated contributions. Renku still names its system package haiku (r1~beta6), so the same .hpkg installs there too. Cosmoe bugs are fixed in Hokku, since Cosmoe doesn't accept AI contributions either.
It records what was learned shipping Folio and Sheath:
Porting: the Makefile platform branches, plus the traps on each system (node monitoring, attributes, Trash, entryref names, font faces picked by style name, tooltips that never hide on Cosmoe, headers missing from R1/beta6).
Packaging for amd64 and arm64: the .hpkg in a Haiku R1/beta6 VM (or on a GitHub runner with cross-platform-actions), x8664 until Haiku has an arm64 target (the skill says how to check at each release); and a relocatable AppImage for x8664 and aarch64 that bundles both Cosmoe backends and is started under X11 and Wayland on each architecture in CI.
Testing: driving VMs headlessly, with keyboard scancodes, mouse input through the VirtualBox SDK (hovering before menu clicks), screenshots read with OCR, and one-time SSH into Haiku-family guests; Cosmoe builds under Xvfb on a display of your choice; and X11 and Wayland smoke tests in CI on both architectures (headless sway with grim screenshots; headless Weston has no seat, so Cosmoe apps quit there), which fail on a blank screen or a window that never appears.
Releases: a complete pipeline: onboarding templates for any app (haiku-app.env, Makefile, packaging, CI), a build of both from one commit, a scripted test of each package on its platform with evidence files, and a release gate that checks the raw evidence and stops for a human before anything is published. Written so that an agent, including a local model, can release an app unsupervised.
Hokku: Linux builds use Hokku, a Cosmoe fork that takes AI-generated fixes and aims to be a library freestanding Renku/Haiku app ports can build against. Cosmoe bugs get fixed there, not worked around in each app; Cosmoe itself doesn't accept AI contributions.
Upstream reports: Renku OS for platform bugs, Hokku for Cosmoe bugs, never Haiku or Cosmoe themselves; how to write them.
## Install
Clone it into your personal skills folder, and Claude Code picks it up in every project: