workflow-editor-copy-paste

Standardize copy and paste operations across workflow editor surfaces.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-editor-copy-paste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-editor-copy-paste
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/workflow-editor-copy-paste
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-editor-copy-paste

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the fragmentation of clipboard behavior in complex workflow editors, ensuring that copy and paste operations remain consistent across graph workspaces, inspector panels, and toolbar shortcuts.

Core Features & Use Cases

  • Host-Owned Clipboard State: Centralizes clipboard logic to maintain consistent undo history and accessibility announcements.
  • Structural Selection: Decouples selection from clipboard implementation, allowing different surfaces to contribute to the same copy-paste flow.
  • Safe Payload Handling: Normalizes action timing and excludes transitions during copy to ensure pasted nodes re-enter validation flows safely.

Quick Start

Apply the workflow editor copy-paste pattern to your component by centralizing clipboard state in the host editor and ensuring structural surfaces only contribute selection data.

Frequently Asked Questions about workflow-editor-copy-paste

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain consistent clipboard behavior across different workflow editor surfaces?

Consistent clipboard behavior is maintained by centralizing copy-paste state in the host editor, allowing graph workspaces and inspector panels to contribute selection data without fragmenting undo history.

Why does pasting duplicated nodes break validation flows in my workflow editor?

Pasting duplicated nodes breaks validation because transition logic is often copied inadvertently. Normalizing action timing and excluding transitions during node duplication ensures pasted nodes re-enter validation flows safely.

What is the best way to decouple structural selection from clipboard implementation?

Decoupling structural selection from clipboard implementation requires centralizing clipboard state in the host editor while different surfaces, like graph workspaces and inspector panels, only contribute selection data to the copy-paste flow.

How do I standardize copy and paste operations across graph workspaces and toolbar shortcuts?

Standardizing copy and paste operations involves centralizing clipboard logic in the host editor to unify behavior across graph workspaces, inspector action lists, and toolbar shortcuts, preventing state fragmentation.

Does centralizing clipboard state in the host editor improve accessibility announcements?

Centralizing clipboard state in the host editor improves accessibility announcements and maintains consistent undo history by providing a single source of truth for all copy-paste operations.

When should I exclude transition logic during node duplication in a workflow authoring environment?

Transition logic should be excluded during node duplication whenever pasted nodes must re-enter validation flows safely, preventing structural integrity issues caused by copying transition timing alongside the node payload.