Workflows

Loomle workflows follow one inspect-and-verify loop:

1. Bind one project with project.
2. Locate the real UE target with editor({}) or an exact Asset Path.
3. Read a compact summary, collection, tree, context, or flow.
4. Load a static interface card or exact dynamic schema only when needed.
5. Search the target Palette before creating a UE object.
6. Send one complete dry-run Patch through sal_patch.
7. Apply the same authored Patch after validation.
8. Read back the affected state.
9. Compile and save through the exact owning asset.

The examples use placeholder StableRef segments because real identities and Palette capabilities must come from the current project. Copy returned flat Targets, @identityPath references, brace object fields, and invocation templates; do not invent them.

Available Workflows

• Format a Blueprint Graph loads Loomle’s resident formatting Skill, requires precise live geometry, plans absolute move-only edits, and audits the measured result.
• Add a Blueprint Node follows Graph discovery, Palette creation, dry run, apply, and Blueprint finalization.
• Edit Blueprint Switch Cases uses exact Node schema for a dynamic UE operation.
• Add Widget Text edits an authored Widget tree and finalizes the owning WidgetBlueprint.

Foundation Guides

Use these guides before a domain workflow when the underlying step is unfamiliar:

• Project Binding
• Editor
• SAL Working Model
• Targets and Stable References
• Schema Discovery
• Mutations and Finalization

Additional workflows for factual reference queries, StateTree editing, and diagnostic recovery will follow this same model.

---

Table of contents

• Format a Blueprint Graph
• Add a Blueprint Node
• Edit Blueprint Switch Cases
• Add Widget Text