← VoltformerCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Voltformer
Snapshot Sep 30, 2026 · 23:11 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "voltformer-sld-engineering",
"description": "Create, edit, analyze, revise, and export member-owned electrical single-line diagrams with Voltformer. Use when a user asks for SLD drafting, diagram changes, studies, revisions, catalog links, or project-equipment synchronization.",
"included_files": [],
"skill_md_contents": "---\nname: voltformer-sld-engineering\ndescription: Create, edit, analyze, revise, and export member-owned electrical single-line diagrams with Voltformer. Use when a user asks for SLD drafting, diagram changes, studies, revisions, catalog links, or project-equipment synchronization.\n---\n\n# Voltformer SLD engineering\n\nMaintain editable, version-safe diagrams in the connected member's Voltformer workspace and clearly separate calculations from engineering approval.\n\n## Workflow\n\n1. Confirm the user is connected and identify the owned project. Use `getSldCapabilities` before drafting when symbols, templates, studies, or the editing contract are needed.\n2. Create a diagram with `createSldDocument`, or list and retrieve an existing diagram with `listSldDocuments` and `getSldDocument`.\n3. Before editing, read the complete current snapshot. Preserve unedited sheets, elements, terminals, busbars, connections, junctions, annotations, metadata, and study settings.\n4. Apply requested editor changes to the snapshot and call `saveSldDocument` with its current storage version. If a conflict occurs, reread, reconcile, and ask the user when intent is ambiguous.\n5. Use `linkSldCatalogProduct` for catalog-backed component properties and `syncSldProjectEquipment` only when the user wants diagram equipment merged into the project.\n6. Use `analyzeSldDocument` or `runSldStudy` only when inputs are sufficient; otherwise report missing inputs. Use `exportSldDocument` for the requested supported formats.\n7. Create an immutable revision only when requested. Treat approval-status changes, snapshot replacement, synchronization, and deletion as consequential actions.\n\n## Invariants\n\n- Never invent terminals, ratings, study results, catalog links, or approval status.\n- Do not overwrite on stale versions or discard fields the user did not ask to change.\n- Obtain explicit confirmation immediately before deletion, replacing a saved snapshot, creating an approval revision, linking properties that overwrite element data, or synchronizing project equipment.\n- Describe engineering studies as preliminary and requiring qualified review.\n\n"
}SHA-256: 11f6edb6940ac5cc833e0740148b014977862e429de6cb13bb4b6af2b3b7063e