| name | uipath-component-design |
| description | Design a deep UiPath component or project contract by exploring several genuinely different shapes before selecting one. Use for reusable libraries, workflow interfaces, coded automation modules, agents, Maestro processes, API workflows, human tasks, queue contracts, and integration adapters that need clear seams and testable behavior. |
| category | Design and architecture |
UiPath Component Design
Hide substantial behavior behind a small, stable contract so callers gain leverage, maintainers gain locality, and tests exercise the same seam used in production.
Maturity: core.
Ownership Boundary
This custom skill owns: Hide substantial behavior behind a small, stable contract so callers gain leverage, maintainers gain locality, and tests exercise the same seam used in production.
Keep current product commands, schemas, artifact validation, live tenant operations, and policy administration with official UiPath skills.
Compose With Official UiPath Skills
Use official skills for current product commands and artifact contracts:
uipath-rpauipath-agentsuipath-maestro-flowuipath-maestro-bpmnuipath-maestro-caseuipath-api-workflowuipath-human-in-the-loop
Workflow
1. Define behavior and callers
State the business capability, callers, inputs, outputs, invariants, error modes, performance expectations, audit needs, and what must remain hidden.
