- Introduced comprehensive documentation for Azure Verified Modules (AVM) and Bicep.
- Included guidelines for module discovery, usage, naming conventions, and best practices.
- Added validation requirements and troubleshooting tips for Bicep files.
- Introduce comprehensive guidelines for TypeScript development targeting TypeScript 5.x and ES2022 output.
- Include core intents, general guardrails, project organization, naming and style, formatting, type system expectations, async handling, architecture patterns, external integrations, security practices, configuration management, UI components, testing expectations, performance, and documentation.
- Add new prompts for suggesting GitHub Copilot collections and instructions.
- Improve the process and output format for suggested collections and instructions, prompts and chat modes.
- Ensure all new prompts align with the current repository context and chat history.
* Add Technical Spike collection and related resources
- Introduced a new collection for Technical Spikes, including a chat mode for research and a prompt for creating spike documents.
- Updated the Project Planning & Management collection to include references to technical spikes.
- Enhanced README files to reflect the addition of technical spike resources.
- Created detailed documentation for the technical spike research methodology and prompt structure.
- Added new tags and items to facilitate better organization and discovery of technical spike-related content.
* CHANGE: Update research methodology for technical spikes
- Refine tool usage philosophy for exhaustive research
- Enhance todo management protocol for better tracking
- Improve spike document update protocol for real-time logging
- Refined the process for updating Azure Verified Modules in Bicep files.
- Added steps for identifying unique AVM modules and validating updates.
- Updated tool usage guidelines to include additional tools.
- Clarified output format and summary requirements.
* CHANGE: update tools list and enhance implementation plan
- Reordered tools in the implementation plan for clarity.
- Added structured implementation phases with task tables.
- Revised goal description for better understanding.
* CHANGE: add status definition for implementation plans
- Introduced a new section for defining the status of implementation plans.
- Status options include `Completed`, `In progress`, `Planned`, `Deprecated`, and `On Hold`.
- Status is displayed as a badge in the introduction section.
* CHANGE: add status field to implementation plan
- Introduced a new 'status' field to the implementation plan.
- The status can be set to 'Completed', 'In progress', 'Planned', 'Deprecated', or 'On Hold'.
* CHANGE: Add PowerShell Pester v5 Testing Guidelines
- Introduced a new guide for PowerShell Pester testing best practices.
- Covers file naming, test structure, core keywords, setup/teardown, assertions, mocking, and best practices.
- Provides examples and configuration details for effective test execution.
* CHANGE: Remove unnecessary code block from guidelines
- Removed the empty PowerShell code block from the PowerShell Pester v5 testing guidelines.
* CHANGE: Correct file naming pattern in guidelines
- Updated the file naming pattern from '**/*.tests.ps1' to '**/*.Tests.ps1' for consistency with PowerShell Pester v5 conventions.
---------
Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
* CHANGE: Add GitHub Actions Workflow Specification prompt
- Introduced a new prompt for creating formal specifications for GitHub Actions CI/CD workflows.
- The prompt includes AI-optimized requirements and a comprehensive specification template.
- Aimed at enhancing workflow documentation and maintenance.
* CHANGE: Update GitHub Actions Workflow Specification
- Enhance the GitHub Actions workflow specification prompt with a detailed description for AI optimization and workflow maintenance.
---------
Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
* CHANGE: Add status section to implementation plan templates
- Introduced a status section in the implementation plan templates to define the current state of the plan.
- Status options include: Completed, In progress, Planned, Deprecated, and On Hold.
- Status will be displayed as a badge in the introduction section.
* CHANGE: Update status formatting in implementation plans
- Enclosed status options in quotes for consistency
- Updated formatting in implementation plan and prompt files
---------
Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
* Add prompts for .NET best practices, design pattern review, and GitHub Copilot suggestions
- Introduced a comprehensive prompt for ensuring .NET/C# code adheres to best practices, covering documentation, design patterns, dependency injection, resource management, async patterns, testing standards, configuration, AI integration, error handling, performance, security, and code quality.
- Added a prompt for reviewing C#/.NET code for design pattern implementation, providing a checklist for required patterns, architecture, best practices, SOLID principles, performance, maintainability, testability, security, documentation, code clarity, and clean code.
- Created prompts for suggesting relevant GitHub Copilot chatmodes and prompts based on the current repository context, including a structured process for fetching available chatmodes/prompts, scanning local files, and presenting options with rationale.
- Developed a prompt for updating Azure Verified Modules (AVM) in Bicep files, detailing the process for scanning, checking for updates, validating, and handling breaking changes.
- Implemented a prompt for updating implementation plans with new requirements, ensuring machine-readable output and adherence to a strict template.
- Added a prompt for updating the llms.txt file to reflect changes in documentation or specifications, focusing on compliance with the llmstxt specification.
- Created a prompt for updating markdown file indices with files from specified folders, including options for table structures and update strategies.
- Developed a prompt for updating object-oriented component documentation, following industry best practices and ensuring alignment with current implementations.
- Added a prompt for updating specification files, emphasizing clarity, structure, and compliance with established documentation standards.
* CHANGE: Update implementation plan prompt formatting
- Renamed prompt title for clarity.
- Added spacing for improved readability.
- Enhanced structure to ensure compliance with template validation rules.
* CHANGE: Fix typo in .NET best practices prompt
- Corrected "soltion" to "solution" in the prompt description.
Daniel Scott-Raynsford
