UiPath Genome — document, author, and execute automation blueprints

Genome: markdown specification an AI agent consumes to rebuild an automation — what it does, business rules, data moving between parts, platform resources, its transactional shape, verification, and which UiPath skill builds each part. Genomes stay thin: build skills carry UiPath know-how; a genome describes what, skills know how.

Read by the mode's read plan (§ Read Plans), never from memory. This file routes; guides carry the rules, each subject in exactly one guide. A file the plan reads whole is read whole — not grepped or skimmed; a pointer that names a section (guide.md § Section) is a section read, that section in full; a guide no condition of the plan has reached stays closed, and the CLAUDE.md beside this file, which governs editing the skill, is not read in a run. A framework selectors guide's per-technology tables are a catalog, read by section: list its headings, then read the sections for the technologies the source recorded; the rules around them are read whole.

When to Use This Skill

• Existing UiPath project or solution to document, understand, or prepare for migration ("what does this solution do", "extract a genome", "document this process at high and low level")
• Described automation idea needing a specification before building, or a goal (a self-paced workshop, a demo, trying a product) needing a scenario proposed first
• *-genome.md file to build from
• Existing genome to update, split into components, or re-extract after source changed

Mode Detection

Determine mode from input, in this order: