power-apps-components

Builds reusable Power Apps canvas components, responsive layouts, and HtmlText-rendered rich content.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill power-apps-components-rorysullivan1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: power-apps-components
Source: https://github.com/RorySullivan1/powerapp_taskmaster/tree/main/.claude/skills/power-apps-components
Command: npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill power-apps-components-rorysullivan1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Canvas Power Apps often suffer from copy-pasted control clusters, absolute X/Y layouts that break on resize, and formatting needs that native Labels cannot express. This Skill guides the creation of reusable components with typed custom properties, responsive container-based layouts, and rich HTML content rendered through the HtmlText control. ## Core Features & Use Cases - Reusable components with typed contracts: Define Data, Function, Behavior/Action, and Event custom properties so components expose clean inputs and outputs, and share them across apps via component libraries. - Responsive layouts with containers: Replace absolute coordinates with Horizontal/Vertical containers, FillPortions, and Parent.Width/Parent.Height formulas so screens reflow across sizes. - Rich content via HtmlText: Render tables, badges, and inline-styled markup in Power Fx with the restricted HTML subset, using EncodeHTML for untrusted data. - Use Case: You need the same KPI card on five dashboards. Build a StatCard component with Label, Value, AccentColor, and Trend input properties plus an OnCardSelect event, then reuse it across screens and propagate updates through a component library. ## Quick Start Ask the assistant to create a reusable Power Apps component with typed input and output properties, or to convert an absolute-positioned screen into a responsive container layout.

Frequently Asked Questions about power-apps-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a reusable component in Power Apps?▼

Create a component and define its contract with custom properties: Data inputs and outputs, Function properties for pure logic, and Behavior or Event properties for side effects. Controls inside size to Parent.Width and Parent.Height so the component resizes with each instance.

How do I share Power Apps components across multiple apps?▼

Publish the component in a component library, then consume it in other apps via Insert, Get more components, Library. After editing and republishing, consuming apps see an update banner and choose when to pull the new version.

Can I put a Power Apps component inside a gallery or form?▼

No, Power Apps does not allow inserting a component into a gallery or a form, including SharePoint forms. Build per-row visuals from plain controls like Image, Label, or Rectangle inlined in the gallery template instead.

Why does my responsive Power Apps layout break after dragging controls?▼

Dragging or resizing a control in the canvas overwrites X, Y, Width, and Height formulas with constants. Once sizing uses Parent.Width or container FillPortions, adjust positions only through the formula bar to preserve responsiveness.

What HTML does the Power Apps HtmlText control support?▼

HtmlText renders a restricted HTML subset with inline styles only; script, style, and object tags are stripped and onclick does not run. Lists need explicit inline styling, and any data-sourced text should be wrapped in EncodeHTML to prevent broken markup.

Why can't I use UpdateContext inside a Power Apps component?▼

Components are isolated and do not support UpdateContext. Use Set instead, which creates variables scoped to the component instance, and surface any state the app needs through an Output property.