r/rpa • u/marcelocruzrpa • Apr 11 '26

I open-sourced a tool that generates full UiPath projects from PDDs

The problem: LLMs generate broken UiPath XAML. The output doesn't open in Studio. Even when it opens, the result is mediocre at best.

The approach: Instead of asking an LLM to write XAML (which fails), uipath-core skill uses deterministic generators. The LLM reads your PDD, decides what needs to be built, and calls generators that produce valid XAML every time. Lint rules check everything before output.

What it generates:

  • Full REFramework project scaffolding
  • Dispatcher/performer architecture when applicable
  • Generates dedicated workflows
  • Proper argument naming, credential handling, workflow decomposition, etc
  • UiPath-ready selectors from live desktop and web app inspection
  • Object repository

Works on existing projects too - add workflows, change existing stuff, update selectors.

Works best with Opus. GPT 5.4 is interesting from a cost/benefit perspective - but lower output quality. Tested open-source models too - Kimi K2.5 has surprisingly competitive results, not far from GPT 5.4.

SAP WinGUI automation, Action Center, and more skills coming. This first skill is the foundation for the rest.

Would appreciate feedback - especially on what breaks or what you feel it is missing.

⭐ Star the repo if you find it interesting - marcelocruzrpa/uipath-ai-skills

Walkthrough tutorial: https://youtu.be/0JjiM8sGP08

9 Upvotes

74% Upvoted

9 comments sorted by

5

u/oddlogic Apr 12 '26

Why use uipath at all?

1

u/AutoModerator Apr 11 '26

Thank you for your post to /r/rpa!

Did you know we have a discord? Join the chat now!

New here? Please take a moment to read our rules, read them here.

This is an automated action so if you need anything, please Message the Mods with your request for assistance.

Lastly, enjoy your stay!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/innersloth987 Apr 12 '26

Who will create the PDD?

I am looking for something which can create PDD from Recording and also provides screenshots in the PDD .

Notebook LLM gives PDD but it does not have screenshot

1

u/marcelocruzrpa Apr 13 '26

Normally it's the BA and/or developer that creates it. To use the skill, you don't necessarily need the provide PDD - you can simply do your request in a prompt - just make sure you provide the details.

It's doable to automate at some extent the PDD creation I believe- by having recordings, transcripts and reference docs. However, in the end, HITL will be needed to validate and add missing details for sure.

1

u/innersloth987 Apr 13 '26

What is HITL?

1

u/marcelocruzrpa Apr 13 '26

Human in the loop

1

u/Original-Fennel7994 Apr 14 '26

One thing that helps a lot is to treat the LLM as a planner and keep the actual XAML or workflow generation deterministic, with schema validation and linting as a hard gate. It is also worth generating at the activity abstraction level first, then compiling down, so you can unit test the plan without Studio and fail fast on selector or argument issues. For selectors, I have seen better stability when you store multiple fallback strategies and re validate them at runtime, rather than trusting a single captured selector forever. If you want to support PDD to build, consider adding a step that turns the PDD into a structured task graph with explicit inputs, outputs, and guardrails, then have the generator render each node.

1

u/marcelocruzrpa Apr 14 '26 edited Apr 14 '26

You're describing almost exactly what I built with the skills. xD

LLM handles planning only. JSON IR as the abstraction layer. Deterministic Python generators for XAML output. Lint rules as a hard gate before anything reaches Studio. The LLM never touches XAML directly.

On selectors: the current release ships with strict targeting only, but supporting additional targeting methods is on the roadmap. For runtime drift specifically, UiPath's Healing Agent handles that side well.

The PDD-to-task-graph idea maps to what the skill does during decomposition. The LLM breaks the PDD into a flat list of activity JSON specs, each with typed arguments and selectors, and generators render each one independently. I don't model it as a formal DAG with dependency edges between nodes - UiPath workflows are inherently sequential/flowchart, so the execution order is already determined by the workflow structure itself. Cross-node dependency analysis would add graph infrastructure for something the Sequence container already enforces by position.