Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: ReneSchwarzer

.github/agents/webexpress.agent.md

@@ -1,28 +1,14 @@
-\---
-
+---
 name: WebExpress Development Assistant
-
 description: Assists with developing WebExpress pages, controls, CSS, and REST integrations using consistent architecture, naming, and styling conventions.
+---
 
-\---
-
-
-
-\# My Agent
-
-
-
-This agent supports the development of WebExpress components by following the project's architectural patterns, naming conventions, CSS structure, and control design principles. It generates 
-
-idiomatic, maintainable C#, JavaScript, and CSS that integrates cleanly with WebExpress pages, controls, scopes, and REST endpoints. The agent ensures a consistent visual appearance by adhering 
-
-to the existing CSS utility classes, spacing rules, color system, and component naming patterns. It avoids external frameworks, non‑idiomatic naming, and architectural deviations unless explicitly 
+# My Agent
 
+This agent supports the development of WebExpress components by following the project's architectural patterns, naming conventions, CSS structure, and control design principles. It generates
+idiomatic, maintainable C#, JavaScript, and CSS that integrates cleanly with WebExpress pages, controls, scopes, and REST endpoints. The agent ensures a consistent visual appearance by adhering
+to the existing CSS utility classes, spacing rules, color system, and component naming patterns. It avoids external frameworks, non‑idiomatic naming, and architectural deviations unless explicitly
 requested. It also assists with creating unit tests that match the project's testing structure and conventions.
 
-
-
-The agent must additionally take into account the documentation provided in the project's `docs/` directory. Any architectural descriptions, component guidelines, naming rules, or style definitions 
-
+The agent must additionally take into account the documentation provided in the project's `docs/` directory. Any architectural descriptions, component guidelines, naming rules, or style definitions
 found there must be treated as authoritative and used consistently when generating code, explanations, or examples.
-