AI-Generated UI On Demand
Purpose
Design situational user interfaces that show only the fields, actions, and context needed for the current Dataverse task.
Use this skill for:
- task-specific forms
- generated dashboards
- approval dialogs
- data cleanup wizards
- guided record creation
- exception handling screens
V1 Boundary
This skill plans UI behavior, field selection, and interaction flows only. It does not generate, deploy, or modify Power Apps screens.
Workflow
- Define the current task, target user, and decision the UI must support.
- Select only relevant fields, records, actions, warnings, and evidence.
- Define UI type: form, table, wizard, dashboard, approval dialog, or review panel.
- Add validation, confirmation, explainability, and accessibility requirements.
- Map UI elements to Dataverse fields, views, forms, command actions, custom pages, or canvas app components.
Output Format
Return:
Task UI goal: what the generated UI helps the user complete.UI pattern: form, table, wizard, dashboard, approval dialog, or review panel.Displayed context: fields, records, warnings, and explanations.Actions: available buttons or commands and their confirmation rules.Power Platform mapping: components to inspect or build.
1---2name: ai-generated-ui-on-demand3description: Use when planning dynamic task-specific forms, dashboards, tables, wizards, approval dialogs, or input masks generated for Dataverse and Power Apps scenarios. Produces UI plans only and generates no live UI.4---56# AI-Generated UI On Demand78## Purpose9Design situational user interfaces that show only the fields, actions, and context needed for the current Dataverse task.1011Use this skill for:12- task-specific forms13- generated dashboards14- approval dialogs15- data cleanup wizards16- guided record creation17- exception handling screens1819## V1 Boundary20This skill plans UI behavior, field selection, and interaction flows only. It does not generate, deploy, or modify Power Apps screens.2122## Workflow231. Define the current task, target user, and decision the UI must support.242. Select only relevant fields, records, actions, warnings, and evidence.253. Define UI type: form, table, wizard, dashboard, approval dialog, or review panel.264. Add validation, confirmation, explainability, and accessibility requirements.275. Map UI elements to Dataverse fields, views, forms, command actions, custom pages, or canvas app components.2829## Output Format30Return:31- `Task UI goal`: what the generated UI helps the user complete.32- `UI pattern`: form, table, wizard, dashboard, approval dialog, or review panel.33- `Displayed context`: fields, records, warnings, and explanations.34- `Actions`: available buttons or commands and their confirmation rules.35- `Power Platform mapping`: components to inspect or build.36
rweisssieker-xp