Update to Aivana Dataverse App Architect

{
  "name": "app-design-review",
  "description": "Creates a reviewable architecture and UX blueprint for new or existing Dataverse model-driven apps and evaluates it through mandatory quality gates.",
  "included_files": [],
  "skill_md_contents": "---\nname: app-design-review\ndescription: Creates a reviewable architecture and UX blueprint for new or existing Dataverse model-driven apps and evaluates it through mandatory quality gates.\n---\n\n## Architect edition scope\n\nThis edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.\n\n# App Design Review\n\nStart by capturing users, tasks, records, lifecycle, security roles, devices, integrations, licensing, accessibility, reporting, and acceptance criteria. Inspect any existing solution before proposing changes. Produce a solution-first blueprint with logical names, ownership, relationships, form sections, views, commands, sitemap, business rules, and explicit non-goals.\n\nEvaluate the blueprint against Microsoft-aligned UX, performance, accessibility, privacy, security, ALM, data-quality, and supportability gates. Identify risks, dependencies, and evidence required to move into implementation. A design review is complete only when assumptions, decisions, acceptance tests, rollback intent, and owners are explicit.\n"
}