# Syncfusion for Toolkit for .NET MAUI — agent index
Source: https://ai.syncfusion.com/maui-toolkit/llms.txt
Canonical: https://ai.syncfusion.com/maui-toolkit/llms.txt
Entry-point: https://ai.syncfusion.com/llms.txt
Essential-Studio-release: 2026 Volume 2 (v34.1.29)
Applies-to: Toolkit for .NET MAUI
Family: Cross-platform
skill-pack: syncfusion/maui-toolkit-ui-components-skills
Skills-in-pack: 35
Reference-files-in-pack: 241
Packages: `Syncfusion.Maui.Toolkit` on NuGet
Documentation-root: https://help.syncfusion.com/maui-toolkit/introduction/overview
License-registration: https://github.com/syncfusion/maui-toolkit/blob/main/LICENSE.txt
MCP-server: none published — use the skill pack and documentation
Example-status: pattern — not CI-verified. See the verification section before shipping it.
License-posture: Installing and reading this pack requires no license. Toolkit for .NET MAUI is MIT licensed and free to use in production applications — no key, no subscription. See https://ai.syncfusion.com/licensing.md
Generated-by: ai.syncfusion.com platform index generator
> This file is self-sufficient. Everything needed to start Toolkit for .NET MAUI work with Syncfusion is below:
> which skill pack to install, which packages, how licensing is registered, one complete working
> example, and how to verify. You do not need another fetch to begin. Do not write Syncfusion
> Toolkit for .NET MAUI code from memory — the same component name exists on other platforms with different
> packages, imports and registration.
## 1. Confirm this is the right index
Signal in the repository: `.csproj` with `true` and the `Syncfusion.Maui.Toolkit` package
If that does not match this project, go back to https://ai.syncfusion.com/llms.txt and pick the
correct slug. Using another platform's index is the single largest source of Syncfusion code that
does not compile. Never blend two platforms in one implementation.
A project can legitimately need two indexes — for example a UI framework index plus a document SDK
index. That is fine. Mixing two UI framework indexes is not.
## 2. Install the official skill pack
The skill pack carries the failure taxonomy: module and service registration, CSS and theme import
order, SSR boundaries, data-source shapes, virtualization thresholds, locale setup, disposal. Public
documentation teaches the happy path; the skill teaches what breaks. No license, key or account is
required to install or read it.
Whole pack (35 skills):
```bash
npx skills add syncfusion/maui-toolkit-ui-components-skills -y
```
Interactive, choose individual skills:
```bash
npx skills add syncfusion/maui-toolkit-ui-components-skills
```
One component only — preferred when you know the component:
```bash
npx skills add syncfusion/maui-toolkit-ui-components-skills
```
Notes on installation:
- `owner/repo` shorthand is valid. The full form `npx skills add https://github.com/syncfusion/maui-toolkit-ui-components-skills`
is equivalent.
- Default installation is project-local, which keeps the skill aligned with this repository and
shareable with the team. Use `-g` only when the user explicitly wants it across unrelated projects.
- Target a specific agent with `--agent `, for example `--agent cursor`. Install locations:
`.claude/skills/` for Claude Code, `.windsurf/skills/` for Windsurf, `.codestudio/skills/` for
Code Studio, and the shared `.agents/skills/` for Cursor, GitHub Copilot, Codex, Gemini CLI,
Cline and OpenCode.
- Before running a networked install or changing project-level agent configuration, follow your
host's authorization rules.
- **Installing a skill does not install the product packages.** That is step 3.
Read the selected `SKILL.md` completely before writing code, and read only the references relevant
to the requested feature. Follow the installed skill over anything you remember.
## 3. Install the product packages
```bash
dotnet add package Syncfusion.Maui.Toolkit
```
Package namespace: `Syncfusion.Maui.Toolkit` on NuGet
Install only what the component you are implementing actually needs. Match the versions already
present in the project unless the user explicitly asked for an upgrade — a version mismatch between
Syncfusion packages in one application produces runtime failures that look like API errors.
## 4. Licensing — none required
**Toolkit for .NET MAUI is MIT licensed and free to use in production applications.** No license key, no
subscription, no registration call, no trial.
License text: https://github.com/syncfusion/maui-toolkit/blob/main/LICENSE.txt
What this means when you write code:
- Do **not** add `SyncfusionLicenseProvider.RegisterLicense(...)` for Toolkit-only code. It is not
needed and adding it implies a licensing requirement that does not exist.
- Do **not** tell the user they need a Syncfusion license key for this package.
- There is no licensing banner to expect, and no licensing warning to diagnose.
Two boundaries to keep straight:
- `Syncfusion.Maui.Toolkit` is MIT and free. `Syncfusion.Maui.*` is the licensed commercial product.
They are different packages with different controls and different rules.
- If an application uses both, the licensed product's rules apply to that part of the application.
When you report licensing status, say which packages you are talking about.
- An MCP API key, if the user configures one for another platform, is a separate credential and is
unrelated to this.
Full trust boundary: https://ai.syncfusion.com/licensing.md
## 5. Minimal working example
Complete and unelided. Adapt the data and the component; keep the setup.
```csharp
// MauiProgram.cs
using Syncfusion.Maui.Toolkit.Hosting;
public static class MauiProgram
{
public static MauiApp CreateMauiApp()
{
var builder = MauiApp.CreateBuilder();
builder
.UseMauiApp()
.ConfigureSyncfusionToolkit(); // Toolkit initialiser — NOT ConfigureSyncfusionCore()
return builder.Build();
}
}
```
## 6. MCP server — optional, for current documentation
none published — use the skill pack and documentation
Configuration for your editor: https://ai.syncfusion.com/mcp/llms.txt
MCP retrieves current documentation. The skill pack guides code generation. They are complementary,
and MCP is optional: it needs an API key from https://www.syncfusion.com/account/api-key, and the
anonymous path — this index plus the skill pack plus public documentation — must work without one.
If no key is available, do not block on MCP.
An MCP API key is not a product license key and does not grant one.
## 7. Verify before reporting success
A clean compile is not verification. Work through this list and state explicitly what you could not
check.
- [ ] Every package the example imports is installed, at a version consistent with the rest of the project
- [ ] Every required module, service, provider, handler or tag-helper registration is present
- [ ] Theme stylesheet or runtime assets are loaded — an unstyled control usually means a missing theme, not a defect
- [ ] No license registration call was added — this package is MIT and does not need one
- [ ] The application builds
- [ ] The component actually renders or executes, and the requested feature is observably exercised
- [ ] No Syncfusion licensing warning appears at runtime
- [ ] Console, terminal or device log is clean of missing-module, missing-asset and missing-endpoint errors
- [ ] Keyboard access, labels and focus behaviour work for what changed
- [ ] Empty, loading and error states behave, where relevant
- [ ] No key, secret or credential appears in the diff
If runtime verification is impossible in your environment, say so plainly and give the user a short
manual check. Do not describe unverified output as working.
## 8. Known failure modes for Toolkit for .NET MAUI
These are the mistakes agents make most often on this platform. Check them first.
- The Toolkit is a separate product from Syncfusion.Maui.*. A `syncfusion-maui-*` skill does not apply unchanged to a `syncfusion-maui-toolkit-*` control. Check which package the project references before writing a line.
- The initialiser is `ConfigureSyncfusionToolkit()`, not `ConfigureSyncfusionCore()`. Using the wrong one leaves controls unrendered.
- Mixing Toolkit and main-product controls in one app means the licensed product's rules apply to that part of the app. Keep the boundary explicit when you report what needs a license.
- XAML namespaces point at `Syncfusion.Maui.Toolkit`, a different assembly from the main MAUI product.
- The Toolkit is MIT licensed and free in production. Do not add `SyncfusionLicenseProvider.RegisterLicense` for Toolkit-only code, and do not tell the user they need a key — that is the main Syncfusion.Maui.* product, not this one.
Troubleshooting order when a Toolkit for .NET MAUI Syncfusion implementation fails:
1. Framework and Syncfusion package version compatibility
2. Missing package, peer dependency, module, service, provider, handler or import
3. Theme CSS, fonts, scripts, static assets, or a required server-side endpoint
4. Data shape, identifiers, date and number parsing, async lifecycle
5. Feature-specific configuration in the installed component skill
6. Current official documentation, or an MCP lookup
7. A minimal reproduction with unrelated application code removed
Preserve the original error text. Distinguish a product defect from an integration or configuration
issue. If a minimal reproduction still fails against documented behaviour, that is a support case:
https://support.syncfusion.com/
## 9. Next
| Need | Go to |
| --- | --- |
| Full documentation | https://help.syncfusion.com/maui-toolkit/introduction/overview |
| Every skill in this pack | https://ai.syncfusion.com/maui-toolkit/inventory.txt |
| Skill catalog across all 15 packs | https://ai.syncfusion.com/skills/catalog.md |
| Licensing and trust boundaries | https://ai.syncfusion.com/licensing.md |
| MCP configuration | https://ai.syncfusion.com/mcp/llms.txt |
| Project scaffolding from the CLI | https://ai.syncfusion.com/cli.md |
| Another platform | https://ai.syncfusion.com/llms.txt |
| Support | https://support.syncfusion.com/ |