UI Master is a task preset package for teams that want UI requests to start from a clearer structure than a single free-text brief.
Why teams install it
Command-guided task framing
Users select an explicit UI command before dispatch, which gives the task preset a more stable starting point for routing, prompt construction, and review.
Scene-aware execution
The task preset can bind to a scene provider so hero selection and execution framing stay consistent with the UI Master operating model.
Controlled repository scope
Repository access remains explicit. That makes the task preset safer to expose in shared workspaces where not every UI task should see every repository.
Best fit
- Best for: intentional UI work, design refinements, interaction cleanup, and implementation-focused interface tasks.
- Not for: open-ended research dumps, backend-only changes, or tasks that need unrestricted project execution.
FAQ
Can this task preset edit every repository in a project by default?
No. Repository access is declared as task preset input and should stay visible to the user before dispatch.
Why keep a command catalog instead of only a free-text brief?
The catalog helps normalize user intent and gives the task preset a more stable structure for routing and prompt construction.
UI Master 适合那些不希望 UI 请求只从一段自由描述开始,而是希望先把任务结构收紧、再进入执行阶段的团队。
为什么团队会安装它
命令驱动的任务成型
用户在派发前先选定明确的 UI 意图,让 task preset 从清晰方向启动,而不是只接收模糊自由文本。
场景感知执行
task preset 可以绑定 scene provider,让 hero 选择和执行 framing 保持一致。
可控的仓库范围
仓库访问范围始终显式声明,更适合暴露在共享工作区里。
适用场景
- 适合:需要明确意图的 UI 工作、设计润色、交互梳理,以及实现导向的界面任务。
- 不适合:开放式调研、纯后端改动,或需要无约束项目执行权限的任务。
常见问题
这个 task preset 默认能修改项目下所有仓库吗?
不能。仓库访问必须作为 task preset 输入显式声明,并在派发前对用户可见。
为什么还要保留命令目录,而不是只靠自由描述?
命令目录可以把用户意图规范化,让路由和 prompt 构造都建立在更稳定的结构上。