Update development instructions and guidelines (#29)

* Delete outdated development instructions for Next.js + Tailwind and Python; add comprehensive guidelines for PostgreSQL DBA, Angular, ASP.NET REST APIs, Azure Functions with TypeScript, Bicep, Blazor, CMake with vcpkg, C#, .NET MAUI, GenAIScript, Terraform for Azure, localization, and markdown standards.

* Update documentation and prompts for consistency and clarity

- Standardized description formatting in various markdown files to use single quotes.
- Added error handling utility in update-readme.js for safer file operations.
- Improved title extraction logic in update-readme.js to handle frontmatter more robustly.
- Updated chat modes section in README to reflect new emoji and sorted chat mode links.
- Cleaned up various instruction files for better readability and consistency.
- Ensured all markdown files end with a newline for better compatibility with version control.

* Remove standardize-frontmatter.js script

* Add usage instructions for creating and switching chat modes in README.md

* Update README.md generation script to enhance instructions and usage details for custom chat modes

* Update README.md and update-readme.js for improved instruction clarity and consistency

* Refactor README.md links and update readme script for improved clarity and consistency in instructions

* Update README.md and update-readme.js for improved instruction clarity and consistency

* Changing from a patch to regen approach for the readme

* Bit more cleanup for how to show things in the readme

* Adding missing description

* Another missing description

---------

Co-authored-by: Aaron Powell <me@aaron-powell.com>

prompts/aspnet-minimal-api-openapi.prompt.md

@@ -1,9 +1,11 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems"]
-description: "Create ASP.NET Minimal API endpoints with proper OpenAPI documentation"
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems']
+description: 'Create ASP.NET Minimal API endpoints with proper OpenAPI documentation'
 ---
 
+# ASP.NET Minimal API with OpenAPI
+
 Your goal is to help me create well-structured ASP.NET Minimal API endpoints with correct types and comprehensive OpenAPI/Swagger documentation.
 
 ## API Organization

prompts/az-cost-optimize.prompt.md

@@ -1,9 +1,10 @@
 ---
-mode: agent
-description: Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.
+mode: 'agent'
+description: 'Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.'
 ---
 
-## Overview
+# Azure Cost Optimize
+
 This workflow analyzes Infrastructure-as-Code (IaC) files and Azure resources to generate cost optimization recommendations. It creates individual GitHub issues for each optimization opportunity plus one EPIC issue to coordinate implementation, enabling efficient tracking and execution of cost savings initiatives.
 
 ## Prerequisites
@@ -301,4 +302,4 @@ This workflow analyzes Infrastructure-as-Code (IaC) files and Azure resources to
 - ✅ All recommendations include specific, executable Azure CLI commands
 - ✅ Priority scoring enables ROI-focused implementation
 - ✅ Architecture diagram accurately represents current state
-- ✅ User confirmation prevents unwanted issue creation
+- ✅ User confirmation prevents unwanted issue creation

prompts/comment-code-generate-a-tutorial.prompt.md

@@ -1,3 +1,7 @@
+---
+description: 'Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial.'
+---
+
 Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial.
 
 1. **Refactor the code**  
@@ -18,4 +22,4 @@ Transform this Python script into a polished, beginner-friendly project by refac
    - **How It Works:** A breakdown of the code logic based on the comments  
    - **Example Usage:** A code snippet showing how to use it  
    - **Sample Output:** (Optional) Include if the script returns visible results  
-   - Use clear, readable Markdown formatting
+   - Use clear, readable Markdown formatting

prompts/csharp-async.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems"]
-description: "Get best practices for C# async programming"
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems']
+description: 'Get best practices for C# async programming'
 ---
 
 # C# Async Programming Best Practices

prompts/csharp-docs.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems"]
-description: "Ensure that C# types are documented with XML comments and follow best practices for documentation."
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems']
+description: 'Ensure that C# types are documented with XML comments and follow best practices for documentation.'
 ---
 
 # C# Documentation Best Practices

prompts/csharp-mstest.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems", "search"]
-description: "Get best practices for MSTest unit testing, including data-driven tests"
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems', 'search']
+description: 'Get best practices for MSTest unit testing, including data-driven tests'
 ---
 
 # MSTest Best Practices
@@ -65,4 +65,4 @@ Your goal is to help me write effective unit tests with MSTest, covering both st
 * Group tests by feature or component
 * Use test categories with `[TestCategory("Category")]`
 * Use test priorities with `[Priority(1)]` for critical tests
-* Use `[Owner("DeveloperName")]` to indicate ownership
+* Use `[Owner("DeveloperName")]` to indicate ownership

prompts/csharp-nunit.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems", "search"]
-description: "Get best practices for NUnit unit testing, including data-driven tests"
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems', 'search']
+description: 'Get best practices for NUnit unit testing, including data-driven tests'
 ---
 
 # NUnit Best Practices

prompts/csharp-xunit.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems", "search"]
-description: "Get best practices for XUnit unit testing, including data-driven tests"
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems', 'search']
+description: 'Get best practices for XUnit unit testing, including data-driven tests'
 ---
 
 # XUnit Best Practices

prompts/ef-core.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["changes", "codebase", "editFiles", "problems", "runCommands"]
-description: "Get best practices for Entity Framework Core"
+mode: 'agent'
+tools: ['changes', 'codebase', 'editFiles', 'problems', 'runCommands']
+description: 'Get best practices for Entity Framework Core'
 ---
 
 # Entity Framework Core Best Practices

prompts/gen-specs-as-issues.prompt.md

@@ -1,3 +1,7 @@
+---
+description: 'This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.'
+---
+
 # Product Manager Assistant: Feature Identification and Specification
 
 This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
@@ -157,4 +161,4 @@ Remember throughout this process:
 - Build a foundation that can be extended later
 - Consider the open-source community and contribution model
 
-This workflow embodiment of our approach should help maintain consistency in how features are specified and prioritized, ensuring that software projects evolve in a thoughtful, user-centered way.
+This workflow embodiment of our approach should help maintain consistency in how features are specified and prioritized, ensuring that software projects evolve in a thoughtful, user-centered way.

prompts/javascript-typescript-jest.prompt.md

@@ -1,5 +1,5 @@
 ---
-description: "Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns."
+description: 'Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.'
 ---
 
 ### Test Structure

prompts/multi-stage-dockerfile.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: "agent"
-tools: ["codebase"]
-description: "Create optimized multi-stage Dockerfiles for any language or framework"
+mode: 'agent'
+tools: ['codebase']
+description: 'Create optimized multi-stage Dockerfiles for any language or framework'
 ---
 
 Your goal is to help me create efficient multi-stage Dockerfiles that follow best practices, resulting in smaller, more secure container images.

prompts/my-issues.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: agent
+mode: 'agent'
 tools: ['githubRepo', 'github', 'get_issue', 'get_issue_comments', 'get_me', 'list_issues']
-description: "List my issues in the current repository"
+description: 'List my issues in the current repository'
 ---
 
 Search the current repo (using #githubRepo for the repo info) and list any issues you find (using #list_issues) that are assigned to me.

prompts/my-pull-requests.prompt.md

@@ -1,7 +1,7 @@
 ---
-mode: agent
+mode: 'agent'
 tools: ['githubRepo', 'github', 'get_me', 'get_pull_request', 'get_pull_request_comments', 'get_pull_request_diff', 'get_pull_request_files', 'get_pull_request_reviews', 'get_pull_request_status', 'list_pull_requests', 'request_copilot_review']
-description: "List my pull requests in the current repository"
+description: 'List my pull requests in the current repository'
 ---
 
 Search the current repo (using #githubRepo for the repo info) and list any pull requests you find (using #list_pull_requests) that are assigned to me.
@@ -12,4 +12,4 @@ If a PR is waiting for someone to review, highlight that in the response.
 
 If there were any check failures on the PR, describe them and suggest possible fixes.
 
-If there was no review done by Copilot, offer to request one using #request_copilot_review.
+If there was no review done by Copilot, offer to request one using #request_copilot_review.