{"id":19608,"plugin_id":"plugins_6a9a4a13b2088191832975a573c4b649","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:40.892Z","digest":"0d75cb172fb022161f6775da56a49cf369b3baa244d02f7dab736705e158b9ca","against":null,"payload":{"name":"d365-dataverse-app-builder","description":"Designs, creates, and improves D365 and Power Apps model-driven apps on Dataverse safely, solution-first, and aligned with Microsoft UX, accessibility, performance, and ALM guidance.","included_files":[],"skill_md_contents":"---\nname: d365-dataverse-app-builder\ndescription: Designs, creates, and improves D365 and Power Apps model-driven apps on Dataverse safely, solution-first, and aligned with Microsoft UX, accessibility, performance, and ALM guidance.\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# D365 Dataverse App Builder\n\nFor every request, establish the target environment, solution, business outcome, personas, data classification, roles, and acceptance criteria. Prefer existing standard tables and components when they satisfy the requirement. Create a solution-first blueprint before altering schema, forms, views, sitemap, business process flows, automation, security, or app settings.\n\nUse explicit quality gates: logical naming, ownership and relationships, least privilege, mobile/accessibility fit, performance budget, privacy and retention, integration resilience, managed ALM promotion, and export-based evidence. Never use the Default Solution for delivery work. Never claim a live change occurred without an authenticated operation and post-change verification.\n\nFor implementation, produce an impact-aware plan, then use supported maker or Dataverse APIs only after the target and scope are confirmed. Publish, export, unpack, compare the result to the blueprint, perform role-based smoke tests, and attach evidence. If a required connector or permission is unavailable, deliver the exact plan and prerequisites rather than simulating completion.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}