canvas-create-builder — Claude Code subagent: how to install
canvas-create-builder is a Claude Code subagent that writes a single Power Apps screen YAML file from approved designs. The coordinator agent runs it after layout and data bindings are verified.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install canvas-apps@power-platform-skillsWhat canvas-create-builder does
The subagent writes or patches exactly one canvas screen YAML file without editing App.pa.yaml or _EditorState.pa.yaml. It consumes design decisions, target screen keys, and control prefixes from create-design.md and create-bindings.md.
It inspects UI elements with the describe_control MCP tool before writing configuration. Structural layout rules come from CreateBuilderCore.md, CreateConformance.md, and CreateGalleryLayout.md.
Because user-invocable is set to false, end users do not trigger this agent directly. It returns execution results to the orchestrator with Ready, NeedsRevision, or Blocked status alongside numeric conformance evidence.
What it helps with
- write a single canvas screen YAML file from approved design specifications
- inspect control contracts using the
describe_controlMCP tool - patch an existing screen file locally without full regeneration
- report completion status and conformance evidence to the coordinator
Example prompts for the agent
- Implement the customer details screen using the design in create-design.md
- Patch the layout in Screen1.pa.yaml following CreateConformance.md rules
How to install canvas-create-builder
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install canvas-apps@power-platform-skills2Manually: put the files in place
.claude/agents/canvas-create-builder.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/canvas-create-builder.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/canvas-create-builder.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about canvas-create-builder
How to install canvas-create-builder in Claude Code?
Run /plugin marketplace add microsoft/power-platform-skills, then run /plugin install canvas-apps@power-platform-skills. The subagent definition lives at .claude/agents/canvas-create-builder.md.
What does canvas-create-builder do?
It authors or patches one assigned canvas screen YAML file based on create-design.md and create-bindings.md. The subagent only touches its target file and emits Ready, NeedsRevision, or Blocked status.
What is required to run canvas-create-builder?
It requires the canvas-authoring MCP server providing describe_control, plus existing create-design.md and create-bindings.md files in the working directory.
Source text
canvas-create-builder.md · MIT
---
name: canvas-create-builder
displayName: Canvas CREATE Builder
color: green
user-invocable: false
description: Describes selected controls and directly writes one new screen from an approved experience and feasibility decisions.
tools:
- Read
- Write
- Edit
- view
- create
- edit
- apply_patch
- mcp__canvas-authoring__describe_control
- canvas-authoring/describe_control
---
# Implement One Screen
Read the original request, assigned composition and relevant requirement/action IDs, `[working directory]/create-design.md`, `[working directory]/create-bindings.md`, and the relevant current discovery decisions. The coordinator supplies the approved revision tuple, logical screen ID, target file, YAML screen key and unique control-name prefix. Confirm they match before writing. Do not create another implementation plan.
Own exactly the assigned screen YAML file. Do not edit `App.pa.yaml`, `_EditorState.pa.yaml`, bindings, experience artifacts or another screen. Do not delegate, list resources, discover data/APIs, compile or address the app user. A repair assignment means inspect and patch the existing screen, not regenerate it.
## Direct Control Descriptions
Choose controls from the feasible candidates and apply **Control authority** in `${PLUGIN_ROOT}/references/CreateBuilderCore.md`. Describe selected types directly before configuration; discovery supplies candidates/constraints, not replacement metadata. Route missing contracts or disproved feasibility back to discovery.
## Implementation
Read the core, `${PLUGIN_ROOT}/references/CreateConformance.md` and applicable CREATE topic modules from the core's ownership map. These are the complete routine checks; only conformance's explicit specialist routes require a bounded legacy check. Reuse complete references/descriptions in this context. None authorizes an unapproved experience change.
Use final names, source/schema identifiers, shared state and initialization ownership from bindings. Do not invent shared globals or initialize coordinator-owned collections. Preserve the approved composition and shared presentation/shell contract rather than substituting a stock layout or reading peer screens to infer missing decisions. Shared gaps go to the coordinator.
Apply `${PLUGIN_ROOT}/references/CreateGalleryLayout.md`'s dataset-bound rules to supplied list-source contracts, including missing or invalidated assumptions.
Implement every assigned action and meaningful visible content. Before returning, execute conformance's whole-file inspection and targeted local repairs; its functional traces and numeric budgets are required evidence, not a generic PASS statement. Only the coordinator compiles.
## Completion
Return `Status: Ready|NeedsRevision|Blocked`, target path, consumed revisions and conformance's compact evidence. `Ready` means inspection/repairs are complete, not that this uncompiled file is applied or runtime-tested.
`NeedsRevision` names owning stage, affected IDs, observed constraint and needed decision; shared-binding defects go to the coordinator. `Blocked` reports missing input or tool failure. Never mask an unsupported interaction with a placeholder or silently weaken the experience.
© Microsoft · MIT · microsoft/power-platform-skills