* feat: Update Blueprint Mode to v16 with enhanced directives and workflows
- Changed model from Claude Sonnet 4 to GPT-4.1.
- Revised description for clarity and conciseness.
- Expanded communication guidelines for improved task management.
- Enhanced quality and engineering protocols, emphasizing SOLID principles and documentation.
- Introduced new execution principles to streamline task execution and reflection.
- Updated artifact structure to include specifications for requirements, architecture, and edge cases.
- Refined workflows for better task handling and validation processes.
- Improved debugging strategies and handling of ambiguous requests.
* refactor: streamline communication guidelines and core directives in Blueprint Mode documentation
* 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>
* docs(instructions): add conventional commit prompt and document in README
* docs(readme,conventional-commit-prompt): clarify Conventional Commit prompt description and improve prompt front matter
Updated README.md to clarify the Conventional Commit prompt description and details. Updated instructions/conventional-commit.prompt.md to improve front matter (description, tools) and remove unnecessary fields.
* docs(prompt): simplify XML structure and remove redundant tags
---------
Co-authored-by: Aung Myo Kyaw <aungmyokyaw@users.noreply.github.com>
* feat(docs): add Blueprint Mode v1 chat mode and documentation
Add Blueprint Mode v1 chat mode instructions and entry to README.
Blueprint Mode introduces specification-first engineering workflow,
artifact management standards, and escalation protocols for autonomous
agent development.
* docs(chatmode): improve formatting and clarify execution policy
- update tools list for accuracy and consistency
- enhance formatting in design and steering documents for readability
- clarify execution policy and internet research instructions
- fix minor markdown and wording issues
* docs(chatmode): add critical execution rules and update tools list
Add mandatory execution instructions and include runTests in tools for blueprint-mode chat mode.
* feat(chatmode): update Blueprint Mode to v2 with enhanced self-sufficient engineering directives and improved documentation
* fix(chatmode): correct formatting of tools list in Blueprint Mode documentation
* feat(blueprint-mode): update Blueprint Mode to v3 with enhanced directives and improved clarity
* fix(blueprint-mode): correct numbering format in main and lightweight workflows
* feat(blueprint-mode): enhance Core Directives with continuation and task review mandates
* feat(blueprint-mode): update Blueprint Mode to v4 with enhanced directives and improved clarity
* feat(docs): update Blueprint Mode documentation to v5 with enhanced directives and workflows
* fix(docs): refine thinking process directive for clarity and completeness
* feat(docs): update Blueprint Mode documentation from v5 to v6 with revised file paths and workflow steps
* feat(docs): update Blueprint Mode documentation to v6 with enhanced agent instructions
* feat(docs): enhance Blueprint Mode directives with self-reflection and retry strategies
* feat(docs): update Blueprint Mode documentation to v7 with enhanced task management and artifact tracking
* feat(docs): update Blueprint Mode documentation to v8 with enhanced specifications and directives
* feat(docs): update Blueprint Mode documentation to v9 with enhanced directives for task workflows and artifact management
* feat(docs): update artifact paths in Blueprint Mode documentation to reflect new directory structure
* feat(docs): update Blueprint Mode documentation from v9 to v10 with enhanced directives and workflow details
* feat(docs): update Blueprint Mode documentation from v10 to v11 with enhanced directives and tool usage guidelines
* feat(docs): update Blueprint Mode documentation to v12 with enhanced directives and workflow details
* feat(docs): add Blueprint Mode v1 chat mode and documentation
Add Blueprint Mode v1 chat mode instructions and entry to README.
Blueprint Mode introduces specification-first engineering workflow,
artifact management standards, and escalation protocols for autonomous
agent development.
* docs(chatmode): improve formatting and clarify execution policy
- update tools list for accuracy and consistency
- enhance formatting in design and steering documents for readability
- clarify execution policy and internet research instructions
- fix minor markdown and wording issues
* docs(chatmode): add critical execution rules and update tools list
Add mandatory execution instructions and include runTests in tools for blueprint-mode chat mode.
* feat(chatmode): update Blueprint Mode to v2 with enhanced self-sufficient engineering directives and improved documentation
* fix(chatmode): correct formatting of tools list in Blueprint Mode documentation
* feat(blueprint-mode): update Blueprint Mode to v3 with enhanced directives and improved clarity
* fix(blueprint-mode): correct numbering format in main and lightweight workflows
* feat(blueprint-mode): enhance Core Directives with continuation and task review mandates
* feat(blueprint-mode): update Blueprint Mode to v4 with enhanced directives and improved clarity
* feat: add tasks.json with task to generate README file (closes#106)
* chore: set tasks.json version to 1.0.0 as requested
* chore(tasks): update tasks.json version to 2.0.0 for VS Code compatibility
---------
Co-authored-by: Aung Myo Kyaw <aungmyokyaw@users.noreply.github.com>
- Add comprehensive NestJS instructions covering DI, modular architecture, and decorators
- Include project structure recommendations and naming conventions
- Cover API development patterns, database integration, and authentication
- Add testing strategies, performance optimization, and security best practices
- Update README.md with new NestJS instructions entry
* 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>
* Adding an action to invoke webhooks
This will allow external tools to be notified when there are updates on the main branch so they can request the data from the repo
* Addressing some feedback
* Changing the log messages
* Cleaning up log message
* Update .github/workflows/webhook-caller.yml
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update .github/workflows/webhook-caller.yml
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update .github/workflows/webhook-caller.yml
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* 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>
* 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>
* adding working skeleton of WPF instructions
* adding updated readme
* Fixing final newline
* based on code review
Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
---------
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>
Introduced a new document outlining best practices for building, structuring, and maintaining Next.js applications. This guide is intended for LLMs and developers to ensure code quality, maintainability, and scalability, covering project structure, component integration, naming conventions, API routes, and general best practices.
* 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
* feat: Add comprehensive AI Prompt Engineering & Safety Best Practices
- Add 868-line instruction file covering prompt engineering fundamentals, safety, bias mitigation, security, and responsible AI usage
- Add 527-line expert chat mode for prompt analysis and improvement with systematic evaluation frameworks
- Include detailed templates, checklists, examples, and educational resources
- Follow industry best practices from Microsoft, OpenAI, and Google AI principles
- Implement comprehensive safety assessment frameworks and bias detection tools
- Add advanced techniques: prompt chaining, templates, versioning, and testing frameworks
- Provide extensive references to official guidelines, research papers, and community resources
- Strictly comply with project guidelines (CONTRIBUTING.md, SECURITY.md, SUPPORT.md)
Total: 1,395 lines of professional-grade prompt engineering guidance
* feat: add comprehensive AI prompt engineering safety best practices instruction
- Add 868-line comprehensive instruction file covering prompt engineering fundamentals
- Include safety frameworks, bias mitigation, security best practices, and responsible AI usage
- Provide detailed templates, checklists, and testing methodologies
- Cover anti-patterns, prompt injection prevention, and ethical considerations
- Add educational content on prompt patterns, validation techniques, and documentation
- Include practical examples and real-world scenarios for developers
- Rename file to avoid conflict with existing prompt-engineer chat mode
- Update README with new instruction file
This instruction provides developers with industry-standard best practices for creating safe, effective, and responsible AI prompts for Copilot and other LLMs.
* fix: restore original prompt-engineer chat mode to match upstream
- Restore the original prompt-engineer.chatmode.md from upstream/main
- Remove overwritten comprehensive version to avoid duplication and conflict
- Ensure only the official, simple prompt engineer chat mode is present
All advanced prompt engineering best practices are now in the new instruction file only.
* chore: regenerate README after restoring original prompt engineer chat mode
- Re-run update-readme.js to ensure only the correct, original description for prompt-engineer.chatmode.md is present
- Remove any duplicate or outdated descriptions from previous comprehensive version
- README is now fully in sync with the restored chat mode and current repo state
* feat: add comprehensive AI prompt engineering safety review prompt
- Add 150+ line prompt file for AI prompt engineering safety review and improvement
- Include systematic analysis framework covering safety, bias, security, and effectiveness
- Provide structured output format with detailed assessment criteria
- Include safety guidelines, testing recommendations, and educational insights
- Complement the existing AI prompt engineering safety best practices instruction
- Follow repository guidelines and best practices for prompt creation
This prompt enables developers to systematically review and improve prompts for safety, bias mitigation, security, and responsible AI usage.
* feat: expand AI prompt engineering safety review prompt with comprehensive analysis
- Expand prompt from basic to comprehensive 200+ line analysis framework
- Add advanced pattern analysis covering zero-shot, few-shot, chain-of-thought, role-based patterns
- Include technical robustness assessment (input validation, error handling, scalability)
- Add performance optimization metrics (token efficiency, response quality, consistency)
- Enhance output format with detailed scoring and assessment criteria
- Include bias mitigation strategies, security enhancements, and technical improvements
- Provide extensive testing recommendations and educational insights
- Follow repository guidelines for comprehensive, actionable prompt content
This expanded prompt provides developers with a thorough, systematic approach to prompt safety review and improvement.
* Add comprehensive guidelines for DDD and .NET best practices
* docs: update docs to include new instructions
* fix: resolve typo in description of DDD and .NET architecture guidelines
* docs: run update-readme.js
