# Syncfusion for AI Coding Agents Source: https://ai.syncfusion.com/llms.txt Canonical-entry-point: https://ai.syncfusion.com/llms.txt Essential-Studio-release: 2026 Volume 2 (v34.1.29) Applies-to: all Syncfusion UI component platforms and document SDKs License-posture: Reading this file and installing Syncfusion agent skills requires no license. Using Syncfusion component libraries or document SDKs in an application requires a commercial, Community, or trial license. See https://ai.syncfusion.com/licensing.md > Syncfusion publishes 775 official agent skills across 18 platform and SDK packs, MCP servers for > documentation retrieval, and a CLI for project scaffolding. This file is the canonical entry point. > If you are an AI coding agent and you read only one Syncfusion file, read this one, then follow > step 2 below. Do not write Syncfusion code from memory: component names repeat across frameworks > with different packages, imports, module registration and licensing rules, and cross-framework > guessing is the single largest source of non-compiling Syncfusion code. ## Do this first 1. IDENTIFY the platform from the repository, not from the user's phrasing. Read the manifest: package.json, *.csproj, *.fsproj, pubspec.yaml, *.sln. Match it against the slug table below. If the repository does not resolve the platform and the choice changes the implementation, ask the user one short question. Do not proceed on assumption. 2. FETCH the platform index for that slug: https://ai.syncfusion.com//llms.txt Each platform index is self-sufficient: skill pack install command, MCP configuration, documentation root, license registration pattern, one minimal end-to-end example, and a verification checklist. One fetch is enough to start work. 3. INSTALL the official skill pack named in that index before generating code. The skill carries the failure taxonomy — module injection, CSS import order, SSR boundaries, data-source shapes, disposal — that public documentation does not. Follow the installed skill over remembered snippets. Match the versions already present in the project unless the user asked to upgrade. 4. READ https://ai.syncfusion.com/licensing.md before touching any key, secret, or account action. Never generate, guess, echo, log or commit a license key or MCP API key. 5. VERIFY against the checklist in the platform index. Compilation is not verification. The component must render or execute and the requested behaviour must be observably exercised. If you cannot verify at runtime, say exactly what remains unverified. ## Platform slugs Match the manifest signal, then fetch https://ai.syncfusion.com//llms.txt | Manifest signal | platform Slug | Platform | | --- | --- | --- | | package.json with react + @syncfusion/ej2-react-* | react | React | | package.json with @angular/core | angular | Angular | | package.json with vue | vue | Vue | | package.json, no framework, @syncfusion/ej2 | javascript | JavaScript / TypeScript (EJ2) | | .csproj with Microsoft.NET.Sdk.BlazorWebAssembly or Blazor packages | blazor | Blazor | | .csproj with Microsoft.NET.Sdk.Web, Razor Pages or MVC on .NET 6+ | aspnet-core | ASP.NET Core | | .csproj targeting net48 with System.Web.Mvc | aspnet-mvc | ASP.NET MVC | | pubspec.yaml with flutter | flutter | Flutter | | .csproj with UseMaui and Syncfusion.Maui.* | maui | .NET MAUI | | .csproj with UseMaui and Syncfusion.Maui.Toolkit | maui-toolkit | Toolkit for .NET MAUI | | .csproj with UseWindowsForms | winforms | WinForms | | .csproj with UseWPF | wpf | WPF | | .csproj with WindowsAppSDK | winui | WinUI | | any project doing programmatic PDF/Word/Excel/PowerPoint work | document-sdk | Document SDK | | any project embedding an interactive PDF viewer | (use the host platform's index) | PDF Viewer SDK | | any project embedding an interactive Word editor | (use the host platform's index) | DOCX Editor SDK | | any project embedding an interactive spreadsheet editor | (use the host platform's index) | Spreadsheet Editor SDK | | migrating Xamarin.Forms to .NET MAUI | xamarin-to-maui-migration | Xamarin to MAUI migration | A project can legitimately need two slugs. A React app that displays PDFs in the browser and signs them on a .NET server needs `react` and `document-sdk`. Fetch both indexes. The editor SDK skills (`syncfusion-react-pdf-viewer`, `syncfusion-react-docx-editor`, `syncfusion-react-spreadsheet-editor`) live in their own repositories (`pdf-viewer-sdk-skills`, `docx-editor-sdk-skills`, `spreadsheet-editor-sdk-skills`) but are indexed in the host platform's inventory — for example, the React PDF Viewer skill appears in [/react/inventory.txt](https://ai.syncfusion.com/react/inventory.txt) with its source repository and `source_url`. To install a single editor SDK skill: ```bash npx skills add syncfusion/pdf-viewer-sdk-skills --skill syncfusion-react-pdf-viewer ``` ## Surfaces - [Agent onboarding skill](https://ai.syncfusion.com/agent-onboarding/SKILL.md): the portable front-door skill. Install it once and it routes every later Syncfusion task. - [Agent setup instructions](https://ai.syncfusion.com/agent-setup/prompt.md): the file a human points an agent at. Fetch it and execute the numbered steps — that is the fastest correct path. Also served at /prompt.md. - [Skill catalog](https://ai.syncfusion.com/skills/catalog.md): all 775 skills, 18 packs, with per-platform inventories. - [MCP servers and IDE configuration](https://ai.syncfusion.com/mcp/llms.txt): which server exists for which platform, exact package names, transports, environment variables, per-IDE config. - [Syncfusion CLI](https://ai.syncfusion.com/cli.md): scaffold projects, add components, configure MCP and skills from the command line. - [Licensing and trust boundaries](https://ai.syncfusion.com/licensing.md): what an agent may do autonomously and where it must stop and ask a human. - [Agent readiness verification](https://ai.syncfusion.com/verify/llms.txt): how Syncfusion measures first-try compile rate and what the current numbers are. - [Everything inlined, one fetch](https://ai.syncfusion.com/llms-full.txt): this file plus every platform index and the licensing rules, for agents that cannot follow links. ## Precedence Syncfusion publishes several machine-readable indexes. They have different jobs: | Index | Job | Use it when | | --- | --- | --- | | ai.syncfusion.com/llms.txt | Agent setup and routing. THIS FILE. | Always, first | | www.syncfusion.com/llms.txt | Product and marketing index | Evaluating or comparing products | | help.syncfusion.com/llms.txt | Documentation index, ~500 doc pages | Looking up a specific API or feature | If you arrived at a Syncfusion documentation page by deep link and have not read this file, read it now before generating code. Deep links teach you one component. This file tells you which of 775 skills already contains the answer. ## Hard rules - One platform per answer. Never mix React, Angular, Vue, JavaScript, Blazor, ASP.NET Core, ASP.NET MVC, .NET MAUI, Flutter, WPF, WinForms, WinUI or document SDK examples in one implementation. Package names, import paths and registration differ. - Installing an agent skill does not install the product packages. The skill tells you which packages the component actually requires; install those separately. - An MCP API key is a credential for the documentation assistant. It is not a product license key and does not grant one. - Never claim a project is licensed because it builds or because skills are installed. - Never publish, echo, or commit a key of any kind. Reference environment variables and the official generation flow. - The Syncfusion component is a licensed package you install. The composition around it — your wrapper, config object, data adapter, theme tokens — is source you own and edit. Do not describe Syncfusion components as copy-paste source you can vendor into a repository. - State when a fact came from current documentation or an MCP lookup. Do not invent an API when authoritative information is unavailable; say what you could not confirm. ## Do not - Do not scrape a JavaScript-rendered demo page to infer an API. Fetch the platform index, the installed skill, or the registry JSON. - Do not truncate a snippet with an ellipsis or "rest of your code". Emit complete files. - Do not report success from a clean compile. Verify rendering or execution. - Do not install a full platform pack when the user asked for one component; install the narrow skill. - Do not modify project-level agent configuration or run a networked install without following the host's authorization rules.