Create developer-ready UiPath Coded Web Apps and Coded Action Apps through one guided workflow: shape a small use case, check prerequisites, scaffold a TypeScript interface, display safe demo data, build, authenticate, publish, deploy, open the live URL, and optionally publish the source to GitHub.
Important
This is an independent community skill. It is not an official UiPath product. Current UiPath commands, SDK contracts, OAuth scopes, and platform operations remain owned by the installed official UiPath skills.
- Turn a simple idea into a focused UI without a lengthy discovery process.
- Confirm whether the developer machine is ready before creating files.
- Build an initial React and TypeScript UI with clearly labeled fictional data.
- Configure
@uipath/uipath-typescriptonly when live UiPath services are needed. - Reuse a matching UiPath CLI login or guide the user through interactive authentication.
- Recommend consistent application, package, Git branch, and Orchestrator folder names.
- Find or create an Orchestrator folder with explicit approval.
- Produce a least-privilege access request when deployment access is missing.
- Build, pack, publish, and deploy through the official
uipath-coded-appsowner. - Open and visually verify local and deployed Web App URLs.
- Create a structured application README and safely publish source to GitHub.
| Mode | Result |
|---|---|
local |
Scaffold, demo UI, structured README, local browser verification, and successful build |
deploy |
Local result plus UiPath authentication, folder resolution, pack, publish, deploy, and live URL verification |
deploy-and-git |
Deployed result plus intentional Git commit, push, and draft GitHub pull request |
Install the UiPath CLI and official skill catalog according to your organization's approved setup. With the UiPath CLI available, the standard skill installation is:
uip skills installThe official uipath-coded-apps and uipath-platform skills remain the product and tenant-operation owners used by this skill.
For Codex:
npx skills add 1aifanatic/uipath-coded-app-launchpad `
--skill create-uipath-coded-app `
--agent codex `
--global `
--yesStart a new Codex conversation after installation so the skill is discovered.
Invoke the skill by name and provide the desired app type and delivery mode:
Use $create-uipath-coded-app.
Create a Coded Web App named claims-review-dashboard.
Build a responsive dashboard for claims reviewers to see pending claims.
Use safe fictional demo data and clearly label it.
Use local delivery mode and open the interface in a browser.
Create the project in C:\projects\claims-review-dashboard.
For complete local, deployment, SDK, Action App, access, and GitHub examples, see the Prompt Cookbook.
Use case and app type
-> delivery authority
-> machine preflight
-> UI and demo data
-> SDK and authentication, when needed
-> build and local browser verification
-> Orchestrator folder and access
-> pack, publish, deploy
-> live browser verification
-> optional GitHub publication
The skill coordinates installed owners rather than duplicating their current product behavior:
uipath-coded-appsowns Coded App artifacts and lifecycle operations.uipath-platformowns authentication, tenant, folder, user, group, and role operations.github:yeetowns intentional GitHub commit, push, and pull-request publication.- Browser control owns visual navigation and verification when available.
The bundled Windows PowerShell checker is read-only. It reports readiness without installing software, authenticating, changing tenant state, deploying, or pushing Git changes.
Check readiness for a Web App that will be published to GitHub:
powershell -NoProfile -ExecutionPolicy Bypass `
-File .\create-uipath-coded-app\scripts\check-prerequisites.ps1 `
-Stage Scaffold `
-AppType Web `
-SourcePublish GitHub `
-OutputFormat JsonCheck an existing project before build:
powershell -NoProfile -ExecutionPolicy Bypass `
-File .\create-uipath-coded-app\scripts\check-prerequisites.ps1 `
-Stage Build `
-AppType Web `
-ProjectPath C:\projects\claims-review-dashboard `
-RequirePlatformSdk `
-OutputFormat JsonExit code 0 means all required checks passed. Exit code 1 means at least one required check failed. The JSON report does not print .env values, credentials, access tokens, folder keys, or deployment URLs.
uipath-coded-app-launchpad/
README.md
docs/
PROMPTS.md
create-uipath-coded-app/
SKILL.md
agents/openai.yaml
references/
scripts/check-prerequisites.ps1
The skill requires or recognizes explicit authority before it performs consequential operations. It does not silently:
- Install or upgrade global software.
- Create or change OAuth applications.
- Create Orchestrator folders or alter access.
- Overwrite non-empty destinations.
- Publish or deploy to a tenant.
- Create GitHub repositories, push branches, or stage unrelated changes.
It never asks for raw access tokens, passwords, or client secrets. Interactive authentication remains in the supported UiPath or GitHub login flow.
The current package has been structurally validated. Its prerequisite checker has been exercised on Windows PowerShell 5.1 against:
- Web and Action App success fixtures.
- Git and GitHub prerequisites.
- Explicit app-type enforcement.
- Missing tools and invalid projects.
- Missing README and invalid folder-key failures.
- HTTPS deployment URL validation.
- Secret-redaction behavior.
The checks do not claim runtime compatibility outside the observed environment, and fixture success does not replace a real application build or tenant deployment.
- Browse this skill on the web — rendered instructions with copy-ready install commands
- Skill instructions
- Readiness contract
- Evaluation scenarios
- Prompt Cookbook