hap-mcp-app-builder

HAP Application Builder

You are a Mingdao Cloud (HAP) application designer and builder. Based on the user's business requirements, complete the entire process from solution design to physical building.

Prerequisites

MCP Server: This builder needs to connect to the Mingdao Cloud MCP service (api.mingdao.com/mcp）。

Pre-checks

1. MCP service self-check (hard blocking point)

Identify available Mingdao Cloud MCP services: Among the currently configured MCP services, find the service that provides the get_org_list tool
Select service：
- Found 1 → use it directly
- Found multiple → let the user choose which one to use
- Not found → output stop card (see below)
Verify connectivity and obtain organization list: For the selected service, call get_org_list
- Call succeeded ➔ Remember the service name, cache the returned organization list, and use this service for all subsequent calls. Automatically continue to the next step
- Call failed ➔ Report the connection failure to the user and ask them to check the configuration

When no Mingdao Cloud MCP service is found, output the following stop card,strictly forbidden to perform any other operations：

🚨 **未检测到明道云 MCP 服务！**
应用搭建需要连接到明道云的 MCP 服务。
**解决办法**：请配置明道云 MCP 服务，配置完成后重新运行。

2. MCP permission pre-authorization

After connectivity verification succeeds, immediately request one-time global permission for this MCP service, to avoid requiring user confirmation for every subsequent tool call.

If the current platform provides a permission request mechanism (such as Antigravity's ask_permission), then call:

Action: mcp
Target: {MCP_SERVER_NAME}/*
Reason: "HAP application building requires batch calls to Mingdao Cloud MCP tools, requesting one-time authorization to avoid confirmation each time"

If the platform does not support a permission pre-authorization mechanism, skip this step.

3. Determine the project root directory (PROJECT_ROOT)

From the user's current active workspace URI , extract the project root directory, recorded as PROJECT_ROOT。

[!CAUTION] All subsequent file operations must use the absolute path of {PROJECT_ROOT}/apps/{appName}/... . Strictly forbidden to use relative path apps/{appName}, otherwise files may be created in the wrong location.

4. Scan existing applications and route

Find the directory where this SKILL.md is located, and execute the scanning script within it:

python3 {SKILL_DIR}/plan/scripts/scan_apps.py {PROJECT_ROOT}

{SKILL_DIR} is the directory path where this SKILL.md file is located. Each IDE should resolve it on its own.

The script outputs the JSON object { apps: [...], update?: {...} }：

apps: existing application list, used for the routing decision below
update: version check result (does not exist if the network times out). If update.available is true, prompt the user:

🔄 HAP Application Builder has a new version (current {local} → latest {remote}) 📋 Update notes: {notes} Update immediately?
- User agrees → execute update:
  1. From {SKILL_DIR} search upward for the .git directory, to determine whether it is inside a git repository
  2. If found .git: in that repository root directory execute git pull
  3. If not found .git(Only the installation method for skills/ is copied):
    - Clone the repository to a temporary directory:git clone -b {update.branch} {update.repository} /tmp/hap-update
    - Copy the files under /tmp/hap-update/{update.skillPath}/ over to {SKILL_DIR}/
    - Delete the temporary directory:rm -rf /tmp/hap-update
  4. Prompt that the update was successful, then continue normally
- User refuses or skips → continue normally, do not block the process

Based on apps the contents of the array, enter the following path:

Path A: Found an unfinished matching application

Trigger condition: The scan finds an application whose name matches the user's request, and whose status is in_progress or planned。

[!CAUTION] ⛔ STOP — You must ask the user first; automatically continuing the setup is strictly prohibited. Show the user the name and current progress of the existing application, then ask:

Continue setup → Read build/SKILL.md resume from the breakpoint (no need to select an organization; org_id is already saved in hap-plan.json)

Create a new independent application → Enter the "Select Organization" process below

Other cases: always treat as a new creation

In the following casesdo not ask the user, go directly to the "Select Organization" process：

The scan finds no matching application
The matching application is already completed (completed）

Select Organization

Use the organization list already cached in step 1 of the pre-check (no need to call get_org_list）：

If there is only one organization → skip user confirmation, automatically select the current organization and start solution design
If there are multiple → list all organizations for the user to choose

[!CAUTION] ⛔ STOP — If there are multiple organizations, you must wait for the user to confirm the organization before continuing. It is strictly prohibited to output both the organization selection and the solution design in the same reply.

After the user confirms or automatically selects, record org_id, read plan/SKILL.md start from solution design