英语 |한국어 |简体中文

可重用的 Unity UI 工作流程规则，适用于 unity-mcp，作为 Codex 技能打包，并附带适用于其他大型语言模型平台的适配器。

从模型、截图、结构导出或目标分辨率创建中立的层到布局树，然后结合所选UI堆栈的布局、重用、缩放和验证机制实现。在叶子细节之前建立顶层区域所有权，重复使用结构，除非运行时需要拆分，否则保持单张图片资源完整。

当前版本：v0.7.0 ·更新日志

从这里开始

1. 打开unity-mcp-ui-layout/SKILL.md以显示规范的工作流程。
2. 在实现之前，先选择UI栈：UGUI 或 UI Toolkit。
3. 选择切换模式：修复现有屏幕或重建新屏幕。
4. 对于新的屏幕或重新设计，通过顺序问题解决开放设计和结构选择，然后就中立层到布局树达成一致。延续之前的答案。
5. 使用模型，检查并重复使用合适的项目图像。对于缺失的角色，询问生成情况，并仅在具备图像生成技能和可用执行路径的情况下生成。

Unity MCP UI Layout

English | 한국어 | 简体中文

Reusable Unity UI workflow rules for unity-mcp, packaged as a Codex skill with adapters for other LLM platforms.

Create a neutral layer-to-layout tree from a mockup, screenshot, structured export, or target resolution, then implement it with the selected UI stack’s layout, reuse, scaling, and verification mechanisms. Establish top-level region ownership before leaf details, reuse repeated structures, and keep single-image resources intact unless runtime behavior requires a split.

Current release: v0.7.0 · Changelog

Start Here

1. Open unity-mcp-ui-layout/SKILL.md for the canonical workflow.
2. Choose the UI stack first, before realization: UGUI or UI Toolkit.
3. Choose the change mode: repair an existing screen or build a new one.
4. For a new screen or redesign, resolve open design and structure choices through sequential questions, then agree on the neutral layer-to-layout tree. Carry forward prior answers.
5. With a mockup, inspect and reuse suitable project images. For missing roles, ask about generation and generate only with an available image-generation skill and usable execution path. Without that skill, skip both even if a standalone image tool exists. Honor explicit layout-only requests.
6. For Stitch HTML/CSS, Figma node-tree exports, DESIGN.md, or design tokens, identify hierarchy sources and style sources before editing.
7. Choose a task from examples/README.md, follow the agent runbook, or consult the reference index for a specific rule or failure mode.

For a small first exercise, use the first layout pass example. Natural requests such as “build this Unity UI from the attached UI mockup” or “create Unity UI prefabs from this design screenshot” should activate the skill without naming it explicitly.

The workflow favors stable structure, scoped changes, and explicit verification. Small widget adjustments do not need every planning step.

The execution contract standardizes routing, review authority, coordinates, and completion verdicts. The installable skill includes its plan template and Ruby validator; the repository-level template is a synchronized compatibility copy. This makes decisions and plan checks repeatable, without promising identical pixels across models or Unity versions.

Planning and Image Resources