hub-pro-master

Indexes skills, checklists, and health checks for SourceA Hub app development workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on SourceA Hub apps (Worker Hub, Mac Health, Form, Chat Unify, n8n, Machine Hub) without a shared index leads to missed pre-flight checks, repeated mistakes, and lost change history. This Skill provides the master entry point that routes you to the right sub-skill, enforces mandatory pre-flight and post-ship steps, and preserves field lessons. ## Core Features & Use Cases - Hub app map: Lists every Hub app with its port, URL, and surface_id so you always target the correct local service. - Skill batch routing: Points to nine specialized skills (UI upgrade, e2e, Mac security, standalone apps, form, cloud API, change log) so you load only what you need. - Mandatory pre-flight and post-ship scripts: Runs path classification, first-check, experience-log reads, health curls, and change-log appends via Python scripts. - Use Case: Before editing the Official Form UI, read this index, run the UI path classifier and first-check scripts, review the last experience log entry for hub_form, ship the change, then append a change-log entry. ## Quick Start Ask the agent to read the hub-pro-master index first, then load the skill matching your Hub app task and run the mandatory pre-flight checks before making changes.

Frequently Asked Questions about hub-pro-master

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

FAQPage Schema
How do I start working on a SourceA Hub app safely?

Read the hub-pro-master index first, then load the sub-skill matching your task (UI upgrade, e2e, Mac security, etc.). Run the mandatory pre-flight scripts: path classifier, first-check, experience-log read, and a health curl on the app's port.

What ports do the Hub apps run on locally?

Worker Hub, Machine Hub, Official Form, and Portfolio Mail run on port 13020 under different paths. Mac Health Guard uses 13024, Chat Unify uses 13023, and the n8n Integration uses 13026, all on 127.0.0.1.

Why does the Hub UI show OFFLINE when the API is live?

Server health and JavaScript errors are separate concerns; the API can be live while the UI reports OFFLINE due to JS failures. Always check the /health endpoint directly and null-guard legacy DOM ids removed by the founder_glance UI.

How do I record changes after shipping a Hub app fix?

Run hub_pro_skills_v1.py with --append, passing app id, agent id, summary, obstacles, and fixes. If the change touched UI, also append an entry with ui_upgrade_ledger_v1.py for the affected surface_id.

Why does form submission fail on macOS threaded servers?

Starting a background subprocess before sending the HTTP response causes macOS threaded servers to drop the connection. Always return the HTTP response first, then launch any background work.