// Explains DOT Studio navigation, UI vocabulary, Asset Library behavior, Stage vs thread terminology, and visible control names. Use for product-help questions. For direct UI mutation payloads, load studio-assistant-ui-operations-guide.
| name | studio-assistant-studio-guide |
| description | Explains DOT Studio navigation, UI vocabulary, Asset Library behavior, Stage vs thread terminology, and visible control names. Use for product-help questions. For direct UI mutation payloads, load studio-assistant-ui-operations-guide. |
| compatibility | Designed for the DOT Studio built-in assistant projection. |
Use this skill for navigation, feature-discovery, and product-usage questions.
Stage, working directory, draft, installed asset, session, and thread.studio-assistant-ui-operations-guide.Tal: always-on instruction/persona layer for a Performer.Dance: optional reusable skill bundle.Performer: an agent on the canvas built from Tal, Dance, model, and MCP.Act: a workflow that connects performers as participants.Workspace: current project folder plus saved Studio state.Working directory: the actual filesystem folder.Stage: the product surface containing current workspace objects; do not use it as a synonym for working directory.Draft: local authoring state for Tal or Dance.Installed asset: locally available Tal, Dance, Performer, or Act.Session: one performer chat history.Act thread: one runtime execution/history of an Act.Assistant.Settings.Asset Library.Asset Library -> Local -> Installed Assets.Asset Library -> Local -> Runtime.Asset Library -> Registry.Asset Library -> Registry -> Import as Dance.Export.Installed Assets and Runtime.Performer, Tal, Dance, and Act.All, Global, Workspace, and Draft.Models lists available model providers.MCPs manages Studio MCP server definitions.Ready to run and Create Thread.Board for shared notes and participant tabs for participant chat.Edit Act to change participants, relations, description, rules, or readiness issues.Save Draft and Close.Save Draft, Open, Export, and Close.Save Local and Publish are asset lifecycle actions outside Assistant CRUD.Read references/navigation.md only when exact UI behavior or labels matter.
Explains the current DOT Studio Act contract: participants, relations, subscriptions, actRules, safety, and publish-safe field boundaries. Use for Act contract, relation, subscription, and runtime guardrail questions. For role split/topology decisions, load studio-assistant-workflow-guide.
Lists the exact Studio Assistant apply_studio_actions mutation surface, field rules, ref ordering, and payload self-checks. Use before emitting or validating any Studio mutation tool call.
Helps design or revise Studio Performers with strong role focus, Tal/Dance/model choices, and Act participant readiness. Use for Performer creation, Performer updates, role design, and participant-quality decisions. For exact payload fields, load studio-assistant-action-surface-guide.
Tells the Studio Assistant how to open, reveal, inspect, hide, show, move, resize, and panel-toggle Studio UI surfaces through apply_studio_actions. Use for direct Studio UI manipulation requests.
Helps design performer teams, role splits, handoff patterns, and connected Act topology in DOT Studio. Use when the user wants a team, workflow, pipeline, role decomposition, or Act structure recommendation.
Helps the Studio Assistant design strong Tal content for agents. Use when deciding what belongs in Tal, how concise it should be, how to express persona and mental model, or how to propose a role-appropriate Tal before creating a Performer.