Syncfusion WPF DOCX Editor

Overview

This skill helps developers generate WPF code for integrating the Syncfusion DOCX Editor into their applications. It provides ready-to-use snippets and best practices for embedding a SfRichTextBoxAdv that supports editing, reviewing, formatting, and more.

Key Capabilities

• Document Editing: Create, edit, and view Word documents.
• Protection: Apply read-only mode, allow comments.
• Comments: Add comments, replies, and navigate between them.
• Find and replace: Perform programmatic find and replace operations for automation.
• Import/Export: Open and save .doc/.docx/.rtf/.html/.xaml/.txt.
• Clipboard: Copy, cut, paste rich content with formatting.
• Hyperlinks: Insert, edit, and navigate hyperlinks.

Prerequisites

• NuGet Packages: Syncfusion.SfRichTextBoxAdv.WPF
• Syncfusion License: https://www.syncfusion.com/products/communitylicense

Quick Start Examples

Example 1: Create Document Editor

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

Result: A WPF XAML + C# snippet that initializes SfRichTextBoxAdv.

Example 2: Enable Read‑Only Restriction Mode

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

Result: A C# snippet that loads a document and applies read-only protection during initialization.

---

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

Trigger keywords: "code", "snippet", "how to", "how to write", "show me", "sample", "example code", "generate code", "generate code for", "implement", "implementation", "create", "integrate", "add to component", "add to project", "configure documenteditor", "API example", "usage example", "how do I", "how to use", "document editor", "wpf document editor", "docx editor", "wpf docx editor", "load docx", "comments", "protect document", "find and replace","MainWindow.xaml", "NuGet", "sfrichtextboxadv", "sfrichtextribbon"

Workflow:

1. Analyze the user's request to identify the feature (e.g., comments, find and replace, import and export).

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

5. Only after the user selects a delivery mode, proceed to generate WPF code using the APIs and snippets from references/*.md, substituting concrete placeholders from the user's project.

6. Do NOT make changes to workspace project files unless the user explicitly chose Option 1 and provided the file path with permission.

7. Provide complete WPF 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 React 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.

2. Snippets must be tested — All code must build and run against current Syncfusion WPF NuGet packages (e.g., Syncfusion.SfRichTextBoxAdv.WPF) and supported .NET target frameworks.

3. 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)

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

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

6. Framework adaptation — Default to C# + XAML. When user specifies framework.

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

Rules

• Only use Syncfusion SfRichTextBoxAdv 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 XAML for WPF projects. No JavaScript, TypeScript, or other languages.