feat: update C# instructions and enhance package-lock with peer dependencies (#8)

* feat: update C# instructions and enhance package-lock with peer dependencies

* Updated based on PR freedback

* Update instructions/csharp.instructions.md

Co-authored-by: Daniel Olvera <139163393+danOIntellitect@users.noreply.github.com>

---------

Co-authored-by: Daniel Olvera <139163393+danOIntellitect@users.noreply.github.com>

Author: breaman

.github/upstream-sync-state.json

@@ -1,4 +1,8 @@
 {
+  "instructions\\csharp.instructions.md": {
+    "branch": "sync/instructions-csharp-instructions-md",
+    "upstreamSha": "206e2766109198bf687c5e5107e9c6994f1e1dc0"
+  },
   "prompts/csharp-xunit.prompt.md": {
     "branch": "sync/prompts-csharp-xunit-prompt-md",
     "upstreamSha": "6fb794bc7917fff6a259ae3ba72cd1fad350c0bf"

instructions/csharp.instructions.md

@@ -6,7 +6,7 @@ applyTo: '**/*.cs'
 # C# Development
 
 ## C# Instructions
-- Always use the latest version C#, currently C# 13 features.
+- Always use the latest version C#, currently C# 14 features.
 - Write clear and concise comments for each function.
 
 ## General Instructions
@@ -19,13 +19,17 @@ applyTo: '**/*.cs'
 
 - Favor clarity over brevity when naming identifiers.
 - Do not use abbreviations or contractions within identifier names.
+- Follow PascalCase for component names, method names, and public members.
+- Use camelCase for private fields and local variables.
+- Prefix interface names with "I" (e.g., IUserService).
 
 ## Formatting
 
 - Apply code-formatting style defined in `.editorconfig`.
 - Use file-scoped namespace declarations (C# 10.0 or later).
-- Insert a newline before the opening curly brace of any code block.
+- Insert a newline before the opening curly brace of any code block (e.g., after `if`, `for`, `while`, `foreach`, `using`, `try`, etc.).
 - Avoid omitting braces, except for the simplest single-line if statements.
+- Ensure that the final return statement of a method is on its own line.
 - Use pattern matching and switch expressions wherever possible.
 - Use `nameof` instead of string literals when referring to member names.
 - Provide XML doc comments on public APIs when they add more context than the signature alone.
@@ -74,7 +78,12 @@ applyTo: '**/*.cs'
 
 - Always include test cases for critical paths of the application.
 - Guide users through creating unit tests using appropriate testing frameworks.
+- Do not emit "Act", "Arrange" or "Assert" comments.
 - Copy existing style in nearby files for test method names and capitalization.
+- Explain integration testing approaches for external services or endpoints.
+- Demonstrate how to mock dependencies for effective testing.
+- Show how to test authentication and authorization logic.
+- Explain test-driven development principles as applied to the current domain.
 - Write tests that verify behavior, not implementation details.
 - Use meaningful test method names that describe the scenario being tested.
-- Demonstrate effective use of mocking for dependencies.
+- Demonstrate effective use of mocking for dependencies.