canvas-apps-ui-gen

$ARGUMENTS

• Load the image now (follow Phase 2 exactly)
• Proceed directly to Phase 3 — do NOT ask the mode question
• Mode (Replicate vs Improve) will be determined as part of Phase 3

$ARGUMENTS

• Ask the user exactly this and wait for their answer:

• Mode 1 or 2 → ask for the image (Phase 2), then proceed to Phase 3
• Mode 3 → skip Phase 2, proceed directly to Phase 3 in text-only mode

1. Layout sections: Every distinct UI region (e.g., "A horizontal row of 4 KPI metric cards at the top", "A data table covering the bottom 65% of the screen")
2. Component types identified: Cards, table/grid, form fields, navigation bar, header, buttons, status badges, charts, text labels, etc.
3. Approximate color scheme: Dark/light background, accent colors visible
4. Approximate section proportions: What takes up most of the screen

"I can see the following:

• A left sidebar (~130px wide) with a logo, vertical navigation gallery, and a profile row at the bottom
• A top bar with a page title and breadcrumb (~64px tall)
• A horizontal tab bar with 6 tabs
• A centered form card (~440px wide) with product title, category, brand, variation, and action button fields

Color scheme: light background (warm gray), white sidebar and cards, orange accent for active states."

reference/canvas-apps-limitations.md

Handle:

Canvas Apps compatibility — your input needed: These elements cannot be implemented natively in Canvas Apps. Please choose an alternative for each:

1. [Element detected] — [one-line reason] (a) [Alternative A] (b) [Alternative B] (c) Omit this element

(repeat for each

ask

match)

Canvas Apps compatibility — elements omitted: The following cannot be generated as Canvas Apps YAML and will be excluded from the output:

• [Element]: [brief reason]

Ready to generate — quick questions:

1. What would you like to do with this design? (a) Replicate — recreate this design faithfully as PA YAML (b) Improve — modernize and polish it (standardize spacing/typography, upgrade controls, add proper hover/focus states)

2. Where will you paste this YAML? (a) Into an existing screen — I'll generate controls with no Screen wrapper (b) As a new screen — I'll generate a

Screens:

block with the screen name and all children (c) Just a specific section/component of a screen

3. Classic or Modern (Fluent) controls?

• Classic — minimal base styling, fully customizable; every color, border, font, and interaction state is individually tunable
• Modern / Fluent — Microsoft Fluent 2 design built in; polished look, smooth animations, and accessible defaults

I'll extract the color palette and use the visible field names directly from the image. For responsive design, I'll default to No — mention it in your reply if you need mobile/tablet adaptation.

Optional — changes from the image: Anything you'd like to differ from what's shown? (e.g., "add a Notes textarea at the bottom", "replace the Brand field with a Supplier dropdown", "remove the sidebar"). Leave blank to proceed exactly as shown.

Ready to generate — a few quick questions:

1. Where will you paste this YAML? (a) Into an existing screen — no Screen wrapper (b) As a new screen — full

Screens:

block (c) Just a specific section/component

2. Classic or Modern (Fluent) controls?

• Classic — fully customizable; every property individually tunable
• Modern / Fluent — Fluent 2 design built in; polished defaults

3. What color palette should I use?

• Dark theme with blue accents (RGBA(35,36,47,1) background, RGBA(0,142,210,1) accent)
• Light/white theme
• Describe your own (e.g., "navy and gold", "corporate blue and white")

4. What is the overall layout pattern? (e.g., sidebar + main content, full-width single column, wizard/stepped form, split pane, dashboard with cards)

5. What is the primary purpose of this screen? (e.g., data table/list, data entry form, dashboard with KPIs, record detail view, settings page)

SKILL_DIR

SKILL_DIR

agents/

reference/

templates/

OUTPUT_DIR

pwd

USER_CWD

OUTPUT_DIR = {USER_CWD}/canvas-apps-output

mkdir -p "{USER_CWD}/canvas-apps-output"

