Updated prompts for .NET upgrade analysis, enhancing project classification, dependency review, and upgrade strategy sections. Added new prompts for CI/CD updates, testing, and documentation.
This document provides a comprehensive set of prompts for analyzing, planning, executing, and validating framework upgrades for multi-project .NET solutions, covering various aspects from project discovery to final validation.
* Add Power BI resources: 4 chat modes, 6 instructions, 4 prompts, and resources README
* Remove power-bi-resources-README.md - not needed for PR
* Add Power BI Development collection
* Fix PR review feedback: Add collection YAML file and remove double fenced code blocks
- Add power-bi-development.collection.yml with proper metadata
- Remove outer 4-backtick fences from all Power BI files (chatmodes, instructions, prompts)
- Files now have only the standard 3-backtick fences for proper GitHub Copilot compatibility
* Remove outer code fences from Power BI chatmode files
* Add files via upload
* Revise Power Apps Code App project scaffolding
Update project scaffolding instructions for Power Apps Code Apps with PAC CLI setup, SDK integration, and connector configuration.
* Update Power Apps Code App scaffolding prompt
* Revise development instructions for Power Apps Code Apps
Update Power Apps Code Apps development instructions with new standards and best practices for TypeScript, React, and Power Platform integration.
* Update Power Platform expert chatmode with new details
* Revise Power Apps Code App project scaffold
Update project scaffolding details and add advanced patterns.
* Fixing line endings
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
- 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
* Fix project name placeholders and update descriptions in Spring Boot project prompts
* Update Spring Boot project prompts to clarify project creation instructions
---------
Co-authored-by: Vincent Huang iMac <vincent.huang@opennet.tw>
* Add `/remember` prompt
The `/remember` prompt is a keeper of memories and lessons learnt during chat sessions. Inspired by Beastmode's `remember` feature.
* Fix typo
- 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.
* Initial plan
* Add mode: 'agent' to all 14 prompt files missing the field, fix BOM character
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
* Revert description field format changes while keeping mode field additions
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
* docs(prompt): add EditorConfig Expert prompt for .editorconfig generation
Adds a new prompt definition that guides the generation of comprehensive .editorconfig files based on project analysis and user preferences, including rule-by-rule explanations and best practices.
* docs(readme): add EditorConfig Expert prompt entry with description and install links
---------
Co-authored-by: Aung Myo Kyaw <aungmyokyaw@users.noreply.github.com>
* Add a comprehensive prompt for containerizing ASP.NET Core projects
This prompt instructs the LLM to conatinerize an ASP.NET Core project
according to ASP.NET Core best practices with flexibility to support a
wide range of possible project customization requirements (including
installing system dependencies, dotnet tools, or other pre-requisites
for the app to work in a container).
* Update readme with ASP.NET Core containerization prompt
* Fix settings file's name
* Combine containerization settings into containerization prompt
* Emphasize that Copilot needs to review its work and check that containerization settings have been respected
- Introduced a detailed Epic Architecture Specification prompt to guide technical architecture creation based on PRDs.
- Created an Epic Product Requirements Document (PRD) prompt for translating high-level ideas into detailed PRDs.
- Developed a Feature Implementation Plan prompt for crafting implementation plans following the Epoch monorepo structure.
- Added a Feature PRD prompt for generating detailed PRDs for new features based on parent Epics.
- Implemented a GitHub Issue Planning and Automation prompt for generating project plans with a structured hierarchy and automated tracking.
- Established a Test Planning and Quality Assurance prompt for creating comprehensive test strategies and quality validation plans.
* feat(prompts): add Git Flow branch creator prompt with full XML-driven workflow
Introduces a new prompt file that guides users through creating Git Flow branches using a structured XML analysis and naming convention. Includes workflow, analysis framework, naming conventions, edge case handling, and validation checklist.
* feat(prompts): add Git Flow Branch Creator prompt to README table
* style(prompts): use single quotes in front matter for git-flow-branch-creator.prompt.md
* Update prompts/git-flow-branch-creator.prompt.md
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* chore(prompts): update git-flow-branch-creator prompt front matter
Remove 'Created' field
Add 'tools' field to front matter for clarity
* docs(readme): clarify Git Flow Branch Creator prompt description and details
---------
Co-authored-by: Aung Myo Kyaw <aungmyokyaw@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* Add Playwright MCP prompts and chat modes for testing and automation
* Update prompts/playwright-generate-test.prompt.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Enhance Playwright prompts and chatmode descriptions for clarity and consistency
* Add model specification to Playwright tester chatmode
* Update model specification in Playwright test generation prompt
* Add description to Playwright test generation prompt
* Refactor Playwright tools list in prompts and chat modes to remove redundant entries as just adding playwright seems to be supported now
* Fix typo in Playwright tester responsibilities section
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* add 7 technology-agnostic blueprint generators for project documentation that helps GitHub Copilot to generate instructions that respect project-specific conventions
- Add architecture-blueprint-generator for documenting system design patterns
- Add code-exemplars-blueprint-generator for identifying quality code standards
- Add copilot-instructions-blueprint-generator for creating AI guidance files
- Add folder-structure-blueprint-generator for documenting project organization
- Add project-workflow-blueprint-generator for end-to-end process documentation
- Add readme-blueprint-generator for comprehensive repository documentation
- Add technology-stack-blueprint-generator for tech stack analysis
* Update README.md
* Update architecture-blueprint-generator.prompt.md
Fixed : The description field in the front matter should be wrapped in single quotes, not double quotes, according to the coding guidelines.
* Update folder-structure-blueprint-generator.prompt.md
Fixed : The description field in the front matter should be wrapped in single quotes, not double quotes, according to the coding guidelines.
* Update project-workflow-analysis-blueprint-generator.prompt.md
Fixed : The description field in the front matter should be wrapped in single quotes, not double quotes, according to the coding guidelines.
* Update readme-blueprint-generator.prompt.md
Fixed : The description field in the front matter should be wrapped in single quotes, not double quotes, according to the coding guidelines.
* update readme and fixed copilot suggestions
---------
Co-authored-by: Ajay Singh <ajay.singh@compunnel.com>
* ms-sql-dba.chatmode
* update-readme.js changes
* more refining
* add instructions file
* adress missed changes and apply suggestions
* Add comprehensive SQL and PostgreSQL prompt collection
- Add sql-code-review.prompt.md: Universal SQL code review for security, maintainability, and quality standards
- Add sql-optimization.prompt.md: Universal SQL performance optimization for query tuning and indexing
- Add postgresql-code-review.prompt.md: PostgreSQL-specific code review focusing on PG best practices and anti-patterns
- Add postgresql-optimization.prompt.md: PostgreSQL-specific development assistant for unique PG features (JSONB, arrays, custom types)
This creates a complete 4-prompt ecosystem with zero overlap:
- Universal SQL (code quality + performance) for cross-database compatibility
- PostgreSQL-specific (code quality + performance) for PG-exclusive features
Each prompt serves distinct, isolated purposes while complementing each other for comprehensive SQL development support.
* enhance: Add comprehensive descriptions and model testing info
- Enhanced all 4 prompt descriptions with detailed capability coverage
- Added tested_with: 'GitHub Copilot Chat (GPT-4o)' to all prompts
- Specified database coverage (MySQL, PostgreSQL, SQL Server, Oracle)
- Detailed feature coverage for each prompt's unique capabilities
- Updated README.md with enhanced descriptions
Addresses PR review feedback for comprehensive descriptions and model testing specification.
* Enhance SQL and PostgreSQL prompts with comprehensive descriptions and testing validation
- Added detailed descriptions for all four prompts explaining their specific purposes
- Enhanced technical depth with comprehensive coverage areas
- Added testing validation with GitHub Copilot Chat (GPT-4o) - Validated July 20, 2025
- Improved frontmatter documentation for better discoverability
- Ensured zero functional overlap between Universal SQL and PostgreSQL-specific prompts
- Completed 4-prompt ecosystem: Code Quality Performance for both Universal SQL and PostgreSQL
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
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>
* feat: add C# TUnit testing prompt template
- Added csharp-tunit.prompt.md with structured prompt template
- Provides testing guidelines and best practices for C# development using TUnit framework
- Includes comprehensive testing patterns for .NET projects
* docs: add TUnit entry to README.md
- Added TUnit Best Practices entry after NUnit and before XUnit
- References prompts/csharp-tunit.prompt.md with proper description
- Includes VS Code and VS Code Insiders installation badges
* move: relocate TUnit prompt to prompts directory
- Move csharp-tunit.prompt.md from root to prompts/ directory
- Follow established project organization pattern
- All prompt files should be in the prompts directory
