Update instructions/csharp-best-practices.instructions.md

Co-authored-by: Copilot <[email protected]>

Author: SynergyMesh-admin

instructions/csharp-best-practices.instructions.md

@@ -1,50 +1,4 @@
----
-applyTo: '**/*.cs'
-description: 'C# best practices and formatting guidelines for AI code generation (all versions).'
----
-
-# C# Best Practices for AI Code Generation Instructions
-
-## Code Style and Formatting
-
-### Namespace Declarations
-
-- Use file-scoped namespace declarations when using C# 10+ (`namespace MyNamespace;`)
-- For older versions, use traditional block-scoped namespaces with proper indentation
-- Keep namespace declarations consistent within the project
-
-### Access Modifiers
-
-- Explicitly declare access modifiers for all members
-- Use `readonly` for fields that are only assigned in constructors
-- Use `const` for compile-time constants
-- Follow principle of least privilege for access levels
-
-### Type Declarations
-
-- Use `var` for local variables when the type is obvious from the right side
-- Use explicit types for method parameters, return types, and field declarations
-- Prefer target-typed expressions when the type is clear from context
-- Use meaningful and descriptive type names
-
-### Method and Property Formatting
-
-- Use expression-bodied members for simple one-line implementations
-- Place opening braces on new lines for methods, classes, and namespaces
-- Use auto-implemented properties when appropriate
-- Implement properties with backing fields only when additional logic is needed
-
-## Modern C# Patterns
-
-### Null Safety
-
-- Use null-conditional operators (`?.`, `??`, `??=`) when available
-- Validate parameters with appropriate null checks
-- Use `string.IsNullOrEmpty()` and `string.IsNullOrWhiteSpace()` for string validation
-- Consider nullable reference types when using C# 8+
-
-### String Handling
-
+# (File removed)
 - Use string interpolation `$""` instead of `String.Format()` or concatenation
 - Use `StringBuilder` for extensive string manipulation
 - Prefer `string.Equals()` with `StringComparison` for culture-aware comparisons