USER_CWD

.claude/plugins

"Note: your terminal appears to be inside the Claude plugins directory. Output will be saved to

{OUTPUT_DIR}

. Navigate to your project folder first if you intended otherwise."

SKILL_DIR

OUTPUT_DIR

• User answered (a) Replicate → proceed as replicate mode
• User answered (b) Improve → proceed as improvement mode
• Mode 3 invocation → proceed as text-only mode

MODIFICATIONS

Screen: [ScreenName]
Paste target: [a / b / c]

  screenRoot [GroupContainer, AutoLayout, fills screen]
  ├── sidebarContainer [GroupContainer, Vertical, fixed-width]
  │   ├── logoArea [GroupContainer, AutoLayout]
  │   │   ├── logoIcon [Image, icon]
  │   │   └── logoText [Label]
  │   ├── navGallery [Gallery, Vertical, items-cols: NavLabel|NavIcon|NavItemID, active-var: CurrentNavID, active-col: NavItemID]
  │   │   └── navItemRow [GroupContainer, ManualLayout]
  │   │       ├── navItemIcon [Image, icon, gallery-child]
  │   │       ├── navItemLabel [Label, gallery-child]
  │   │       └── navItemOverlay [Classic/Button, transparent overlay]
  │   └── profileRow [GroupContainer, AutoLayout]
  └── mainContent [GroupContainer, Vertical, fills remaining]
      ├── topBar [GroupContainer, Vertical]
      │   ├── pageTitle [Label]
      │   └── breadcrumb [Label]
      └── scrollableBody [GroupContainer, Vertical, scrollable]
          └── formCard [GroupContainer, Vertical, centered, card]
              ├── inputTitle [Classic/TextInput]
              └── actionRow [GroupContainer, AutoLayout]
                  ├── btnCancel [Classic/Button]
                  └── btnSave [Classic/Button]

transparent overlay

icon

gallery-child

scrollable

centered

card

• items-cols: A|B|C

  — the exact column names the controls-agent must use in the

  Table()

  . Derive names from the gallery's semantic purpose:
  • Nav/sidebar gallery →

    NavLabel|NavIcon|NavItemID

  • Tab gallery →

    TabLabel|TabID

  • Data-table row gallery → column names matching the visible fields in the design (e.g.,

    OrderName|Status|Amount|OrderID

    )
  • Simple list gallery →

    ItemLabel|ItemID

• active-var: CurrentX

  — the global variable name that tracks the selected item. Always use the

  Current

  prefix (never

  var

  ), followed by a semantic noun:

  CurrentNavID

  ,

  CurrentTabID

  ,

  CurrentOrderID

  . This variable is initialized in

  OnVisible

  and set in the overlay button's

  OnSelect

  .

• active-col: X

  — the column from

  items-cols

  that is compared against

  active-var

  to determine the active/selected state. This is always the ID/key column.

navGallery [Gallery, Vertical, items-cols: NavLabel|NavIcon|NavItemID, active-var: CurrentNavID, active-col: NavItemID]

reference/design-spec-formats.md

• Replicate mode → ## Replicate Mode section
• Improvement mode → ## Improvement Mode section
• Text-only mode → ## Text-Only Mode section

• Palette: Commit to exactly 7 RGBA values. Derive from the user's described purpose or screen context (e.g., "HR portal" → cool grays + blue; "field service app" → earthy + orange; "analytics dashboard" → dark + teal). Background and Surface must differ by at least 4 lightness points. Leave Accent-Secondary blank if only one accent is needed. Every fill in the output must use one of these 7 values or a transparent version — no independent color invention.
• Typography: Pick ONE font family for the entire screen. Do not mix fonts. Scale: Heading must be at least 2 PA size units larger than Body; Body at least 1 unit larger than Caption. Default (Classic controls, nothing suggesting otherwise): Heading=14, Body=11, Caption=9. For Modern controls, apply the Classic→Modern size conversion from

  reference/sizing-reference.md

  .
