What problem does it solve?
Building a Power Apps Component Framework (PCF) control that correctly dispatches to a third-party native module inside a wrapped mobile app requires precise knowledge of the host bridge contract, manifest schema, and property usage rules — mistakes cause silent on-device failures. This Skill scaffolds the entire companion PCF correctly from the committed manifest.json and PRD.
Core Features & Use Cases
- PCF scaffolding: Runs
pac pcf init with the field template and vanilla DOM framework, then rewrites ControlManifest.Input.xml with human-readable labels and correct bound/input/output property usage.
- Bridge contract wiring: Generates index.ts that dispatches the composite key
<name>/<receiver> through window.PowerApps.NativeExtension.sendAsync with an extractResponse helper that unwraps the wrap host's nested response container.
- Diagnostics built in: Emits Status, ErrorCode, ErrorMessage outputs plus a raw-response bound property so failures are visible in Power Fx without a native debugger.
- Use Case: After generating a native extension module for a wrapped Power Apps mobile app, run this Skill to produce the Canvas Studio control that triggers the native operation and surfaces its result, validated by
npm run build.
Quick Start
Ask the agent to run /generate-pcf-companion to scaffold the dispatcher PCF for the native module already present in the repository.