feat(automation): rename to arrange-selection and add distribution#353
feat(automation): rename to arrange-selection and add distribution#353andypalmi wants to merge 0 commit into
Conversation
| * |OPEN_PALETTE_MANAGER | ||
| * |MANAGE_GROUPS | ||
| * |ALIGN_SELECTION} ExpertAutomationsActionsEnum | ||
| * |ARRANGE_SELECTION} ExpertAutomationsActionsEnum |
There was a problem hiding this comment.
ARRANGE_SELECTION infers it will operate on the selection however the schema expects the array of ids - this is unclear and confusing (to humans and AI). A better name might be simply arrange_nodes coupled with a parameter UseCurrentSelection? or the omittance of ids means work on the selection?
Do we want to split MCP tools into arrange_selection and arrange_nodes ?
Consider the conversation:
→ Select all the debug nodes
← Selected 3 debug nodes
→ Align them left and space vertically
← align ids 1,2,3 left
← vertically space ids 1,2,3
The AI will need to maintain the array of nodes to operate on & send them every time.
Consider the conversation:
→ user selects things to modify
→ Align the selection left and space vertically
← gets selected ids 1,2,3
← align ids 1,2,3 left
← vertically space ids 1,2,3
The AI still needs to maintain the array of nodes to operate on & send them every time.
By supporting arrange_selection this changes
Consider the conversation:
→ user selects things to modify
→ Align the selection left and space vertically
← align selection left
← vertically space selection
The AI simply issues the automation to perform the operations without maintaing a list of IDs or acidentally selecting wrong things
2ea8741 to
7dcf1d8
Compare
Summary
automation/align-selectionaction toautomation/arrange-selectionto support both alignment and distributionhorizontallyandverticallydistribution directions that invokecore:distribute-selection-horizontally/verticallyThis renames the action introduced in #347 (not yet released).
Test plan
Closes #352