prime-dev-cli 2.0.1 → 2.0.3

package/skills/prime-workspace/SKILL.md

@@ -0,0 +1,347 @@
+---
+name: prime-workspace
+description: Use this skill to handle prime-dev-cli workspace operations through natural language, such as starting an env like icrc, checking one app's status, creating or editing mock APIs and Mock.js responses, managing mock scenes, switching proxy targets, and updating microapp bindings.
+---
+
+# prime-workspace
+
+This is the platform-neutral execution spec for `prime-dev-cli`.
+
+The goal is not to expose raw API endpoints to the user. The goal is to let the user speak naturally, for example:
+- 帮我启动 icrc
+- 停掉 ilink-icrc
+- 看看 iqc 在不在跑
+- 把 icrc 切到 sitnew
+- 给 isource 挂上 ilink-isource
+- 把 /api/user/info 切到异常场景
+
+## Preconditions
+
+### Default local server
+- Base URL: `http://localhost:52741`
+
+### Reachability rule
+Before using any action, first verify that the local server is reachable.
+
+If the local server is not reachable:
+- do not fabricate results
+- for packaged users, suggest `prime ui`
+- for repository developers, `pnpm run dev:server` is also acceptable
+
+### Configuration source
+Treat the runtime workspace configuration as the source of truth:
+- current workspace/project/env structure comes from `~/.prime-projects.json`
+- do not rely on stale example config fields if runtime data differs
+
+## Intent-first action map
+
+Do not think in terms of endpoints first. Think in terms of user intent first.
+
+### 1. Workspace status
+Typical requests:
+- 看下工作空间状态
+- 哪些项目还没准备好
+- 项目空间现在什么情况
+
+Use:
+- `GET /api/check-workspace`
+- `GET /api/process/status`
+
+Return:
+- whether workspace exists
+- project counts
+- existing / pending / incomplete projects
+- currently running envs
+
+### 2. Project drill-down
+Typical requests:
+- 看下 esource-fe
+- 看下 esource-fe 分支
+- 打开 esource-fe
+- 给我建个 ilink-fe 和 iqc-fe 的工作区
+
+Use as needed:
+- `GET /api/project-config?project=<projectName>`
+- `GET /api/current-branch?project=<projectName>`
+- `POST /api/open-project`
+- `POST /api/workspace/create`
+
+### 3. Start / stop / status / logs
+Typical requests:
+- 帮我启动 icrc
+- 停掉 ilink-icrc
+- 看看 iqc 在不在跑
+- 打开 isource 的日志
+
+Use:
+- `POST /api/process/start`
+- `DELETE /api/process/start?projectName=<projectName>&envName=<envName>`
+- `GET /api/process/status?projectName=<projectName>&envName=<envName>`
+- `GET /api/process/logs?projectName=<projectName>&envName=<envName>&tail=100`
+
+When starting one env:
+- use that env's configured `startCommand`
+- report the access URL from that env's configured `host`
+- prefer output like:
+  - 已启动 icrc
+  - 访问地址：`http://localhost:8806`
+
+### 4. Mock project-level control
+Typical requests:
+- 打开 iqc-fe 的 mock 功能
+- 关闭 iqc-fe 的 mock 功能
+- 打开 iqc-fe 的 mock 拦截
+- 关闭 iqc-fe 的 mock 拦截
+
+Use:
+- `GET /api/project-config?project=<projectName>`
+- `PUT /api/project-config`
+
+Project-level mock fields:
+- `mockOpen`
+- `mockingIntercept`
+
+### 5. Mock scene management
+Typical requests:
+- 看 mock 列表
+- 把 /api/user/info 切到异常场景
+- 新建一个超时场景
+- 打开这个场景
+- 关闭这个场景
+- 预览 GET /api/user/info 现在返回什么
+
+Use:
+- `GET /api/mock-file?project=<projectName>`
+- `POST /api/mock-file`
+- `GET /api/mock-file-content?project=<projectName>&apiName=<apiName>&method=<method>&siteName=<siteName>`
+- `PUT /api/mock-file-content`
+- `PUT /api/mock-setting`
+- `PUT /api/mock-open-status`
+- `GET /api/get-mock-data?project=<projectName>&url=<url>&method=<method>`
+
+### 6. Mock deletion and bulk toggles
+Typical requests:
+- 删除这个 mock 场景
+- 删除整个 /api/user mock 接口
+- 一键开启所有 mock
+- 一键关闭所有 mock
+
+Use:
+- `DELETE /api/mock-file?project=<projectName>&apiName=<apiName>&method=<method>&siteName=<siteName>`
+- `DELETE /api/delete-mock-api?project=<projectName>&apiName=<apiName>`
+- `POST /api/open-all-mock`
+- `POST /api/cleanup-mock`
+
+### 7. Proxy viewing and editing
+Typical requests:
+- 看 icrc 现在走哪个代理
+- 把 icrc 切到 sitnew
+- 把 ilink 的 /icrc-api 切到 uat
+- 给 ispar 新增 /idea-api
+
+Use:
+- `GET /api/project-config?project=<projectName>`
+- `PUT /api/project-config`
+
+### 8. MicroApp bindings
+Typical requests:
+- 看 icrc 挂了哪些微应用
+- 给 isource 挂上 ilink-isource
+- 清空 iua 的微应用代理
+
+Use:
+- `GET /api/all-projects-envs`
+- `PUT /api/microapp-proxy-config`
+
+## Natural-language routing rules
+
+### Project vs env interpretation
+Normalize both forms:
+- `project` / `projectName`
+- `env` / `envName`
+
+Interpretation priority:
+- start / stop / logs / proxy / microapp -> prefer **env**
+- open project / branch / workspace creation -> prefer **project**
+
+Examples:
+- `帮我启动 icrc` -> treat `icrc` as an env
+- `打开 ilink-fe` -> treat `ilink-fe` as a project
+- `打开 ilink` -> ambiguous, ask whether the user means the project or the env
+
+### Access URL rule
+When an env is running or has just been started:
+- derive the user-facing URL from that env's configured `host`
+- if process APIs also return a port, still prefer `host` as the primary display URL
+
+### Project workspace vs editor workspace
+These are different intents:
+- “创建项目空间” -> initialize/repair local repos
+- “创建工作区” -> create/open a multi-project editor workspace
+
+Do not collapse them into one action.
+
+## Confirmation matrix
+
+Always confirm before:
+- deleting one mock scene
+- deleting a whole mock API
+- opening all mock scenes
+- closing all mock scenes
+- changing microapp selections
+- changing proxies when multiple prefixes may match
+
+Also explain why confirmation is needed.
+
+## Required input rules
+
+### Starting one env
+To start an env reliably, determine:
+- `projectName`
+- `envName`
+- `startCommand` from runtime config
+- `host` from runtime config
+
+If the env name maps cleanly to one configured env, proceed.
+If multiple matches exist, ask a follow-up question.
+
+### Proxy edits
+For proxy edits, determine:
+- `projectName`
+- `envName`
+- target prefix
+- target proxy name or custom URL
+- optional rewrite settings
+
+If the env has multiple prefixes and the user did not specify which one, ask.
+
+### Mock scene operations
+For mock scene operations, determine:
+- `projectName`
+- `apiName`
+- `method`
+- `siteName`
+
+Use “scene” as the user-facing term.
+
+### MicroApp edits
+For microapp operations, determine:
+- `projectName`
+- `envName`
+- `selectedItems`
+
+Important:
+- `selectedItems` are env-name strings
+- they are not full project/env identifiers
+- explain this if the operation may affect expectations
+
+## Request examples
+
+### Workspace status
+```http
+GET /api/check-workspace
+```
+
+### Project config
+```http
+GET /api/project-config?project=esource-fe
+```
+
+### One env status
+```http
+GET /api/process/status?projectName=esource-fe&envName=icrc
+```
+
+### Start one env
+```http
+POST /api/process/start
+Content-Type: application/json
+
+{
+  "projectName": "esource-fe",
+  "envName": "icrc",
+  "startCommand": "npm run serve:c"
+}
+```
+
+### Switch current mock scene
+```http
+PUT /api/mock-setting
+Content-Type: application/json
+
+{
+  "projectName": "iqc-fe",
+  "apiName": "api_user_info",
+  "method": "get",
+  "currentSite": "异常场景"
+}
+```
+
+### Update env proxy config
+```http
+PUT /api/project-config
+Content-Type: application/json
+
+{
+  "projectName": "esource-fe",
+  "envName": "icrc",
+  "apiProxies": []
+}
+```
+
+### Update microapp bindings
+```http
+PUT /api/microapp-proxy-config
+Content-Type: application/json
+
+{
+  "projectName": "isource-fe",
+  "envName": "isource",
+  "selectedItems": ["ilink-isource"]
+}
+```
+
+## Friendly usage examples
+
+### Workspace / project / branch
+- 看下工作空间状态
+- 打开 esource-fe
+- 给我建个 ilink-fe 和 iqc-fe 的工作区
+- 看下 esource-fe 分支
+
+### Start / stop / status / logs
+- 帮我启动 icrc
+- 停掉 ilink-icrc
+- 看看 iqc 在不在跑
+- 打开 isource 的日志
+
+### Proxy
+- 看 icrc 现在走哪个代理
+- 把 icrc 切到 sitnew
+- 把 ilink 的 /icrc-api 切到 uat
+- 给 ispar 新增 /idea-api
+
+### Mock
+- 打开 iqc-fe 的 mock 功能
+- 打开 iqc-fe 的 mock 拦截
+- 看 mock 列表
+- 把 /api/user/info 切到异常场景
+- 新建一个超时场景
+- 删除这个 mock 场景
+- 一键关闭所有 mock
+
+### MicroApp
+- 看 icrc 挂了哪些微应用
+- 给 isource 挂上 ilink-isource
+- 清空 iua 的微应用代理
+
+## Failure handling
+
+If an API fails:
+- name the exact action that failed
+- report whether the likely cause is missing project, missing env, missing local workspace, bad input, or server unavailability
+- do not invent missing values
+
+If a request is ambiguous:
+- ask one narrow follow-up question
+- prefer clarifying project/env/prefix/scene ambiguity before doing anything destructive