RPA Workflow Architect

Generate and edit RPA workflows using a discovery-first approach with iterative error-driven refinement. Always understand before acting, start simple, and validate continuously.

This skill uses uip CLI commands (via Bash) and Claude Code's built-in tools (Read, Write, Edit, Glob, Grep) to interact with UiPath Studio Desktop projects and manage workflow files.

Core Principles

1. Activity Docs Are the Source of Truth — Installed packages may ship structured documentation at {projectRoot}/.local/docs/packages/{PackageId}/. When present, these docs contain source-accurate properties, types, defaults, enum values, conditional property groups, and working XAML examples. They eliminate guesswork and are more reliable than examples or CLI-retrieved defaults. Always check for them first; push for package updates if unavailable, or fallback to get-default-activity-xaml and/or get-workflow-example.
2. Know Before You Write — Never generate XAML blind. Never try to guess properties, types, or configurations. Understand the project structure, what packages are installed, what expression language is used, and what patterns existing workflows follow. The deeper your understanding, the fewer validation cycles you'll need.
3. Use What You Know, Skip What You Don't Need — If you already know the package ID and activity class name, go directly to its doc file — don't enumerate all packages first. If activity docs give you a complete XAML example, don't also call get-default-activity-xaml. Be efficient: the discovery steps are a priority ladder, not a mandatory checklist.
4. Start Minimal, Iterate to Correct — Build one activity at a time. Write the smallest working XAML, validate with uip rpa get-errors --use-studio, fix what breaks, repeat. Start with what you know works (default or example values, configurations). Complex workflows emerge from validated building blocks, not from generating everything at once.
5. Validate After Every Change — Never assume an edit succeeded. Always confirm with uip rpa get-errors --use-studio. Static validation catches most problems; run-file catches the rest.
6. Fix Errors by Category — Triage errors in order: Package (missing dependencies) → Structure (invalid XML) → Type (wrong property types) → Activity Properties (misconfigured activity) → Logic (wrong behavior). Fixing in this order avoids cascading false errors.

CLI Output Format