Menu
Work through persisted, element-anchored review comments on shared Design prototypes and close the loop with verified edits.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to look up version-matched Agent Native framework docs and source in node_modules. Use before coding against @agent-native/core APIs or advanced features.
Creating, editing, and managing extensions — sandboxed Alpine.js mini-apps that run inside iframes. Use when a user asks for a dashboard, widget, calculator, or any interactive mini-app that calls external APIs. Distinct from LLM "tools" (function calls) — see note below.
Agent observability, evals, feedback, and experiments. Use when adding observability dashboards, configuring trace capture, setting up evals, creating A/B experiments, or collecting user feedback on agent responses.
Server-side analytics tracking with pluggable providers. Use when adding analytics events, registering custom tracking providers, or configuring built-in providers (PostHog, Mixpanel, Amplitude, Webhook).
Live calendar-backed meetings in Clips — upcoming Google Calendar events, desktop join/record reminders, live transcripts with mic + system-audio capture, AI summary / bullets / per-attendee action items, and the bidirectional recording↔meeting link. Use when listing meetings, opening a meeting detail, finalizing notes, connecting a calendar, or working with attendee-tagged transcript segments.
Declare, evaluate, manage, and remove framework feature flags. Use when shipping a capability gradually, targeting users or organizations, or replacing a compile-time rollout switch with a production-safe runtime flag.
| 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.