Is your feature request related to a problem? Please describe.
There is no copilot-instructions.md file in the Ignite UI Blazor repository. Without it, GitHub Copilot has no repo-scoped context about the library it doesn't know about component naming, coding conventions, file structure, best practices, or where domain-specific skills are located. This results in inconsistent, lower-quality AI-generated code suggestions.
Describe the solution you'd like
Add a copilot-instructions.md file that provides Copilot with:
- A Blazor developer persona focused on the latest .NET and C# 13 features
- Code examples showing the
.razor / .razor.cs / .razor.css code-behind pattern
- Links to official Blazor documentation resources
- Best practices covering naming conventions, Blazor patterns, components, state management, caching, error handling, security, and testing
- A Copilot Skills section linking to the domain-specific
SKILL.md files for components, grids, and theming
Describe alternatives you've considered
Relying on individual developers to add context manually in each Copilot prompt. This is error-prone and doesn't scale.
Additional context
A reference implementation already exists for the Ignite UI Angular repository. The Blazor version follows the same structure but uses C#/Razor conventions instead of TypeScript/Angular.
The file is actively used alongside skill files (SKILL.md) that teach Copilot about specific areas of the library, such as grids, components, and theming.
Is your feature request related to a problem? Please describe.
There is no
copilot-instructions.mdfile in the Ignite UI Blazor repository. Without it, GitHub Copilot has no repo-scoped context about the library it doesn't know about component naming, coding conventions, file structure, best practices, or where domain-specific skills are located. This results in inconsistent, lower-quality AI-generated code suggestions.Describe the solution you'd like
Add a
copilot-instructions.mdfile that provides Copilot with:.razor/.razor.cs/.razor.csscode-behind patternSKILL.mdfiles for components, grids, and themingDescribe alternatives you've considered
Relying on individual developers to add context manually in each Copilot prompt. This is error-prone and doesn't scale.
Additional context
A reference implementation already exists for the Ignite UI Angular repository. The Blazor version follows the same structure but uses C#/Razor conventions instead of TypeScript/Angular.
The file is actively used alongside skill files (
SKILL.md) that teach Copilot about specific areas of the library, such as grids, components, and theming.