菜单
Work through persisted, element-anchored review comments on shared Design prototypes and close the loop with verified edits.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/BuilderIO/agent-native --skill design-review-feedback命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | design-review-feedback |
| description | Work through persisted, element-anchored review comments on shared Design prototypes and close the loop with verified edits. |
Use the shared review actions for design feedback:
view-screen first so the active design, screen, inspector tab, and
review queue are current.get-review-feedback for the open queue and work on one root thread at
a time. Keep the thread id, target screen id, anchor node id, and nearby
context together while editing.data-agent-native-node-id from the anchor. Use the stored percentage point
only as a visual fallback when the node cannot be resolved.get-design-snapshot, make the smallest
persisted edit with edit-design or the appropriate design action, then
verify the saved result with get-design-snapshot and a screenshot or audit
when the change is visual.resolve-review-thread only after the edit is
persisted and verified, and pass resolutionNote with a one-line description
of the persisted change. If the user needs to decide something, reply with
reply-review-comment and set resolutionTarget: "human"; do not silently
resolve it.consume-review-feedback for the applied
agent-targeted root comment so the queue does not repeatedly resurface the
same work.Reviewers can leave a human-only comment or choose Send to agent when
composing. Editors can selectively route an existing open thread with
send-review-thread-to-agent; that action only changes the selected thread.
When a thread is sent from the Design UI, the agent chat handoff includes its
thread id and instructs the agent not to apply other queued feedback.
Use create-review-comment for agent-authored follow-up notes when a durable
record is more useful than a chat-only explanation. Keep review comments
scoped to the design resource and the target screen; never copy large HTML,
screenshots, or provider payloads into a comment.