Syncfusion Blazor DOCX Editor

Overview

Generates production-ready C# and Razor code for integrating the Syncfusion DOCX Editor (Document Editor) into Blazor Server or WebAssembly applications. It provides ready-to-use snippets and best practices for embedding a Document Editor that supports editing, reviewing, formatting, and more.

Key Capabilities

• Document Editing: Create, edit, and view Word documents.
• Protection: Apply read-only mode, allow comments, allow form filling, enforce tracked changes,and define editable ranges.
• Review: Enable track changes (revisions) and accept/reject changes.
• Comments: Add comments, replies, and author metadata.
• Find and replace: Perform programmatic find and replace operations for automation.
• Form Fields: Insert and fill text fields, check boxes, and dropdown form fields.

Prerequisites

• .NET 8+ Blazor project (Server/WebAssembly/WebApp)
• NuGet packages: Syncfusion.Blazor.WordProcessor, Syncfusion.Blazor.Themes
• Syncfusion License: https://www.syncfusion.com/products/communitylicense

Quick Start Examples

Example 1: Display a basic DOCX Editor

User: "Show me code to create a Document Editor component."

Result: C# + Razor code snippet displayed

Example 2: Enable Read‑Only Restriction Mode

User: "Create a Document Editor with Read‑Only restriction mode."

Result: A Blazor snippet that creates a Document Editor with read‑only protection enabled.

Generate C# Code for the User's Project (default)

Trigger keywords: "code", "snippet", "how to", "show me", "sample", "example code", "generate code", "implement", "add to component", "configure documenteditor", "create" , "blazor document editor", "docx editor", "document editor", "track changes", "load docx", "comments", "accept changes", "protect document", "find and replace", "content control"

Workflow:

1. Analyze the user's request to identify the feature (e.g., track changes, restrict editing, toolbar customization).
2. Read the relevant references/*.md file(s) to understand the APIs and code patterns for the requested feature.
3. STOP before generating code. Check if the user has already chosen a delivery mode.
4. If no delivery mode is chosen yet, you MUST ask the user first using this concise multiple-choice question:

"How would you like to receive the generated code?"

- Option 1: Replace the code in a specific project file (you'll need to provide the file path and confirm) - Option 2: Share the code directly in the chat window

1. Only after the user selects a delivery mode, proceed to generate C# code using the APIs and snippets from references/*.md, substituting concrete placeholders from the user's project.
2. Do NOT make changes to workspace project files unless the user explicitly chose Option 1 and provided the file path with permission.
3. Provide complete C# snippets and concise integration steps after delivering the code.

Refer to ## Rules section for operational constraints (output directory, temporary files, allowed libraries, etc.)

Code References

All code snippets and examples are in the references/ folder. Each file contains:

• Minimal Code — a working, ready-to-use snippet
• Placeholders — values the user must customize
• Notes — best practices, additional information to note while using that functionality, constraints

Key Rules for Code Generation

1. No inline code in SKILL.md — Always point to snippets in references/*.md. This file is loaded into context for every prompt; inline code wastes tokens.

1. Snippets must be tested — All code must compile and run against the current Syncfusion.Blazor.WordProcessor NuGet package version.

1. Minimal Code + Placeholders + Notes — Every reference file must include:

- Minimal Code (complete, working snippet) - Placeholders (values user must substitute — marked with {{ }} or [PLACEHOLDER]) - Notes (best practices, framework-specific adaptations, constraints)

1. Share code and notes for the requirement — Never create temporary files or scripts.

1. License handling — Never hardcode license keys. Point user to environment variables or config files.

1. Framework adaptation — Default to C# + Razor. When user specifies framework.

1. No hallucinated APIs — Use only verified Syncfusion DOCX Editor SDK method names. One wrong method breaks user trust.

Rules

• Only use Syncfusion Document Editor APIs — never recommend or use alternative Word Editor libraries.
• No temporary files — never create temporary scripts, intermediate files, or scaffolding outside the output directory
• C#-only code — all generated code must be valid C# and Razor for Blazor projects. No JavaScript, Python, or other languages.