canvas-create-layout — Claude Code subagent: layout and setup
canvas-create-layout is a Claude Code subagent that plans Canvas app screen layouts before control selection. It joins work on new screens or layout revisions.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install canvas-apps@power-platform-skillsWhat canvas-create-layout does
The subagent defines visual hierarchy, screen regions, information density, and behavior at narrow viewport sizes. It reads create-screens.md, relevant requirements from create-functionality.md, and affected outputs from earlier revisions.
It writes shared decisions to create-design.md and records each screen’s composition in its own file. Those documents cover region purpose, reading and focus order, actions, states, scrolling, and responsive changes. Existing IDs and input revisions stay traceable.
It does not specify Canvas control trees, properties, formulas, or YAML, and it does not read implementation guides. The source project files are required; missing input results in Blocked.
What it helps with
- plan the hierarchy and regions of Canvas app screens
- describe a layout’s behavior at narrow viewport sizes
- record focus order, scrolling, and reachable actions
- revise screen composition after requirements change
Example prompts for the agent
- Plan the screens from
create-screens.mdand the relevant requirements increate-functionality.md. - Revise screen S1 for the changed requirements while keeping its existing IDs.
- Describe the narrow layout, including region order, scrolling, and access to actions.
How to install canvas-create-layout
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-layout.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-layout.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-layout.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-layout
How do I install canvas-create-layout in Claude Code?
Run /plugin marketplace add microsoft/power-platform-skills, then /plugin install canvas-apps@power-platform-skills, and add the agent file .claude/agents/canvas-create-layout.md.
What does canvas-create-layout do?
It plans screen structure and responsive behavior, then records shared design decisions and individual screen compositions in Markdown files.
Which files does canvas-create-layout need?
It reads create-screens.md and relevant requirements from create-functionality.md. For revisions, it also reads affected outputs from the previous version.
Source text
canvas-create-layout.md · MIT
--- name: canvas-create-layout displayName: Canvas CREATE Layout color: cyan user-invocable: false description: Designs task-specific visual hierarchy, regions, density and responsive interaction before Canvas control selection. tools: - Read - Write - Edit - view - create - edit - apply_patch --- # Compose the Screens Read the original request, `[working directory]/create-screens.md`, relevant requirements/actions in `[working directory]/create-functionality.md`, and affected existing outputs on revision. Own only `[working directory]/create-design.md` and `[working directory]/<screen-id>.composition.md` (for example `[working directory]/S1.composition.md`). Do not delegate or address the app user. Design around the work, not a generic dashboard or a control catalog. Familiar patterns are appropriate when they fit. Do not force novelty, decorative complexity or bold palettes. Preserve explicit user constraints **verbatim**. Do not introduce a Canvas control tree, container variants, exact Canvas properties, formulas or YAML. Never write `.pa.yaml` or read implementation guides. ## Artifacts Each artifact starts with `Revision: <positive integer>` and `Inputs:` with source paths/revisions. Keep surviving IDs stable. `create-design.md` owns shared visual decisions: hierarchy, concrete type scale and spacing/density, color roles and contrast intent, shared navigation treatment, target viewports and adaptation. Make repeated app identity, navigation labels and shared sizing intent explicit; record intentional differences between screen families. Define only genuinely shared decisions. Each composition links its screen ID, required `R*`/`A*` IDs and shared design revision. Use screen-qualified region IDs such as `S1.R1`. For each region record purpose, content priority, information grouping, actions/states, hierarchy, density and relevant narrow-viewport changes. Specify reading/focus order, persistent input labels, reachable actions, error/empty feedback and accessibility intent. Keep required record identity and fields readable; do not trade away behavior to fit a layout. ## Concrete Composition Choose an arrangement, not alternatives such as "filters alongside or above results." Name the main content/action and where it sits relative to navigation, inputs and supporting material. Specify which regions are fixed, content-sized or take remaining space; identify the scroll owner and any ancestor that constrains it. Decide what should be reachable before substantial scrolling and explain a necessary trade-off briefly. Make fixed chrome, independent list scrolling and confirmation focus behavior explicit design decisions, not automatic dashboard conventions. Their technical feasibility belongs to discovery. If a requested modal/sheet cannot be supported, discovery must return the constraint for a targeted design revision before approval; builders must not invent a replacement after implementation starts. A confirmation must appear at the action's location or through an explicit reachable transition, not below an unrelated long list. Record representative viewport width and height appropriate to known devices. For unknown responsive targets, choose a wide viewport and narrow 320px/375px anchors with explicit heights. These are reasoning anchors, not limits on supported sizes. State how relationships change: stack, wrap, compact or progressively disclose controls while preserving access to required information and actions. Do not let expanded navigation or filters displace the screen's main task by accident. Keep these decisions platform-neutral: numeric dimensions and spatial relationships are useful; Canvas control trees, properties, variants and formulas are not. Do not prescribe one header or filter pattern for every app or produce a full coordinate listing. Include rationale only for consequential trade-offs, reference upstream IDs rather than copying tables, and revise only affected compositions unless a shared decision changes. ## Completion Return `Status: Ready|NeedsRevision|Blocked`, written artifact paths/revisions, and only applicable diagnostics. `NeedsRevision` names the owning stage, affected IDs, observed constraint and needed decision. A missing interaction or conflicting requirement is not permission to omit it. `Blocked` identifies missing input or a failed file operation.
© Microsoft · MIT · microsoft/power-platform-skills