agentleFS
vchelaruvchelaru/Gum/.claude/skills/gum-tool-copy-paste/SKILL.md

gum-tool-copy-paste

Skill659 starsChanged 2 months agoMITView on GitHub

Gum copy/paste. Triggers: CopyPasteLogic, ICopyPasteLogic, OnCopy/OnPaste/OnCut, PasteInstanceSaves, CopiedData, clipboard behavior, multi-paste selection tracking.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the matched state has any VariableReferences row, the qualified list marker "<instance>.VariableReferences" is also added so paste drops …

    line 63
  2. Distinctive:

    All copy/paste is triggered through:

    line 93
  3. Very specific:

    Do not call CopyPasteLogic methods directly from outside these entry points.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Gum Copy/Paste Reference

In-Memory, Not System Clipboard

Gum's copy/paste does not use the system clipboard. Copied data lives in CopyPasteLogic.CopiedData (an in-memory instance). MonoGameGum/Clipboard/ClipboardImplementation.cs is a separate text-only clipboard used elsewhere in the app — not part of this system.

CopyType Dispatch

CopyType drives the entire operation:

  • InstanceOrElement — copies selected instances within an element, or a whole element if nothing is selected
  • State — copies the selected state within a state category

Copy, cut, and paste each accept a CopyType parameter and bail out early if it doesn't match what's stored.

TopOrRecursive

Paste offers two modes: Recursive (instances + all descendants) vs Top (only top-level instances). The UI exposes both as separate "Paste" and "Paste Top Level Instance(s)" menu items.

Cutting Instances vs. Elements

Cutting instances calls StoreCopiedObject() (same as copy) and then deletes the source instances right away via IDeleteLogic.RemoveInstance(), so cutting and never pasting still removes them.

Cutting a screen or component leaves it in place. The next paste on a folder moves it there (MoveCutElement), and a paste anywhere else leaves the cut pending.

Multi-Paste Targeting Is Shared With Ctrl+Shift-Click Adds

Where a repeat paste lands is owned by IAddDestinationTracker (Tools/Gum.Presentation/Logic/AddDestinationTracker.cs), not by CopyPasteLogic. It listens to SelectionChangedMessage; any selection change forgets the remembered destination and flags the selection as user-chosen, and Anchor(destination) is called after an add has selected what it created, so that selection change does not count. Paste uses it as:

  • HasSelectionChangedSinceAnchor true — attach to the current selection, then anchor that container
  • false with a Destination — attach to the remembered container (repeat-paste, or a paste after a Ctrl+Shift-click add into that container)
  • false with no Destination — keep the original parents (paste straight after copy)