• Density: Infer from layout type:
  • Data tables / lists → compact: LayoutGap=8, PaddingH=12, PaddingV=8
  • Forms / record detail views → balanced: LayoutGap=12, PaddingH=16, PaddingV=12
  • Dashboards / landing pages → generous: LayoutGap=16, PaddingH=20, PaddingV=16
• Radius: Pick one value for containers (0=sharp, 4=slight, 6=standard, 8=rounded, 12=soft). Interactive controls get the same value or half — never more. Default: Container=6, Interactive=4.
• State Colors: All derived from Accent-Primary:
  • HoverFill: RGBA(accent_r, accent_g, accent_b, 0.08)
  • PressedFill: RGBA(accent_r, accent_g, accent_b, 0.15)
  • FocusedBorder: Accent-Primary at full opacity
  • DisabledFill: near-background (very low contrast)
  • DisabledColor: Text-Secondary at 0.38 opacity

{OUTPUT_DIR}/temp-design-spec.md

reference/controls-index.md

agents/

• agents/layout-sizing-agent.md

• agents/controls-agent.md

• agents/styling-agent.md

• The full content of its instruction file (as the task description)
• The absolute path to

  {OUTPUT_DIR}/temp-skeleton.md

• The absolute path to

  {OUTPUT_DIR}/temp-design-spec.md

• SKILL_DIR

  (the skill directory absolute path, for reading reference docs in

  reference/

  )
• The control style preference (classic / modern) from the user's Phase 3 answer — pass this explicitly to the controls-agent so it selects the correct variants
• The absolute path to its output file:
  • Layout+Sizing →

    {OUTPUT_DIR}/temp-layout-annotations.yaml

  • Controls →

    {OUTPUT_DIR}/temp-controls-annotations.yaml

  • Styling →

    {OUTPUT_DIR}/temp-styling-annotations.yaml

agents/assembly-agent.md

• The full content of

  agents/assembly-agent.md

• Absolute paths to:

  {OUTPUT_DIR}/temp-skeleton.md

  ,

  {OUTPUT_DIR}/temp-layout-annotations.yaml

  ,

  {OUTPUT_DIR}/temp-controls-annotations.yaml

  ,

  {OUTPUT_DIR}/temp-styling-annotations.yaml

• Absolute path to

  {OUTPUT_DIR}/temp-design-spec.md

  (needed for QA fidelity checks)

• SKILL_DIR

  (the skill directory absolute path, for reading

  reference/controls-reference.md

  during QA)
• Paste target (a, b, or c) and the screen name
• The output filename: determine a unique filename first using

  Glob

  on

  {OUTPUT_DIR}/[ScreenName]-*-generated.yaml

  . If

  {OUTPUT_DIR}/[ScreenName]-1-generated.yaml

  exists, use

  -2-

  , and so on.
• Data binding instructions (inline for paste target b; separate block for a and c)
• Responsive design flag (if user mentioned responsive in their Phase 3 reply) with screen name for

  ScreenName.Size

  formulas

• {OUTPUT_DIR}/temp-skeleton.md

• {OUTPUT_DIR}/temp-design-spec.md

• {OUTPUT_DIR}/temp-layout-annotations.yaml

• {OUTPUT_DIR}/temp-controls-annotations.yaml

• {OUTPUT_DIR}/temp-styling-annotations.yaml

Your YAML is ready: Your file has been saved to

{OUTPUT_DIR}/[ScreenName-N-generated.yaml]

. Open it in your editor, press Ctrl+A then Ctrl+C to copy everything, then paste into Power Apps Studio.

• (a) or (c): "In PA Studio: open the tree view, right-click the target screen or container, and select Paste code."
• (b) new screen: "In PA Studio: right-click in the screen list panel and choose Paste code. If unavailable, create a blank screen (Insert → New Screen → Blank), right-click it in the tree view, select Paste code, and paste only the content under

  Children:

  . Then copy the

  OnVisible

  formula into the screen's

  OnVisible

  property."

