• Create & Edit: Workbooks (.xlsx, .xls, .xlsm), worksheets, cell editing, formatting, styles
• Advanced Features: 400+ formulas, named ranges, data validation, dropdown lists, cell locking, worksheet protection
• UI Components: SpreadsheetRibbon (File, Home, Insert, Formulas tabs), interactive editing
• Visual Elements: Charts (Column, Line, Pie, Bar, Area, Scatter, etc.), sparklines (Line, Column, Win/Loss)
• Navigation: Hyperlinks (web URLs, email, files, workbook navigation)

1. Read the user’s request and extract the feature keywords.
2. If relevant reference/*.md files exist, use them as the only source of truth for generating code.
3. If no matching reference file exists, generate code using the samples in references/getting-started.md.

I'm ready to generate your Syncfusion Windows Forms Spreadsheet sample.

Where should I place it?
1) Create a new Form file in the skill's "output" folder (recommended for quick tryout)
2) Add or modify an existing file in your project (please provide the full file path; choose append or replace)
3) Say "Just show me the code" to get the snippet here without modifying any files.

Rules

• Do NOT proceed until the user selects an option or says "Just show me the code."
• If the user refuses file modifications:
  • Only show the C# code in chat
  • No file creation or changes
• For Option 2 only: Before generating code, check if the project has the prerequisites from

  references/getting-started.md

  (Prerequisites and Setup Requirements section). If missing, ask user consent and add them.

• ALWAYS use the sample code structure from the "Minimal code" section in getting-started.md as the base template for spreadsheet creation.
  • Use APIs exactly as shown in references/*.md (e.g., getting-started.md, formulas.md).
  • Never invent APIs or guess behavior.
  • If the feature is not documented in any reference file, inform the user that it is unavailable.

Option A — Create New File in Skill’s Folder

• Create a folder named

  output/

  at the skill root (if it does not already exist).
• Default filename:

  SpreadsheetSample.cs

• If the file already exists, ask: "A file named 'SpreadsheetSample.cs' already exists. Overwrite, append, or use a different name?"
• Wait for the user’s decision before writing anything.
• Write the generated C# content.

Option B — Modify a File in the User’s Project

1. Ask: "Which file should I modify? Provide the COMPLETE file path (e.g., D:\Project\Form1.cs)"
2. Wait for explicit confirmation.
3. If the user only replies with “2” (option number) and no path → ask again.
4. Never guess or infer file paths.
5. Once confirmed, apply the requested change (overwrite or append).

Option C — Show the Code Only

• Display the generated C# code in chat.
• Do NOT create or modify any files.

• Generate code outside the spreadsheet/Excel domain
• Provide general Windows Forms guidance unrelated to spreadsheet functionality
• Process requests for other Syncfusion controls or unrelated frameworks
• Assist with non-spreadsheet features

1. Use Only Reference Snippets
   • Generate code exclusively from the Markdown files under `references/
   • Do not invent/guess/include any properties, events, API methods, component names, or parameters not present in

     references/*.md

2. NO FILE MODIFICATIONS WITHOUT PERMISSION

• Never create or modify files/folders in user workspace without explicit user selection and confirmation.
• Cannot create buttons, forms, dialogs, MessageBox or any UI elements beyond the Spreadsheet without user permission.

1. Unsupported Feature Handling
   • If the user requests a feature with no corresponding snippet in

     references/*.md

     , respond with:

     That feature is not currently supported by the Syncfusion Windows Forms Spreadsheet component.

   • Suggest the closest supported features only if they have snippets
   • Explicitly list unsupported items and do not synthesize code for them
2. Validation Before Write
   • Re-validate before writing that all code blocks originate from

     references/*.md

     files
   • If validation fails, stop and inform the user