* 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.
- 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
