/studio-assistant-ui-operations-guide

name: studio-assistant-ui-operations-guide
description: "Tells the APM Studio Assistant how to open, reveal, inspect, hide, show, move, resize, and panel-toggle UI surfaces through apply_studio_actions. Use for direct UI manipulation requests."
compatibility: Designed for the APM Studio built-in assistant projection.

APM Studio UI Operations Guide

Use this skill when the user asks APM Assistant to manipulate the APM Studio interface.

When To Use

• Open, show, reveal, select, focus, or inspect an Agent, Team, or draft.
• Open or close Packages, Workspace Tracking, or Terminal.
• Hide or show an Agent or Team.
• Move, resize, align, or arrange Agent/Team canvas windows.

Action Choices

• `showAgent`: select/reveal an Agent, or open its editor with `surface: "editor"`.
• `showTeam`: select/reveal a Team, or open its editor with `surface: "editor"`.
• `showDraft`: open an Instruction or Skill draft editor.
• `setStudioPanel`: toggle `packages`, `workspaceTracking`, or `terminal`.
• `setStudioNodeVisibility`: set visible/hidden state for an Agent or Team.
• `setStudioNodeFrame`: set absolute `position` and/or `size` for an Agent or Team.

Targeting Rules

• Prefer exact ids from the snapshot.
• Use exact names only when ids are not needed or the target is unambiguous.
• Use same-call refs only for objects created earlier in the same tool call.
• Ask a short clarifying question if multiple visible objects match the user's target.

Surface Rules

• For `showAgent` and `showTeam`, omit `surface` or use `surface: "canvas"` for simple show/reveal requests.
• Use `surface: "editor"` only when the user asks to edit, configure, inspect settings, or fix readiness.
• For `showTeam` editor requests:
• `editorMode: "team"` for general Team editing
• `editorMode: "participant"` with `participantKey`
• `editorMode: "relation"` with `relationId`

Geometry Rules

• Use `setStudioNodeFrame` only when the snapshot provides current position and size or the user gives explicit coordinates/size.
• Use absolute canvas coordinates.
• Do not invent geometry for subjective layout requests; ask if the desired arrangement is unclear.
• UI-only changes are hot Studio state. Do not describe them as packaged, saved, installed, or runtime-affecting.

Examples

{"version":1,"actions":[{"type":"showAgent","agentName":"Writer","surface":"editor"}]}

{"version":1,"actions":[{"type":"setStudioPanel","panel":"packages","open":true}]}

{"version":1,"actions":[{"type":"setStudioNodeFrame","nodeType":"team","teamName":"Review Flow","position":{"x":320,"y":240},"size":{"width":520,"height":460}}]}