Iec Network Drawio

IEC Network Draw.io

Core Rule

Preserve the original electrical topology and spatial layout unless the user explicitly asks for a redesign. Improve symbols, spacing, alignment, and readability without changing feeder order, branch positions, protection placement, or network connectivity.

For new diagrams without an existing source, establish the topology from the user's description first. Do not invent feeders, devices, ratings, switch states, or distributed energy resources that were not provided or explicitly requested.

Workflow

1. Inspect the source .drawio XML and any reference screenshots or exported images before editing. If creating a new diagram, inspect the user's topology description and identify any missing connectivity details.
2. Inventory the topology: source or MV grid, MV bus, switches or breakers, transformer, LV bus, feeders, branches, loads, measurements, and legend.
3. Decide whether the task is a symbol replacement, alignment cleanup, busbar insertion, full redraw, or validation-only pass.
4. Modify only the requested or necessary elements. Keep branch endpoints and feeder order stable unless the user asks for layout changes.
5. Generate or edit the diagram as editable Draw.io mxCell primitives, not as a flattened screenshot or embedded raster.
6. Render or export the final .drawio, then visually inspect alignment, symbol overlap, text-symbol overlap, label clutter, and unintended crossings. Do not rely only on XML geometry checks when visual rendering is available.

Topology Rules

• Do not convert a radial feeder drawing into a row-based topology unless explicitly requested.
• Preserve open points, switches, protection devices, and measurement locations when they exist in the source.
• Add an LV busbar only as a structural common bus for existing LV feeder taps.
• When adding an LV busbar to a radial layout, extend it far enough to span the feeder tap points while preserving original feeder positions.
• Connect feeders to busbars cleanly at aligned tap points.
• Do not add PV, storage, protection, or measurement symbols unless they are present in the source or requested by the user.
• Route conductors as horizontal or vertical segments by default. Avoid tilted or diagonal lines; use orthogonal bends when a connection cannot be drawn as a single straight segment.

Symbol Standards

Use these conventions by default:

• Busbar: thick black horizontal line. Label only meaningful busbars such as MV bus and LV bus.
• External grid or upstream network: densely cross-hatched square, connected to the upstream side of the network. Use repeated diagonal strokes in both directions so the square is visibly filled with a tight X-pattern. Keep all hatch/cross lines clipped inside the square boundary; no hatch strokes should exceed or protrude past the outline.
• MV node: represent an MV node as a busbar, not as a filled black circle.
• LV node: filled black circle at explicit LV bus, feeder, branch, or numbered node connection points. Use these solid balls by default for numbered LV nodes, as in common distribution-feeder figures.
• Load: proper filled arrow connected to the busbar or to an LV node. Draw a short conductor stem from the connection point to a filled triangular arrowhead; the stem must be perpendicular to the triangle base and centered on the arrowhead. Use one global arrow direction for loads across the diagram by default; do not mirror arrows left/right just because loads are on different feeder sides. Change direction only to avoid overlap or when the source/user explicitly specifies it. Follow the source or layout direction; use a downward arrow only when no orientation is implied. Do not add extra vertical strokes inside the load symbol.
• Transformer in main diagram: two overlapping transparent rings, oriented vertically or horizontally to match the original layout. Do not draw any conductor through the rings. Stop the conductor before the first ring and resume after the second ring. Label the transformer with the known voltage levels, such as MV/LV transformer or HV/MV transformer; if voltage levels are unknown, use Transformer.
• Transformer in legend: horizontal overlapping transparent rings.
• Load in legend: short horizontal line with a filled arrowhead followed by the label Load. Do not include an LV node marker in the load legend.
• Rings: use transparent or no fill so both ring outlines remain visible at the overlap.
• Switch or breaker: keep the source device location and state. Use a simple IEC-style open contact, closed contact, or breaker block only when the source implies that device.
• PV: do not include PV, L/P, or Load/PV labels unless explicitly requested.

Draw.io Implementation

