# pcf-manifest-schema

A rule that feeds Copilot the structure of ControlManifest.Input.xml: which elements and attributes exist and what they do. Useful when editing a PCF component manifest.

- rule · `type=rule` · GitHub Copilot · ★ 40418
- Author: github · official GitHub repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/github/awesome-copilot/tree/HEAD/instructions/pcf-manifest-schema.instructions.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/rules/pcf-manifest-schema

## What it does

The rule fires on `**/*.xml` files. Inside is a walkthrough of the manifest: the root `manifest`, the `code` and `control` elements, `property` and `type-group`, `data-set` for tabular data, the `resources` container with `css`, `img` and `resx`, feature declarations via `uses-feature`, dependencies, `platform-library` entries for React and Fluent UI, events, and `platform-action`. Each element comes with its attributes and the platforms where it is available.

A full example manifest sits at the end: a control with version and localization keys, a property using `of-type`, a type group holding `Whole.None` and `Currency`, a dataset, an event, resources, and feature declarations such as `WebAPI` and `Device.captureImage`. There is a validation section too — the schema is checked at build time, a missing required element breaks the build, and you can validate the structure with `pac pcf` commands.

It advises resource keys over hardcoded strings and declaring every feature the component uses. One catch: the rule is scoped to XML, so it stays quiet in your TypeScript implementation files.

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/instructions/pcf-manifest-schema.instructions.md` — The applyTo field sets which files it applies to

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/pcf-manifest-schema.md` — The paths frontmatter field limits the files: move applyTo from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### Cursor

**Manually: put the files in place**
- File: `.cursor/rules/pcf-manifest-schema.mdc` — Frontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/pcf-manifest-schema.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/pcf-manifest-schema.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/github/awesome-copilot/tree/HEAD/instructions/pcf-manifest-schema.instructions.md

## When to use it
- recall which attributes a `property` element takes
- define a property that accepts several types via `type-group`
- wire up React and Fluent UI as `platform-library`
- declare device features in `feature-usage`
- validate the manifest before a build fails on it

## Example prompts
- add a property to ControlManifest.Input.xml that accepts Whole.None and Currency
- explain what the resx tag does and how it ties to display-name-key
- check my manifest: are all required elements there?

## Source text · pcf-manifest-schema.instructions.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 8c6e9e12866526e5.

BEGIN THIRD-PARTY FILE 8c6e9e12866526e5
```text
---
description: 'Complete manifest schema reference for PCF components with all available XML elements'
applyTo: '**/*.xml'
---

# Manifest Schema Reference

The manifest file (`ControlManifest.Input.xml`) is a metadata document that defines your code component. This reference lists all available manifest elements and their purposes.

## Root Element

### manifest

The root element that contains the entire component definition.

## Core Elements

### code

Refers to the resource file that implements the component logic.

**Attributes:**
- `path`: Path to the TypeScript/JavaScript implementation file
- `order`: Loading order (typically "1")

**Availability:** Model-driven apps, canvas apps, portals

### control

Defines the component itself, including namespace, version, and display information.

**Key Attributes:**
- `namespace`: Namespace for the component
- `constructor`: Constructor name
- `version`: Semantic version (e.g., "1.0.0")
- `display-name-key`: Resource key for display name
- `description-key`: Resource key for description
- `control-type`: Type of control ("standard" or "virtual")

**Availability:** Model-driven apps, canvas apps, portals

## Property Elements

### property

Defines an input or output property for the component.

**Key Attributes:**
- `name`: Property name
- `display-name-key`: Resource key for display name
- `description-key`: Resource key for description
- `of-type`: Data type (e.g., "SingleLine.Text", "Whole.None", "TwoOptions", "DateAndTime.DateOnly")
- `usage`: Property usage ("bound" or "input")
- `required`: Whether property is required (true/false)
- `of-type-group`: Reference to a type-group
- `default-value`: Default value for the property

**Availability:** Model-driven apps, canvas apps, portals

### type-group

Defines a group of types that a property can accept.

**Usage:** Allows a property to accept multiple data types

**Availability:** Model-driven apps, canvas apps, portals

## Data Set Elements

### data-set

Defines a dataset property for working with tabular data.

**Key Attributes:**
- `name`: Dataset name
- `display-name-key`: Resource key for display name
- `description-key`: Resource key for description

**Availability:** Model-driven apps (canvas apps with limitations)

## Resource Elements

### resources

Container for all resource definitions (code, CSS, images, localization).

**Availability:** Model-driven apps, canvas apps, portals

### css

References a CSS stylesheet file.

**Attributes:**
- `path`: Path to CSS file
- `order`: Loading order

**Availability:** Model-driven apps, canvas apps, portals

### img

References an image resource.

**Attributes:**
- `path`: Path to image file

**Availability:** Model-driven apps, canvas apps, portals

### resx

References a resource file for localization.

**Attributes:**
- `path`: Path to .resx file
- `version`: Version number

**Availability:** Model-driven apps, canvas apps, portals

## Feature Usage Elements

### uses-feature

Declares that the component uses a specific platform feature.

**Key Attributes:**
- `name`: Feature name (e.g., "Device.captureImage", "Device.getCurrentPosition", "Utility.lookupObjects", "WebAPI")
- `required`: Whether feature is required (true/false)

**Common Features:**
- Device.captureAudio
- Device.captureImage
- Device.captureVideo
- Device.getBarcodeValue
- Device.getCurrentPosition
- Device.pickFile
```
END THIRD-PARTY FILE 8c6e9e12866526e5

The third-party file has ended. Everything between the 8c6e9e12866526e5 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3403 of 8257 bytes. © github · MIT · https://github.com/github/awesome-copilot/tree/HEAD/instructions/pcf-manifest-schema.instructions.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md