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