hub-pro-standalone-apps

Build and maintain WKWebView-based macOS standalone apps wrapping embedded Python servers.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-standalone-apps-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hub-pro-standalone-apps
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/hub-pro-standalone-apps
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-standalone-apps-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing four standalone macOS desktop apps (Worker Hub, Mac Health Guard, Chat Unify, n8n Integration) that wrap embedded Python servers in Swift WKWebView shells requires consistent build, sync, and launch procedures that are easy to get wrong. ## Core Features & Use Cases - Build orchestration: Documents the per-app build scripts that produce Desktop .app bundles from Swift shells and Python servers on fixed ports (13020, 13023, 13024, 13026). - SSOT vs bundle sync: Clarifies which source directories serve live in dev versus which require copying or rebuilding for the Desktop .app to pick up changes. - Single-instance launch fix: Applies SinaStandaloneShell.prepareApp so a second double-click activates the existing window instead of spawning crash loops. - Use Case: After editing the Mac Health Guard server, run the build script, verify cold-start health within 15 seconds, confirm codesign passes, and ditto the app to Desktop and Applications before shipping. ## Quick Start Ask the assistant to rebuild the Worker Hub standalone app and verify it cold-starts with a healthy server on port 13020.

Frequently Asked Questions about hub-pro-standalone-apps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a standalone macOS app that wraps a Python server?

Use the per-app build scripts such as build-worker-hub-standalone-app-v1.sh, which compile the Swift WKWebView shell and bundle the Python server into a Desktop .app. The shell starts the server if the health check fails, then loads http://127.0.0.1:<port>/.

Why does my WKWebView app open multiple windows or crash on launch?

Repeated double-clicks can spawn duplicate instances and crash loops. Call SinaStandaloneShell.prepareApp with the app's bundle ID so a second launch activates the existing window instead of starting a new process.

How do I keep the Desktop .app in sync after editing server source files?

Edits to the SSOT directories serve live only in dev mode; the Desktop .app uses its own bundle copy. Always copy the updated files or rerun the build script after standalone edits before shipping.

Where are the launch and server logs for these macOS apps?

Worker Hub logs to ~/.sina/worker-hub-app-launch.log, Mac Health to ~/.sina/mac-health-app-launch.log, and the Mac Health server to ~/.sina/mac-health-guard-server.log. Check these first when a window shows a failed health state.

What should I verify before shipping a rebuilt standalone app?

Confirm cold-start health passes within 15 seconds, the window loads the UI rather than an error, codesign verification passes, and the app is ditto'd to both Desktop and Applications. Then append an entry to the experience log.