Run, diagnose, and iterate on Power Apps Component Framework (PCF) controls locally with the PCF Workbench harness. Replaces `pcf-scripts start` with a richer dev loop: gallery discovery, device emulation, network conditioning, WebAPI mocking from data.json, scenarios, lifecycle/leak tracking, and a headless build→render→report loop for AI-assisted iteration. ALWAYS use this skill for ANY PCF development work (alongside the pcf-engineer skill for code authoring/review) — the headless loop is the acceptance gate after any non-trivial code change. TRIGGER: PCF, PCF control, PCF component, Power Apps Component Framework, code component, PCF Workbench, pcfworkbench, run pcf, test pcf locally, harness, pcf gallery, pcf loop, debug pcf control, pcf-scripts start replacement, build pcf, validate pcf, ControlManifest.
Senior PCF engineer for Power Apps Component Framework. Use when creating, reviewing, or debugging PCF controls. Aligned with official Microsoft best-practices and limitations guidance. Covers lifecycle, manifest, testing, CSS scoping, performance, accessibility, async loading UX, large-target interaction patterns, multi-host support, and mobile constraints. ALWAYS use this skill for ANY PCF development work (alongside the pcf-workbench skill for local run/test). TRIGGER: PCF, PCF control, PCF component, Power Apps component, Power Apps Component Framework, component framework, code component, ControlManifest, updateView, init, destroy, pac pcf, pcf-scripts, virtual control, dataset control, field control.