• Use editable mxCell primitives: groups, edges, ellipses, rectangles, and text labels.
• Prefer structured XML parsing and generation over ad hoc string replacement.
• Use orthogonal connectors for feeders and branches unless the source drawing intentionally uses another routing style.
• Use black strokes and Times-style labels when matching technical IEC figures.
• Keep consistent stroke widths within symbol classes: busbars should be visually heavier than feeders and symbol outlines.
• Size symbols proportionally so the diagram looks balanced: nodes, arrows, transformer rings, external-grid squares, switch symbols, and labels should be visually compatible with conductor thickness and spacing.
• Keep page dimensions tight enough to frame the diagram without unnecessary whitespace.
• Preserve stable element IDs when making small edits to an existing .drawio file, unless regeneration is simpler and safe.

Labels And Legend

• Keep labels sparse and technical.
• Label MV bus and LV bus when those busbars exist.
• Do not label feeders with IDs such as F1, F2, or Feeder 1 unless the user explicitly requests feeder labels or the source diagram already uses them and the task is to preserve existing labels.
• Use a small legend for symbols that appear in the drawing, typically External grid, Bus, Load, Transformer, and any switch or breaker symbol actually present.
• Enclose the legend in a dashed rectangular box.
• Place the legend where it minimizes the total figure footprint while keeping clear spacing from the network and avoiding text-symbol overlap.
• Remove legend entries for components that do not exist in the diagram.
• Place all labels so they do not cross conductors, overlap symbols, touch arrowheads, or obscure switch states.

Alignment Rules

• Align LV load nodes on a grid: same feeder column means same x; equivalent load levels across feeders should share the same y.
• Align feeder tap points along the LV busbar.
• Center branch endpoints and load arrows on the connected busbar or LV node, regardless of arrow direction.
• Keep load arrows pointing in the same global direction for comparable nodes when space allows, even when loads are attached to different feeders or opposite sides of a layout.
• Use right-angle bends to keep feeder and branch conductors horizontal or vertical; avoid small diagonal shortcuts between nodes.
• Keep transformer rings centered on the main conductor path, with visible gaps where the conductor stops and resumes.
• Maintain clear spacing between text and graphical symbols. Move labels outward or adjust connector routing when text would overlap nodes, arrows, busbars, transformers, or the external-grid symbol.
• Keep symbol sizes aesthetically balanced across the diagram. Avoid oversized arrows, tiny transformer rings, disproportionate external-grid squares, or labels that visually dominate the electrical symbols.
• Position the legend compactly in unused whitespace near the diagram rather than expanding the canvas unnecessarily.

Output Rules

• Return a user-facing .drawio file unless the user only asked for review or validation.
• If generating companion exports, keep the .drawio as the source of truth and treat PNG/PDF/SVG exports as previews.
• Report any topology ambiguity instead of silently guessing a new network structure.

Validation Checklist

Before final delivery:

• Confirm the .drawio XML parses cleanly.
• Confirm the diagram remains editable as Draw.io primitives.
• Confirm no unintended PV, L/P, or Load/PV text remains unless requested.
• Confirm no conductor lines cross through transformer rings.
• Confirm transformer ring overlaps are visible.
• Confirm explicit LV connection nodes use filled black circles unless another node style was requested.
• Confirm LV nodes are aligned horizontally and vertically.
• Confirm comparable load arrows point in the same global direction unless a different direction avoids overlap or follows an explicit instruction.
• Confirm conductors are horizontal or vertical, with no unintended tilted segments.
• Confirm symbol sizes are balanced and visually consistent across the diagram.
• Confirm no text overlaps or touches symbols, conductors, arrowheads, or other labels.
• Confirm feeder labels such as F1 and F2 are absent unless explicitly requested or intentionally preserved from the source.
• Confirm the legend is enclosed in a dashed box and placed compactly to avoid unnecessary figure whitespace.
• Confirm labels and legend entries match the actual symbols in the drawing.
• Render or export the .drawio and inspect the actual visual output specifically for text-symbol overlap and label readability. If Draw.io export tooling is unavailable, report that limitation and perform XML-level checks for geometry, labels, and symbol consistency instead.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Plusero
• Source: Plusero/agentic-research-skills
• License: CC0-1.0

Install and usage instructions live in the source repository linked above.