LayoutMinWidth

=Parent.Width

[ScreenName].Size

ONVISIBLE_BLOCK

Also paste this into your screen's

OnVisible

property:

[formula from ONVISIBLE_BLOCK]

yaml

QA warnings (non-blocking):

• [warning text]

Handle: auto

Substitutions applied automatically:

• [Original element] → [Canvas Apps alternative used]

auto

1. Write a preview to

   output/staging-[name].yaml

   inside the skill directory
2. Tell the user to paste the preview into Power Apps Studio and verify it renders correctly
3. Wait for the user to confirm the preview works
4. Promote: move the validated file to

   templates/[name].yaml

   inside the skill directory, and delete the staging file from

   output/

1. Read

   reference/pa-yaml-rules.md

   before generating the Skeleton — it contains the exact format rules, sizing strategies, and valid control types.
2. Read

   reference/controls-reference.md

   for valid property names and enum values.
3. Never use

   context: fork

   on this skill itself — it must remain conversational to access pasted images. However, the Agent tool IS used within Phase 4 to spawn specialist workers. Those workers receive the pre-analyzed skeleton and design spec as text — they do not need access to the original image.
4. Never write files unless the user explicitly confirms (e.g., saving a new template). The temp files in Phase 4 are internal working files — these are fine.
5. Never expose real data source names or connection strings in generated YAML.
6. Version self-healing: If the user reports a PA2105 warning for any control, immediately update that control's

   @version

   everywhere it appears: the VALID CONTROL TYPES table in

   reference/pa-yaml-rules.md

   , all code examples in

   reference/pa-yaml-rules.md

   , the section heading in

   reference/controls-reference.md

   , and every

   .yaml

   file in

   templates/

   . Use the version number PA reports as current. The same PA2105 warning must never occur twice for the same control.
7. Never use

   Control: Screen

   — this causes PA2101. For new screens always use the

   Screens:

   top-level format documented in Phase 4 Step 3 and in

   reference/controls-reference.md

   .
8. Control fidelity — never substitute an inferior control. Always use the correct semantic control for the UI element. Use

   reference/controls-index.md

   to identify the right control. Version uncertainty is not a reason to substitute.
9. Before using

   TextInput@0.0.54

   ,

   ComboBox@0.0.51

   , or

   Radio@0.0.25

   : Check whether you need

   Default

   (TextInput/Radio) or

   SearchFields

   (ComboBox). If yes, use the Classic variant instead. Never add these properties to the previous-gen controls — they cause PA2108.
10. Never mix Classic and Modern control properties. Always look up properties in

    reference/controls-reference.md

    under the exact control type you are using.
11. No emojis or em dashes in generated text values — never use emojis or em dashes (—) in any

    Text

    ,

    HintText

    ,

    Placeholder

    ,

    TrueText

    ,

    FalseText

    ,

    Tooltip

    , or any other string property on a control, unless the user's source image explicitly contains them or the user explicitly requests them.
12. Always use custom SVG icons — never

    Classic/Icon@2.5.0

    . For every icon, use

    Image@2.2.3

    with an inline SVG. The

    Classic/Icon

    control must never appear in generated YAML.
13. Output token budget — always stay within 32 000 tokens per response. Write YAML to file first (Phase 4 Step 4), then apply the code-block size guard (400 lines threshold).
14. HtmlText is display-only — never code interactions on it. For any hyperlink or clickable link, use

    Classic/Button@2.2.0

    (or a Modern button) with

    OnSelect: =Launch("<url>")

    . Style it as a text-only button (no fill/border) to visually match a link. Never use

    <a>

    tags inside HtmlText as an interaction mechanism.
15. Never use

    Variant: GridLayout

    on

    GroupContainer

    . Use only

    Variant: AutoLayout

    or

    Variant: ManualLayout

    for

    GroupContainer@1.5.0

    . Direction must be expressed with

    LayoutDirection

    .