Merge upstream#2
Merged
Merged
Conversation
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.
* 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>
* 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 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>
… and optimization (#115) * 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>
* add Object Calisthenics instruction file This instruction enforces the 9 original Object Calisthenics rules for business domain code (C#, TypeScript, Java). It provides clear guidelines and examples for maintainable, robust, and clean backend code. DTOs and infrastructure code are exempted. References to original sources included. Signed-off-by: SebastienDegodez <sebastien.degodez@gmail.com> * Update instructions/object-calisthenics.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update instructions/object-calisthenics.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Signed-off-by: SebastienDegodez <sebastien.degodez@gmail.com> Co-authored-by: Matt Soucoup <masoucou@microsoft.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add TDD chatmodes * Update chatmodes/tdd-red.chatmode.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update chatmodes/tdd-green.chatmode.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
…t documentation (#113) * 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>
* Initial plan * Fix table formatting issues in Reusable Prompts section Co-authored-by: codemillmatt <2053639+codemillmatt@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: codemillmatt <2053639+codemillmatt@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>
* 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>
* Added Terraform instructions and updated README * Reverted changed to CONTRIBUTING.md --------- Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
…99) * 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 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
Co-authored-by: Aung Myo Kyaw <aungmyokyaw@users.noreply.github.com>
* 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>
…ation Prompt (#121) * feat: add comprehensive repository analysis prompt and methodology * README updated * refactor: update tools and enhance methodology for repository analysis * refactor: update command syntax for repository analysis to PowerShell format --------- Co-authored-by: Aaron Powell <me@aaron-powell.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): 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
…mpts (#136) * feat: add Prompt Builder for creating high-quality GitHub Copilot prompts * run node update-readme.js * change " to ' * fix: correct formatting of description in prompt-builder prompt
Reduce redundancy; improve coverage of excluding .env.* files.
* Add Microsoft Study and Learn chat mode * Fix update-readme.js for windows env
#131) * 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>
#132) * 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>
* 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
* Initial draft of .NET Framework instructions * Revisions and adding additional details * A few additional formatting tweaks * Update readme for .NET Framework instructions * Shorten and fix .NET Framework instructions description
* feat(chatmode): add Thinking Beast Mode chatmode with quantum cognitive workflow and constitutional agent protocol Introduce a new chatmode, 'Thinking Beast Mode', which defines a transcendent coding agent with quantum cognitive architecture, adversarial intelligence, and recursive meta-cognitive workflow. The prompt includes: - Multi-phase quantum cognitive workflow for problem solving - Constitutional, adversarial, and meta-cognitive analysis layers - Explicit instructions for recursive internet research and rigorous validation - Multi-perspective and adversarial thinking protocols - Markdown todo list framework for constitutional task management - Communication protocol for intent, process, and pattern synthesis This enables advanced autonomous agent behavior for complex, research-driven coding tasks. No breaking changes. * docs(README): add Thinking Beast Mode chatmode to chatmode table with description and install links --------- Co-authored-by: Aung Myo Kyaw <aungmyokyaw@users.noreply.github.com>
…on, and testing (#148) - 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.
…#195) * feat: Revise Blueprint Mode documentation for clarity and conciseness * feat: Update Blueprint Mode to v30 with enhanced workflows and self-correction features * fix: Correct terminology from 'todos' to 'tasks' and improve capitalization for consistency * feat: Upgrade model to GPT-5 Mini and enhance communication guidelines for brevity and clarity * feat: Update model version to GPT-4.1 and clarify critical execution guidelines * feat: Enhance Blueprint Mode with improved task handling and workflow directives * feat: Revise Blueprint Mode directives for clarity and brevity, introducing confidence-based ambiguity resolution
* Add documentation writer prompt * review: explicitly define the minimum-required tools
* Add first-ask prompt for informed task execution * Fix typos * Add mode and title * node update-readme.js
* Added instructions for Azure DevOps pipelines Added new instructions on best practices for Azure DevOps pipeline YAML files in `azure-devops-pipelines.instructions.md`. Sections include general guidelines, pipeline structure, build best practices, test integration, security considerations, deployment strategies, variable and parameter management, performance optimization, monitoring and observability, template reusability, and branching and triggering strategies. An example YAML pipeline structure and a list of common anti-patterns to avoid have also been added. * fix following the copilot's comments --------- Co-authored-by: Christophe Peugnet <christophe.peugnet@outlook.fr>
* Adding improved instructions back in * Removing duplicate line
…rs (#208) * Initial plan * Add all-contributors setup with contributor recognition Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com> * Finalize all-contributors setup and update documentation Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com> * Add @aaronpowell as a contributor * Add @mubaidr as a contributor * Add @digitarald as a contributor * Add @mbianchidev as a contributor * generating the current list * playing with emojis --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com> Co-authored-by: Aaron Powell <me@aaron-powell.com> Co-authored-by: all-contributors-bot <all-contributors-bot@example.com>
* Add C# instruction in Korean * Update README
- 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.
* Experimenting with a sub-README structure * title * removing emojis * some emoji changes * Fixing a whitespace issue
* Add clojure memory instructions and prompt * Fix typos
* Add nudge prompt for keeping the agent in repl using mode * Fix typos
* Updated the redirect url * Update update-readme.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Upload chatmode * Upload instructions * Update READMEs * Fix quotes in applyTo field in instructions * Revert other instructions
* Adding MCP Server to the README * Don't need that header * Changing summary text * Using aka.ms links * changing logo style to be consistent
* Add agents.md creation prompt * Refine description and clean up
* Add C# instruction in Japanese * change title * update README
… enhance clarity on workflows and directives. (#230) * Update Blueprint Mode documentation to reflect version 36 changes and enhance clarity on workflows and directives. * Update chatmodes/blueprint-mode.chatmode.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Refine directives in Blueprint Mode documentation for clarity and accuracy * Update Blueprint Mode documentation to version 37, enhancing clarity and detail in core directives and tool usage policies. * Update Blueprint Mode documentation to version 37, enhancing clarity on workflows and directives. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Adds Oqtane instructions file. Adds a new file containing instructions for Oqtane. This provides necessary documentation for setting up and using the Oqtane framework. * Adds instructions for Oqtane module Introduces a new file with instructions for customizing GitHub Copilot behavior for Oqtane modules. Removes the old instruction file. * Adds Oqtane module development instructions Provides instructions for customizing GitHub Copilot behavior for Oqtane module development, including code style, naming conventions, error handling, and performance optimization. * Update instructions/oqtane.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update instructions/oqtane.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update instructions/oqtane.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update instructions/oqtane.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update instructions/oqtane.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update instructions/oqtane.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Adding to readme Don't know why the github action wasn't picking it up --------- Co-authored-by: DAVIS Mark E <Mark.DAVIS@lanecountyor.gov> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Aaron Powell <me@aaron-powell.com>
* Create Azure Bicep coding specialist chat mode Added a new chat mode for Azure Bicep Infrastructure as Code coding specialization, detailing key tasks, pre-flight checks, testing, validation, and final checks. * Create bicep-plan chatmode for Azure planning Added a new chatmode for Azure Bicep Infrastructure planning, detailing requirements, focus areas, and implementation plan structure. * updated readme * PR feedback * PR feedback about quotes
stevewithington
pushed a commit
that referenced
this pull request
Apr 14, 2026
…te-build skills (github#899) * feat: add flowstudio-power-automate-debug and flowstudio-power-automate-build skills Two companion skills for the FlowStudio Power Automate MCP server: - flowstudio-power-automate-debug: Debug workflow for failed Power Automate cloud flow runs - flowstudio-power-automate-build: Build & deploy flows from natural language descriptions Both require a FlowStudio MCP subscription: https://flowstudio.app These complement the existing flowstudio-power-automate-mcp skill (merged in PR github#896). * fix: address all review comments — README, cross-refs, response shapes, step numbering - Add skills to docs/README.skills.md (fixes validate-readme CI check) - Update cross-skill references to use flowstudio- prefix (#1, github#4, github#7, github#9) - Fix get_live_flow_run_action_outputs: returns array, index [0] (#2, #3) - Renumber Step 6→5, Step 7→6 — remove gap in build workflow (github#8) - Fix connectionName note: it's the key, not the GUID (github#10) - Remove invalid arrow function from Filter array expression (github#11) * feat: add flowstudio-power-automate plugin bundling all 3 skills Plugin bundles: - flowstudio-power-automate-mcp (core connection & CRUD) - flowstudio-power-automate-debug (debug failed runs) - flowstudio-power-automate-build (build & deploy flows) Install: copilot plugin install flowstudio-power-automate@awesome-copilot Per @aaronpowell's suggestion in review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
node update-readme.jsand verified thatREADME.mdis up to date.Description
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.