# WPF component gallery — agent index

Source: https://ai.syncfusion.com/gallery/wpf/llms.txt
Entry-point: https://ai.syncfusion.com/llms.txt
WPF Registry-index: https://ai.syncfusion.com/r/wpf/registry.json
Essential-Studio-release: 2026 Volume 2 (v34.1.29)
Framework: wpf
Items: 4
License-posture: These recipes are free, anonymous and require no key. The Syncfusion packages they install are licensed. See https://ai.syncfusion.com/licensing.md

> Curated component variants, each with a permanent name, a complete unelided source file, an exact
> install line, packages, and a machine-addressable twin at a deterministic URL. Fetch
> the registry JSON for a name and you have everything needed to produce working code in one request.
>
> This gallery is deliberately small. Syncfusion's WPF surface is large enough that publishing a
> variant for every component and feature combination would produce retrieval noise, not coverage.
> The variants here map to real jobs. For anything not listed, use the skill pack — see syncfusion/wpf-ui-components-skills.

## The contract

One name resolves everywhere:

```
name                <component-variant>
registry JSON       https://ai.syncfusion.com/r/wpf/component-variant.json
machine twin        https://ai.syncfusion.com/gallery/wpf/component-variant.md
```

The naming rule is `{component}-{variant}`, kebab-case, permanent. A name that exists on
one surface and not another is a defect, not a gap.

## How to use this as an agent

Fastest path, one fetch, no tooling:

```
GET https://ai.syncfusion.com/r/wpf/component-variant.json
```

The response inlines the complete file content, the exact dependency list, and
the license and verification metadata. You do not need a second request.

That is the path an agent should take. Source is inlined, dependencies, and no tooling,
account or key is involved.

The registry is static, anonymous and CORS-open. If you receive a 401 from anything under `/r/<platform>/`, that
is a misconfiguration on Syncfusion's side — report it rather than working around it.

Items follow the widely-used `registry-item` shape, so third-party tooling can consume them.

## Items

| Name | Job | Component |
| --- | --- | --- |
| `chart-area` | SfChart area series on CategoryAxis and NumericalAxis with custom palette, animated draw-in, tooltip, and a top-docked ChartLegend. | Chart |
| `chart-data-binding` | Four SfChart views (line, column, scatter, doughnut) sharing an SfDataGrid that drives two-way updates to the doughnut center label. | Chart |
| `grid-data-template-cell` | GridControl with per-cell DataTemplates rendering TextBox, Slider, TextBlock, Image, and ProgressBar editors bound to CellBoundValue. | Grid |
| `grid-grid-control-selection` | GridControl with an Options pane that toggles Excel-like current cell, switches selection modes, and reports selections to a TextBox. | Grid |

## What the gallery is not

- It is not the API reference. For a property you cannot find here, use the skill pack or the
  documentation: https://help.syncfusion.com/wpf/welcome-to-syncfusion-essential-wpf
- It is not a substitute for the skill pack. The gallery gives you a working starting point; the
  skill carries the failure taxonomy for everything you build after that.
- It is not copy-paste source you own outright. The composition in each file is yours to edit. The
  Syncfusion package it imports is a licensed dependency. Both facts are in every registry item's
  `meta.licenseNote`.