OnCopy/OnCut call MarkSelectionUnchanged() (the destination is kept); ForceSelectionChanged() (drag-drop's cross-element move) calls MarkSelectionChanged(). Every other way of adding an instance goes through IAddInstanceLogic (Tools/Gum.Presentation/Logic/AddInstanceLogic.cs), which anchors the same tracker, so chip clicks, drags, the right-click menus, the Add Instance dialog and pastes keep adding siblings into one container until the user selects something else.

Paste Creates New Instances, Does Not Clone

PasteInstanceSaves() creates fresh InstanceSave objects and assigns properties from the copied states. It does not simply clone the stored instances. Name uniqueness is enforced via StringFunctions.MakeStringUnique(), and an oldNewNameDictionary is built to remap parent references throughout the copied hierarchy.

Expansion State Follows the Source Node

StoreCopiedInstances also snapshots which copied instances' tree nodes were expanded (via the head-provided IElementTreeRoots seam) into CopiedData.CopiedExpandedInstanceNames. PasteInstanceSaves re-expands the matching new instance's node after the tree refresh, so pasting an expanded parent leaves the new copy expanded instead of defaulting to collapsed. Direct PasteInstanceSaves callers outside CopyPasteLogic (drag-drop, HandleMoveToBase) pass no expansion set, so this only applies to copy/paste.

Base-Element Capture is Filtered, Not Wholesale

StoreCopiedInstances captures the source's own selected state into CopiedStates AND the default state of every base element in the source's BaseType chain into a separate CopiedBaseElementDefaultStates list. The base captures exist so the new instance keeps inherited effective values (e.g. Text="Click Me" from a base) even after renaming/relocation, where the regular inheritance walk would no longer reach them.

At paste time, base captures are filtered by CopiedNamesOwnedByReachableStates — the set of qualified item names owned by any reachable categorized state on the source instance. "Owned" covers three shapes:

  1. Local VariableReferences rows on the source state targeting this instance — their LHSes are scalar names owned.
  2. The matched categorized state of the instance's BaseType (e.g. TextCategoryState = "Title" on a Label instance → Label.Title, with the BaseType chain walked via GetStateSaveRecursively):
    • LHSes from its VariableReferences rows are owned scalars.
    • Direct scalar variables on the state are owned (this is what catches the broader case where the state sets values directly without a ref — e.g. Label.Title.Variables["FontSize"] = 28).
    • If the matched state has any VariableReferences row, the qualified list marker "<instance>.VariableReferences" is also added so paste drops the base-snapshotted reference row that would otherwise shadow the categorized walk.

Anything in a base capture whose name matches the owned set is dropped rather than snapshotted. The new instance picks up the active categorized state's contribution via the normal GetValueRecursive / GetVariableListRecursive walks instead of carrying the source's base-level orphans.

The walk is implemented in ElementSaveExtensions.GetItemNamesOwnedByReachableCategorizedStates(StateSave, InstanceSave). The shape mirrors HeadlessErrorChecker's GUM0002 check, though GUM0002 currently only flags the reference-owned subset; broadening the error check to direct-scalar conflicts is a separate piece of work.

Variables and lists on the source's own selected state are never filtered — directly-authored values pass through untouched even when they conflict with a reachable reference. GUM0002 handles surfacing that conflict at the source; copy/paste preserves author intent.

Undo Integration

Paste and cut each acquire an undo lock (_undoManager.RequestLock()) for their whole operation. The entire paste — all instances, state variable copies, parent assignments — records as a single undo action; a cut records the removal of every cut instance as one action. IDeleteLogic.RemoveInstance() does not take a lock of its own, so any caller that removes through it must hold one (#4691).

State Paste Validation

Pasting a state runs ValidateStatePaste() first. It checks that all variables in the copied state exist in the target category and are supported by the target element. Paste is silently blocked (or shows a dialog) if incompatible.

Plugin Hook

Pasting a category or a state raises CategoryAdd / StateAdd through ICopyPastePluginNotifier, like adding one by hand (the File Watch plugin forgets its referenced-file set on them, and code output refreshes).

PluginManager.InstanceAdd() is called for each newly pasted instance, allowing plugins to react to paste-created instances the same way they react to manually added ones.

Duplicating or pasting an element raises ElementDuplicate before the copy is added, so plugins copy their sidecar files (.codsj, animation file) there; ElementAdd handlers must read the new element's own settings, not the tab's.

Animation Copy/Paste

AnimationCopyPasteManager.cs is a separate, independent copy/paste system for animations. It has its own CopiedData class, stores a single AnimationViewModel, and does not interact with CopyPasteLogic.

Entry Points

All copy/paste is triggered through:

  • HotkeyManager — routes Ctrl+C / Ctrl+X / Ctrl+V → ICopyPasteLogic.OnCopy / OnCut / OnPaste
  • ElementTreeViewManager.RightClick — right-click context menu items

Do not call CopyPasteLogic methods directly from outside these entry points.

Key Files

FilePurpose
Tools/Gum.Presentation/Logic/CopyPasteLogic.csAll copy/paste orchestration; CopiedData nested class defined here
Tools/Gum.Presentation/Logic/ICopyPasteLogic.csInterface
Tools/Gum.Presentation/Commands/EditCommands.csThin wrappers that delegate to ICopyPasteLogic
Tools/Gum.Presentation/Managers/HotkeyManager.csKeyboard entry point
Tool/TreeViewPlugin.Core/ElementTreeViewManager.RightClick.csContext menu entry point
Gum/StateAnimationPlugin/Managers/AnimationCopyPasteManager.csSeparate animation copy/paste
Tool/Tests/GumToolUnitTests/Logic/CopyPasteLogicTests.csWPF-head unit tests
Tests/Gum.Presentation.Tests/Logic/CopyPasteLogicExpansionTests.csHeadless unit tests for pasted-node expansion

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.