Add Ignite UI Blazor skill

[kdinev]

Summary

This pull request adds a new skill for integrating Ignite UI components into Blazor applications, along with an evaluation test for the skill. The main focus is to provide clear, file-oriented guidance for adding and configuring Ignite UI in various Blazor project types, especially split Blazor Web Apps.

Related issue

Validation

Introduced a new evaluation YAML (eval.yaml) that tests the skill’s ability to provide concrete, file-specific integration steps for using Ignite UI in a split Blazor Web App. The evaluation checks for explicit package references, service registration in both server and client, correct _Imports.razor usage, proper asset linking, and file-oriented instructions.

Checklist

• I searched existing issues and pull requests to avoid duplicates.
• I kept this pull request focused and avoided unrelated refactors.
• I added or updated tests, evals, or documentation when changing skill or agent behavior.
• I updated CODEOWNERS when adding or moving owned content.
• I updated all marketplace manifests when plugin metadata changed.
• I updated eng/known-domains.txt for any new external domains referenced by skill content.

[Copilot]

Pull request overview

This pull request introduces a new dotnet-blazor skill that guides developers through integrating Ignite UI (including GridLite) into Blazor apps—especially split Blazor Web Apps—and adds a capability eval to validate that the skill produces concrete, file-oriented setup steps.

Changes:

• Added a new skill document (SKILL.md) describing NuGet packages, service registration, _Imports.razor, host-page assets, and render-mode guidance for Ignite UI in Blazor.
• Added a new evaluation spec (eval.yaml) to test that responses include the required packages, AddIgniteUIBlazor() registration, _Imports.razor usage, and asset linking details.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
tests/dotnet-blazor/use-igniteui-blazor/eval.yaml	Adds a capability eval that checks for key Ignite UI integration details in the model output.
plugins/dotnet-blazor/skills/use-igniteui-blazor/SKILL.md	Adds the new skill guidance for installing/configuring Ignite UI (Lite + GridLite) across Blazor project types.

Suppressed comments (2)

plugins/dotnet-blazor/skills/use-igniteui-blazor/SKILL.md:84

• The fingerprinted asset example also uses the _content/IgniteUI.Blazor/... root; if the intent is to document the Lite package setup, this should reference the Lite asset root for consistency with the rest of the setup steps.

<link rel="stylesheet" href="@Assets["_content/IgniteUI.Blazor/themes/light/bootstrap.css"]" />

plugins/dotnet-blazor/skills/use-igniteui-blazor/SKILL.md:79

• The theme path description still points to _content/IgniteUI.Blazor/themes/, which doesn’t match the recommended IgniteUI.Blazor.Lite package in this skill. Aligning the documented _content root avoids confusion about which static asset base path to use.

Theme files under `_content/IgniteUI.Blazor/themes/` are `{light|dark}/{bootstrap|material|fluent|indigo}.css` — link exactly one.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[AbhitejJohn]

Tagging @danroth27 and @javiercn to help review.