- 📁 assets/
- 📁 evals/
- 📁 references/
- 📄 requirements.txt
- 📄 SKILL.md
Generates UiPath Studio XAML workflows, project scaffolds (sequence/dispatcher/performer), and expressions via 94 deterministic Python generators (plus additional generators from installed plugin skills). Use when the user mentions UiPath, XAML, RPA, REFramework, Orchestrator, or UiPath Studio development. --- # UiPath Core Skill > ⚠️ **Safety Rules** (I-1, I-2 in `rules.md`) > - Playwright/browser inspection is **READ-ONLY**. Login page → STOP, WAIT for user. See `ui-inspection.md` → Login Gate. > - Desktop inspection via PowerShell (`inspect-ui-tree.ps1`): read-only tree inspection only. > - NEVER generate credentials, tokens, or passwords — real or fake. Generate production-quality UiPath automation artifacts using real Studio-exported templates and comprehensive reference documentation. Template baseline: Studio 24.10 Windows. ## When To Read Which Reference **Start here.** Match the user's task to the right file, then read only what's needed. For files > 200 lines, use `grep` or line-range reads — never read entire large files or XAML assets. ### Common Tasks (check these first) | Task | Read first | |---|---| | Generate a XAML workflow (any kind) | `cheat-sheet.md` → JSON spec patterns → `scripts/generate_workflow.py` **(G-1)** | | Scaffold a project | `scaffolding.md` → Template Selection → run `scripts/scaffold_project.py` | | Generate a full project (checklist) | `scaffolding.md` → "Generating a Full Project" checklist | | Inspect a web app (selectors) | `ui-inspection.md` → Playwright MCP workflow → `playwright-selectors.md` | | Validate XAML | Run `scripts/validate_xaml <project> --lint` | | Fix a specific lint warning | `lint-reference.md` → search by lint number | | Write an expression (VB.NET/C#) | `expr-foundations.md` (start here for any expression task) | | Decomposition / project structure | `decomposition.md` → Decomposition rules (Universal 1-8, Browser 9-13, Desktop 14) | | Fix a user's .xaml file | `skill-guide.md` → Example 6 | | Action Center
Build immersive 3D web experiences with Three.js, React Three Fiber, Spline, and WebGL. Covers product configurators, 3D portfolios, scroll-driven 3D, model pipeline optimization, performance budgets, and interactive scenes. Use when building 3D websites, three.js scenes, or WebGL experiences.
Ask a specific AI model (codex, gemini, grok, perplexity, claude) for focused analysis or a second opinion
Use when the user wants to view, change, or reset their persistent preferences, or when triggered by "/caliper-settings", "my settings", "change defaults".
Complete architecture guide for building features from database to UI. Routes to frontend/, fullstack/, mobile/, backend/, or sdks/ based on detected stack. Covers decomposition, multi-tenant isolation, auth model, query patterns, and component patterns.
Add or update a model in the harness model registry. Use when the user wants to add a new AI model, update model pricing, or change default models for a harness.
- 📁 templates/
- 📄 LICENSE.txt
- 📄 SKILL.md
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.
Map requirements (PRD/user stories/AC) to comprehensive test coverage using a traceability matrix (RTM). Outputs coverage gaps, risks, test levels, prioritization, automation candidates, and change-impact notes. Designed for QA/Test Architect workflows.
Schedule recurring tasks (cron) and periodic agent check-ins (heartbeat).
PHP debugging and analysis tools using Xdebug. Use when asked to trace, debug, profile, or analyze coverage of PHP code. Trigger phrases include "trace this function", "profile this code", "check coverage", "debug PHP", "set breakpoint", "find the bottleneck", "why is this slow", "トレース", "プロファイル", "カバレッジ".
The absolute gatekeeping factor for app development success. Context-first, never act without verified planning, unbroken hierarchy chains, and domain boundaries enforced.
