- Introduced a detailed guide covering core principles, coding standards, security practices, internationalization, performance optimization, admin UI, REST API, block development, asset loading, testing strategies, and documentation best practices.
- Emphasized the importance of following WordPress Coding Standards (WPCS) and provided examples for plugin headers, linting setup, and security measures.
- Included a checklist to ensure compliance with best practices for plugin development.
* Enhance Go development instructions with additional best practices and guidelines
* node update-readme.js
* Enhance Go development instructions with additional clarity on self-documenting code and comment practices
* Enhance package declaration guidelines in Go instructions to prevent duplicate declarations and ensure proper naming conventions
* Update WaitGroup usage instructions for Go 1.25 to include new Go method syntax
* Enhance Go development instructions by emphasizing the use of early return patterns to improve code clarity
- 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 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>
* Java 25 upgrade guide with best practices (Java 21 -> 25)
Added a description for the Java upgrade guide.
* Add Java Development Collection and Upgrade Guides
- Created a new collection for Java development, including prompts and instructions for Spring Boot, Quarkus, JPA, JUnit, and Javadoc.
- Added comprehensive markdown documentation for upgrading from Java 17 to Java 21, detailing new language features, API changes, and best practices.
- Introduced upgrade guide for transitioning from Java 21 to Java 25, highlighting new features, migration strategies, and performance considerations.
* Update upgrade guide headers and descriptions for Java 21 to 25
* Refactor Java Development Collection: Update Upgrade Guides with Descriptions
* Add Java 11 to Java 17 Upgrade Guide with best practices and migration patterns
* Rename files
* 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>
* 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>
* add instructions for accessibility
* update readme
* Added a description to the a11y instructions
* Fix spelling and formatting issues
* Fixing line ending
---------
Co-authored-by: Michael Fairchild <mfairchild@microsoft.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* feat: add task-planner, task-researcher chatmodes with accompanying task-implementation instructions
* chore: update README.md with new references to chatmodes and instructions
* Add Playwright Python test generation custom instructions
* Add best practice for assertion style in Playwright Python instructions
* Add Playwright Python test generation instructions to README
* 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>
- 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
* 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 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>
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.
