agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/canvas-apps/SKILL.md

canvas-apps

Skill46 starsChanged 8 months agoMITView on GitHub

Canvas Apps Development with Power Fx. Use when: building Canvas Apps, Power Fx formulas, delegation patterns, component libraries, responsive Canvas layout, offline capabilities, modern controls, named formulas, Canvas App ALM.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Live property for dynamic content updates (screen reader announcements)

    line 78
  2. Distinctive:

    Ensure all functionality accessible via keyboard

    line 80
  3. Distinctive:

    Use the Accessibility Checker in Power Apps Studio: App checker → Accessibility

    line 81
  4. Distinctive:

    Not implementing error handling on form submissions

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Canvas Apps Development

When to Use

Trigger when building, reviewing, or debugging Canvas Apps — low-code Power Apps built with Power Fx formulas, connectors, and drag-and-drop controls for mobile, tablet, and web scenarios.


AI Accuracy Warning

LLMs produce less accurate Power Fx than mainstream languages (JavaScript, C#, Python) due to smaller training datasets. Always verify AI-generated Power Fx formulas — especially complex ones involving delegation, ThisItem/ThisRecord, concurrent collections, or nested If/Switch logic. Use Power Apps Test Engine to validate formulas before promoting to production.


When to Use Canvas Apps vs Alternatives

ScenarioBest ChoiceWhy
Standard Dataverse CRUD + business processModel-Driven AppBuilt-in forms, views, business rules
Custom pixel-perfect UI + pro-dev teamCode AppFull React/TypeScript control
Mobile-first field appCanvas AppPower Apps mobile, offline, camera, GPS
SharePoint list frontendCanvas AppSharePoint form customization
Multi-data-source mashupCanvas App1000+ connectors
Quick internal tool / formCanvas AppFastest time-to-value
Citizen developer / makerCanvas AppLow-code, no TypeScript needed
Complex interactive dashboardsCode AppBetter performance, charting libraries

⚠️ REQUIRED: Load Sub-Files Before Implementation

SKILL.md is a summary only — it is NOT sufficient for implementation.

The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:

  • Power Fx Fundamentals — data types, core functions (CRUD, navigation, variables), named formulas, UDFs
  • Delegation — delegable vs non-delegable functions, limits, warning patterns, workarounds
  • Components & Modern Controls — component library, property types, Fluent 2 modern controls, theming
  • Screen Patterns & Responsive Design — master-detail, loading pattern, container layout, phone vs tablet
  • Offline Capabilities — LoadData/SaveData, connectivity check, offline queue + sync pattern
  • Connectors, Data Sources & Integration — connector types, Dataverse/SharePoint patterns, Power Automate integration, environment variables
  • Canvas ALM — solution-aware development, source control (pac canvas unpack/pack), co-authoring
  • Performance & Error Handling — Concurrent loading, optimization do's/don'ts, form validation, IfError
  • Power Fx Function Reference — Complete function reference by category: Text, Math, Date/Time, Logical, Table, Collection, Behavior, JSON, Environment
  • Power Fx Operators Reference — Arithmetic, comparison, logical, membership (in/exactin), scope (ThisItem/Self/Parent/As/@), chaining, type operators, precedence
  • Controls Reference — Top 15 Canvas controls (Gallery, EditForm, TextInput, ComboBox, Button, etc.) with key properties, events, patterns, modern vs classic differences

Naming Conventions

ObjectConventionExample
Screens[Feature]ScreenContactBrowseScreen, ContactDetailScreen
Galleriesgal[Name]galContacts, galOrders
Buttonsbtn[Action]btnSave, btnDelete, btnRefresh
Text Inputstxt[Field]txtFirstName, txtSearchQuery
Dropdownsdrp[Field]drpStatus, drpPriority
Labelslbl[Purpose]lblTitle, lblErrorMessage
Iconsico[Purpose]icoSearch, icoClose
Formsfrm[Entity]frmContact, frmOrder
Containerscon[Purpose]conHeader, conSidebar
Global variablesgbl[Name]gblUserName, gblIsAdmin
Context variablesloc[Name]locIsEditing, locErrorMsg
Collectionscol[Name]colContacts, colPendingChanges
Flowsflow[Action]flowProcessOrder, flowSendNotification
Componentscmp[Name]cmpStatusBadge, cmpSearchBar
Component librarieslib[Name]libSharedControls

Accessibility in Canvas Apps

  • Set AccessibleLabel on every control
  • Set TabIndex for logical tab order (0 for interactive, -1 to skip)
  • Use Live property for dynamic content updates (screen reader announcements)
  • Provide sufficient color contrast (4.5:1 for text)
  • Ensure all functionality accessible via keyboard
  • Use the Accessibility Checker in Power Apps Studio: App checker → Accessibility

Anti-Patterns

  • Building Canvas Apps outside of solutions ("My Apps")
  • Direct connections instead of connection references
  • Hardcoded GUIDs or environment URLs
  • Loading entire tables without Filter or $top
  • Ignoring delegation warnings (blue underline in formula bar)
  • Using Set for table data instead of ClearCollect
  • Nesting ForAll with Patch for bulk operations
  • Using OnStart for heavy data loading without Concurrent
  • Naming controls with default names (Button1, Label4, Gallery3)
  • Not implementing error handling on form submissions
  • Using Navigate without Back() support (no way to return)
  • Embedding sensitive values in formulas (visible in .msapp file)
  • Using the Dynamics 365 connector (deprecated) — use the native Microsoft Dataverse connector instead
  • Using the Dataverse (legacy) connector — use the current Microsoft Dataverse connector

Related Skills

  • dataverse — Table design and data modeling for Canvas App data sources
  • power-automate — Cloud flows triggered from Canvas Apps
  • testing — Canvas App testing strategies
  • accessibility-ux — WCAG compliance in Canvas Apps

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.