uipath-diagram-design

name	uipath-diagram-design
description	Create crisp, evidence-backed explanatory diagrams for UiPath solutions. Use for solution architecture, process swimlanes, interaction sequences, state or lifecycle models, and deployment or integration topology when verified UiPath artifacts, approved documents, or user decisions need a communication-grade HTML, SVG, and PNG visual.

UiPath Diagram Design

Turn verified UiPath facts into a focused communication artifact. Produce explanatory visuals; leave executable UiPath artifacts and current product truth with their official owners.

Maturity: pilot.

Ownership Boundary

This custom skill owns: communication-grade diagrams that explain verified UiPath solutions, responsibilities, interactions, lifecycles, deployments, and integrations.

It does not author or validate .xaml, .flow, .bpmn, agent.json, project.uiproj, tenant configuration, or other executable product artifacts. Use official UiPath skills for those surfaces.

Supported Diagram Types

Need	Type	Read before drawing
Components, services, systems, and data movement	Solution architecture	references/solution-architecture.md
Actor ownership and cross-functional handoffs	Process swimlane	references/process-swimlane.md
Time-ordered messages among humans, agents, robots, and systems	Interaction sequence	references/interaction-sequence.md
States, transitions, retries, failures, and completion	State and lifecycle	references/state-lifecycle.md
Environment promotion and runtime connections	Deployment and integration	references/deployment-integration.md

Read exactly one type reference for the primary diagram. Split the request when two grammars compete.

Workflow

1. Establish the communication question

Identify the audience, the decision or understanding the diagram must enable, the primary diagram type, and the required output location.

Completion criterion: One sentence states what the reader must understand after viewing the diagram.

2. Build the evidence inventory

Use facts in this order: validated official-skill output, approved repository or PDD/SDD content, explicit user decisions, working notes, then clearly labeled inference. Read references/evidence-and-boundaries.md.

Ask only for facts whose absence would materially change the diagram. Label synthetic examples, assumptions, and inference inside the artifact metadata.

Completion criterion: Every node and connector is supported, user-approved, or labeled as inference or synthetic.

3. Design within the visual budget

Read references/visual-system.md and the selected type reference. Use at most 9 nodes, 12 connectors, 2 orange focal elements, and 5 lanes or lifelines unless the type reference sets a stricter limit.

Use the seven UiPath semantic roles: human, automation, orchestration, UiPath service, external system, data or artifact, and control or evidence.

Completion criterion: The layout has one dominant reading direction, a clear focal point, and no unearned element.

4. Create the diagram-only HTML

Write a self-contained HTML file with one inline accessible SVG using viewBox="0 0 1600 900". Include <title>, <desc>, and <metadata>. Use system fonts, inline CSS, and no JavaScript or external assets.

Save new work under diagrams/<slug>/<slug>.html unless the user names another location. If the target exists, add -v2, -v3, and so on rather than overwriting it.

An official UiPath logo may appear only when the user supplies an authorized local asset or written permission. Product names and semantic shapes remain sufficient by default.

Completion criterion: The HTML opens without a network connection and the SVG contains the complete diagram.

5. Export SVG and PNG

Read references/export.md, then run scripts/export_diagram.py. The helper uses only the Python standard library for SVG extraction and an already installed Chrome, Edge, or Chromium browser for PNG rendering. It never installs dependencies.

Completion criterion: Matching .html, .svg, and 1600x900 .png files exist, or the response explicitly reports the missing browser and the incomplete PNG requirement.

6. Inspect the rendered result

Open the PNG at full resolution. Check text containment, connector routing, label gaps, attach points, hierarchy, contrast, and legibility. Correct every clipped label, box collision, shared connector path, or ambiguous arrow before finishing.

Completion criterion: The rendered pixels, not only the source, pass the visual checks in the selected type reference.

7. Report evidence and handoff

Return clickable paths to every output, name the selected type, list important assumptions or inference, and state that the visual is explanatory rather than executable.

Completion criterion: A reader can open the outputs, understand their evidence status, and identify the official owner for any next product change.

Compose With Official UiPath Skills

• Use uipath-solution and uipath-planner for authoritative solution design content.
• Use uipath-rpa, uipath-agents, uipath-maestro-flow, and uipath-maestro-bpmn for executable artifacts.
• Use uipath-review to establish verified project findings.
• Use uipath-platform, uipath-admin, and uipath-governance for observed tenant and platform state.
• Use uipath-process-mining for mined process graphs; use this skill only to explain verified findings.

Output Contract

• One evidence-backed diagram with one primary grammar.
• Self-contained diagram-only HTML with accessible inline SVG.
• Extracted SVG and exact-size PNG preview.
• Evidence status, assumptions, inference, and explanatory-artifact disclaimer.
• Official UiPath handoff for any executable or platform work.

Guardrails

• Keep customer data, credentials, tenant identifiers, and confidential architecture out unless explicitly approved and safely handled.
• Preserve product truth from official outputs; never invent services, commands, schemas, or successful runtime behavior.
• Use orthogonal connectors for off-axis nodes and distinct attach points for multiple edges.
• Treat PNG generation as incomplete when no compatible local browser is available.
• Keep community-project labeling visible when public examples could imply UiPath endorsement.

Example Requests

• "Create a UiPath solution architecture from this approved SDD."
• "Show the human exception path as a five-lane swimlane."
• "Create a sequence diagram for Maestro, an agent, a robot, and a reviewer."
• "Visualize this queue item's retry and terminal-failure lifecycle."
• "Show our Dev, Test, and Production promotion and runtime integrations."

Finish

Report the generated files, selected grammar, evidence and assumptions, render validation, next official owner, and every unresolved blocker. Never imply that a UiPath artifact, tenant configuration, deployment, or runtime behavior was created or validated unless its official owner actually performed and observed that work.

Design Lineage

The focused visual system is adapted from Kathryn Lavery's MIT-licensed diagram-design project. See THIRD_PARTY_LICENSES.md for the retained notice and modification summary.