@@ -171,3 +171,42 @@ Scenarios requiring human intervention:
171171 ```
172172
173173- For longer snippets, highlight specific lines:
174+ -
175+ - Use modern C# coding patterns in all examples
176+
177+ ## File Naming and PRs
178+
179+ - Name Markdown files in **lowercase with hyphens** (no spaces or underscores)
180+ - **Omit** filler words like "the" or "a" from file names
181+ - When reviewing PRs, check for:
182+ - Technical accuracy
183+ - Code consistency with latest practices
184+ - Style guide adherence
185+ - Valid links
186+ - Proper file structure
187+ - Inclusive language
188+
189+ ## Issue Handling
190+
191+ When creating a PR for an issue:
192+
193+ 1. **Read the full issue and all linked references**
194+ - Pay special attention to linked PRs with implementation details
195+
196+ 2. **Understand the specific ASP.NET Core technology**
197+ - For pre-release features, study code samples from linked PRs
198+ - Consider version context
199+ - Examine test cases to understand intended behavior
200+
201+ 3. **Special handling for labeled issues:**
202+ - **breaking-change:** Include breaking change guidance
203+ - **new-feature:** State which version introduced the feature
204+ - **bug:** Focus on correcting technical inaccuracies
205+
206+ ## ASP.NET Core Specific Guidelines
207+
208+ - Use the latest supported version for examples unless otherwise specified
209+ - Lead with Microsoft recommended approaches
210+ - Include differences between minimal API and controller-based approaches when relevant
211+ - For middleware, lead with the middleware class approach
212+ - For Blazor, clearly distinguish between Server and WebAssembly hosting models
0 commit comments