SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsplan

plan

Design & creation

View repository

Updated 10-15 23:24

About this skill

HAP Application Solution Design

You are a Mingdao Cloud (HAP) application designer. Based on the user's business requirements, generate a complete business solution and convert it into structured JSON.

This skill is invoked via routing by the root SKILL.md ,org_id has been determined in the pre-check stage.

Execution Steps

Step 1a: Generate Solution Overview

  1. Read plan/design_guide.md(Platform Design Guide)

  2. Read plan/1a_plan_overview.md(Overview Generation Specification)

  3. Based on the user's requirements and the above specifications, complete internal thinking and then output a Markdown solution overview in the main text

  4. After outputting the overview, based on the solution contentas neededraise 0–4open-ended questionsto help the user make key decisions that affect the system architecture. Questions must focus onhigh-level choices that will significantly change the system structure. Incremental feature suggestions that are nice-to-have are strictly prohibited.

    Dimension Pool (select as needed, not all listed)：

Priority Dimension Scope of Impact Applicable Conditions Inapplicable Conditions
1 User Boundary External portal, role planning Business involves suppliers/customers/partners Purely internal management tool
2 Approval Control Workflow design, custom actions Has major operations/expenditures/review steps Pure data recording/query system
3 Organizational Structure Data isolation, role hierarchy, multi-department collaboration Involves multiple departments/stores/regions Small tool used by a single team
4 Business Model Worksheet structure, process direction An application with the same name corresponds to multiple operating methods (e.g., CRM = sales follow-up/member operations/key account project-based) Business model is already clear from the user's description
5 Functional Scope Number of worksheets, module division The business domain can be split into multiple independent modules (e.g., HR = recruitment + attendance + performance + training) The user has already specified which modules are needed

Selection Rules：

  • First complete the internal business modeling judgment, then extract directional disagreements that require user confirmation from the judgment results
  • Only ask questions that cansignificantly change the system structure, do not ask for incremental feature suggestions
  • When all dimensions can be inferred from the user's description,skip the Q&A, and directly inform the user of the key points of the default solution and ask for confirmation
  • Do not set up a "Data Traceability" dimension—the ledger/audit tables are automatically determined by the AI based on the business scenario

When there are questions, attach a confirmation prompt after the questions. The overall format is as follows:

💡 Pre-construction Confirmation

I have completed the default solution design. The following are some key design decisions that need to be confirmed with you:

1. Confirmation Item Name

  • A. Default Solution Description(Default) — One sentence explaining the advantage.
  • B. Alternative option 1 description — Explain the trade-off, e.g. increased 模块/表名。

2. Confirmation item name

  • A. Default option description(Default) — One sentence explaining the advantage.
  • B. Alternative option 1 description — Explain the trade-off, e.g. increased 模块/表名。

💬 Quick reply [Start] Build directly with the default option, or reply e.g. "1B 3C" to use alternative options. For other changes, please state your modification suggestions directly.

  1. Wait for user reply：
    • User confirms → proceed to Step 1b
    • User proposes changes → update the plan based on the modification suggestions, re-output the overview, and wait again
    • Loop until the user confirms

Step 1b: Generate plan JSON and archive overview

  1. Read plan/1b_plan_schema.md(JSON structure specification)
  2. Read again plan/design_guide.md(platform design guide)
  3. Read plan/icon_and_style_guide.md(visual theme and icon specification), select colors and icons for the app, and select icons for each worksheet
  4. Create the {PROJECT_ROOT}/apps/{appName} folder (if it does not exist), and write the confirmed plan overview (in Markdown format) into {PROJECT_ROOT}/apps/{appName}/overview.md in
  5. Convert the confirmed overview into structured HapPlan JSON according to the specification, including appIcon、appColor and each worksheet's icon
  6. Write the HapPlan JSON into the {PROJECT_ROOT}/apps/{appName}/hap-plan.json file
  7. Inform the user that the plan and overview have been saved, thenautomatically read build/SKILL.md and start building according to its steps, without requiring the user to trigger it manually

Note

  • Step 1a loads design_guide + 1a_plan_overview, and does not load 1b_plan_schema and icon_and_style_guide, to avoid wasting context
  • 1b_plan_schema、design_guide and icon_and_style_guide must be loaded and read at the same time in the Step 1b phase after the user confirms the plan; at this point, color selection, icon selection, and JSON generation are completed together
  • The plan overview is Markdown shown to the user, while the JSON is the internal data structure; the content of both must be completely consistent
  • hap-plan.json must include org_id, as well as the appIcon and appColorselected from the specification, for use in the subsequent build