powerplatform-core

Use for Power Apps Code Apps - the pro-code model where a standalone Vite-built React/Vue/TS single-page app uses the `@microsoft/power-apps` client library and is pushed into a Power Platform environment with no server to manage. Covers scaffolding from the official Vite template, initializing with `power.config.json`, adding Dataverse data sources that generate typed model/service files, local dev, building, and pushing via `npx power-apps push` (npm CLI) or legacy `pac code push`. Trigger whenever the user mentions a code app, `power.config.json`, `@microsoft/power-apps`, `pac code` / `power-apps` CLI, a `CodeApp/` folder, or wants to build, run, or push a custom SPA into Power Platform, even if no helper is named. Not for PCF controls embedded in model-driven forms (use pcf-and-web-resources) or Canvas/maker apps.

Use to DESIGN Power Platform custom connectors and integration wrappers - review an OpenAPI/Swagger description, choose the auth shape (API key, OAuth2, basic, none), inventory operations, and decide whether to expose an API as a direct custom connector or behind an Azure Function / API facade. Produces a connector name, auth approach, operation summaries, a recommended pattern, suggested environment variables, and solution-aware connection-reference guidance. Trigger whenever the user mentions a custom connector, OpenAPI/Swagger for Power Platform, connecting a flow or app to an external/REST API, an integration wrapper or facade, or whether an Azure Function should front an integration, even if no helper is named. Design-first - it does not publish the connector. Not for authoring the flow that calls it (use power-automate-flows) or server-side Dataverse logic (use plugins-server-extensions).

Use for Dataverse row/record DATA and query design - create, update, or upsert rows, seed or sync reference/config data, and design queries. Trigger on "create a record/row", "update this record", "upsert by alternate key", "seed config data", "import/sync these rows", "set a field value on a row", "design an OData / FetchXML query", or "build the List rows filter for a flow", even when no helper is named. Covers keyed create/update/upsert via SDK or Web API and query design across OData, FetchXML, and Power Automate "List rows". Not for table/column/form/ view/ribbon METADATA - use dataverse-schema.

Use for Dataverse table METADATA - tables, columns, lookups/relationships, choices/option sets, alternate keys, main forms, public/lookup views, the form-level ribbon (RibbonDiffXml), form event handlers and script libraries, and table icons - plus up-front schema and query-shape design before metadata exists. Trigger on "create a table", "add a column/field", "add a lookup", "add a choice", "set an alternate key", "update the main form", "add a view / change view columns", "add a button to the form ribbon", "set the table icon", or "design a Dataverse schema", even when no helper is named. Prefer this over hand-edited customizations.xml. Not for row/record DATA, seeding config rows, or query authoring - use data-operations.

Use for Dataverse document generation built on Word Templates - inventory the content controls in a `.docx`/`.dotx` template, map placeholders to data, and plan a template-aware change before editing blindly. Fires whenever the user mentions a Word Template, document generation, content controls, placeholder or merge-field mapping, document-definition records, "why is this field blank in the generated doc", "add a placeholder to the template", "what tags does this template use", or a document-generation plug-in, even if no helper is named. Treats `Word Templates/` as first-class source, surfaces duplicate tags, missing required placeholders, and unused controls, and points at the `*.Business`, `*.Plugins`, and `*.Data` touchpoints a placeholder change implies. Run the live-mutation preflight from the `powerplatform-core` orchestrator before any live template or component write.