From b1f3346ef2d05f445b19a46bfeaeb887010b323d Mon Sep 17 00:00:00 2001 From: Aaron Powell Date: Fri, 13 Mar 2026 13:45:17 +1100 Subject: [PATCH] content review (#995) * Cleaned up some tool names * Removing some instructionsThese instructions are no longer useful as the knowledge the add is already well handled by frontier models, so the instructions potentially provide conflicting or incorrect information to the agent while it undertakes a task * Improved the skill to be more explicit on how to use playwright * Removing a skill that is of low value The information captured in this skill is mostly just what is found in the links that are at the top of the references, and thus the model will already have that knowledge available to it, meaning that the skill will potentially provide conflicting guidance to the agent as it works * Updating readmes --- agents/csharp-dotnet-janitor.agent.md | 2 +- agents/janitor.agent.md | 2 +- docs/README.instructions.md | 6 - docs/README.skills.md | 3 +- instructions/angular.instructions.md | 104 - instructions/java.instructions.md | 81 - instructions/python.instructions.md | 56 - instructions/reactjs.instructions.md | 162 -- .../typescript-5-es2022.instructions.md | 114 - instructions/vuejs3.instructions.md | 153 -- skills/create-web-form/SKILL.md | 85 - .../references/accessibility.md | 512 ---- .../references/aria-form-role.md | 156 -- .../create-web-form/references/css-styling.md | 1027 ------- .../create-web-form/references/form-basics.md | 451 --- .../references/form-controls.md | 851 ------ .../references/form-data-handling.md | 627 ----- .../references/html-form-elements.md | 822 ------ .../references/html-form-example.md | 990 ------- .../references/hypertext-transfer-protocol.md | 1227 --------- .../create-web-form/references/javascript.md | 2413 ----------------- .../create-web-form/references/php-cookies.md | 145 - .../create-web-form/references/php-forms.md | 601 ---- skills/create-web-form/references/php-json.md | 202 -- .../references/php-mysql-database.md | 1696 ------------ .../references/progressive-web-app.md | 211 -- .../references/python-as-web-framework.md | 567 ---- .../references/python-contact-form.md | 453 ---- .../references/python-flask-app.md | 449 --- .../references/python-flask.md | 432 --- skills/create-web-form/references/security.md | 136 - .../references/styling-web-forms.md | 1643 ----------- skills/create-web-form/references/web-api.md | 165 -- .../references/web-performance.md | 974 ------- skills/create-web-form/references/xml.md | 366 --- skills/webapp-testing/SKILL.md | 39 +- .../{ => assets}/test-helper.js | 0 37 files changed, 31 insertions(+), 17892 deletions(-) delete mode 100644 instructions/angular.instructions.md delete mode 100644 instructions/java.instructions.md delete mode 100644 instructions/python.instructions.md delete mode 100644 instructions/reactjs.instructions.md delete mode 100644 instructions/typescript-5-es2022.instructions.md delete mode 100644 instructions/vuejs3.instructions.md delete mode 100644 skills/create-web-form/SKILL.md delete mode 100644 skills/create-web-form/references/accessibility.md delete mode 100644 skills/create-web-form/references/aria-form-role.md delete mode 100644 skills/create-web-form/references/css-styling.md delete mode 100644 skills/create-web-form/references/form-basics.md delete mode 100644 skills/create-web-form/references/form-controls.md delete mode 100644 skills/create-web-form/references/form-data-handling.md delete mode 100644 skills/create-web-form/references/html-form-elements.md delete mode 100644 skills/create-web-form/references/html-form-example.md delete mode 100644 skills/create-web-form/references/hypertext-transfer-protocol.md delete mode 100644 skills/create-web-form/references/javascript.md delete mode 100644 skills/create-web-form/references/php-cookies.md delete mode 100644 skills/create-web-form/references/php-forms.md delete mode 100644 skills/create-web-form/references/php-json.md delete mode 100644 skills/create-web-form/references/php-mysql-database.md delete mode 100644 skills/create-web-form/references/progressive-web-app.md delete mode 100644 skills/create-web-form/references/python-as-web-framework.md delete mode 100644 skills/create-web-form/references/python-contact-form.md delete mode 100644 skills/create-web-form/references/python-flask-app.md delete mode 100644 skills/create-web-form/references/python-flask.md delete mode 100644 skills/create-web-form/references/security.md delete mode 100644 skills/create-web-form/references/styling-web-forms.md delete mode 100644 skills/create-web-form/references/web-api.md delete mode 100644 skills/create-web-form/references/web-performance.md delete mode 100644 skills/create-web-form/references/xml.md rename skills/webapp-testing/{ => assets}/test-helper.js (100%) diff --git a/agents/csharp-dotnet-janitor.agent.md b/agents/csharp-dotnet-janitor.agent.md index 4ab83815..858f55bd 100644 --- a/agents/csharp-dotnet-janitor.agent.md +++ b/agents/csharp-dotnet-janitor.agent.md @@ -1,7 +1,7 @@ --- description: 'Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.' name: 'C#/.NET Janitor' -tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github'] +tools: [vscode/extensions, vscode/getProjectSetupInfo, vscode/installExtension, vscode/newWorkspace, vscode/runCommand, vscode/vscodeAPI, execute/getTerminalOutput, execute/runTask, execute/createAndRunTask, execute/runTests, execute/runInTerminal, execute/testFailure, read/terminalSelection, read/terminalLastCommand, read/getTaskOutput, read/problems, read/readFile, 'github/*', 'microsoft.docs.mcp/*', edit/editFiles, search, web] --- # C#/.NET Janitor diff --git a/agents/janitor.agent.md b/agents/janitor.agent.md index 5a2f6400..42fb9258 100644 --- a/agents/janitor.agent.md +++ b/agents/janitor.agent.md @@ -1,7 +1,7 @@ --- description: 'Perform janitorial tasks on any codebase including cleanup, simplification, and tech debt remediation.' name: 'Universal Janitor' -tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'vscode/extensions', 'web/fetch', 'findTestFiles', 'web/githubRepo', 'vscode/getProjectSetupInfo', 'vscode/installExtension', 'vscode/newWorkspace', 'vscode/runCommand', 'vscode/openSimpleBrowser', 'read/problems', 'execute/getTerminalOutput', 'execute/runInTerminal', 'read/terminalLastCommand', 'read/terminalSelection', 'execute/createAndRunTask', 'execute/getTaskOutput', 'execute/runTask', 'execute/runTests', 'search', 'search/searchResults', 'execute/testFailure', 'search/usages', 'vscode/vscodeAPI', 'microsoft.docs.mcp', 'github'] +tools: [vscode/extensions, vscode/getProjectSetupInfo, vscode/installExtension, vscode/newWorkspace, vscode/runCommand, vscode/vscodeAPI, execute/getTerminalOutput, execute/runTask, execute/createAndRunTask, execute/runTests, execute/runInTerminal, execute/testFailure, read/terminalSelection, read/terminalLastCommand, read/getTaskOutput, read/problems, read/readFile, browser, 'github/*', 'microsoft.docs.mcp/*', edit/editFiles, search, web] --- # Universal Janitor diff --git a/docs/README.instructions.md b/docs/README.instructions.md index f50183be..671ac8e3 100644 --- a/docs/README.instructions.md +++ b/docs/README.instructions.md @@ -25,7 +25,6 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [Agent Safety & Governance](../instructions/agent-safety.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fagent-safety.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fagent-safety.instructions.md) | Guidelines for building safe, governed AI agent systems. Apply when writing code that uses agent frameworks, tool-calling LLMs, or multi-agent orchestration to ensure proper safety boundaries, policy enforcement, and auditability. | | [Agent Skills File Guidelines](../instructions/agent-skills.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fagent-skills.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fagent-skills.instructions.md) | Guidelines for creating high-quality Agent Skills for GitHub Copilot | | [AI Prompt Engineering & Safety Best Practices](../instructions/ai-prompt-engineering-safety-best-practices.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fai-prompt-engineering-safety-best-practices.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fai-prompt-engineering-safety-best-practices.instructions.md) | Comprehensive best practices for AI prompt engineering, safety frameworks, bias mitigation, and responsible AI usage for Copilot and LLMs. | -| [Angular Development Instructions](../instructions/angular.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fangular.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fangular.instructions.md) | Angular-specific coding standards and best practices | | [Ansible Conventions and Best Practices](../instructions/ansible.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fansible.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fansible.instructions.md) | Ansible conventions and best practices | | [Apex Development](../instructions/apex.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fapex.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fapex.instructions.md) | Guidelines and best practices for Apex development on the Salesforce Platform | | [Arch Linux Administration Guidelines](../instructions/arch-linux.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Farch-linux.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Farch-linux.instructions.md) | Guidance for Arch Linux administration, pacman workflows, and rolling-release best practices. | @@ -107,7 +106,6 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [Java 11 to Java 17 Upgrade Guide](../instructions/java-11-to-java-17-upgrade.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-11-to-java-17-upgrade.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-11-to-java-17-upgrade.instructions.md) | Comprehensive best practices for adopting new Java 17 features since the release of Java 11. | | [Java 17 to Java 21 Upgrade Guide](../instructions/java-17-to-java-21-upgrade.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-17-to-java-21-upgrade.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-17-to-java-21-upgrade.instructions.md) | Comprehensive best practices for adopting new Java 21 features since the release of Java 17. | | [Java 21 to Java 25 Upgrade Guide](../instructions/java-21-to-java-25-upgrade.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-21-to-java-25-upgrade.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-21-to-java-25-upgrade.instructions.md) | Comprehensive best practices for adopting new Java 25 features since the release of Java 21. | -| [Java Development](../instructions/java.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava.instructions.md) | Guidelines for building Java base applications | | [Java MCP Server Development Guidelines](../instructions/java-mcp-server.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-mcp-server.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjava-mcp-server.instructions.md) | Best practices and patterns for building Model Context Protocol (MCP) servers in Java using the official MCP Java SDK with reactive streams and Spring integration. | | [Joyride User Scripts Project Assistant](../instructions/joyride-user-project.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjoyride-user-project.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjoyride-user-project.instructions.md) | Expert assistance for Joyride User Script projects - REPL-driven ClojureScript and user space automation of VS Code | | [Joyride Workspace Automation Assistant](../instructions/joyride-workspace-automation.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjoyride-workspace-automation.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fjoyride-workspace-automation.instructions.md) | Expert assistance for Joyride Workspace automation - REPL-driven and user space ClojureScript automation within specific VS Code workspaces | @@ -153,13 +151,11 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [PowerShell Cmdlet Development Guidelines](../instructions/powershell.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell.instructions.md) | PowerShell cmdlet and scripting best practices based on Microsoft guidelines | | [PowerShell Pester v5 Testing Guidelines](../instructions/powershell-pester-5.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell-pester-5.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell-pester-5.instructions.md) | PowerShell Pester testing best practices based on Pester v5 conventions | | [Project Context](../instructions/moodle.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmoodle.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmoodle.instructions.md) | Instructions for GitHub Copilot to generate code in a Moodle project context. | -| [Python Coding Conventions](../instructions/python.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython.instructions.md) | Python coding conventions and guidelines | | [Python MCP Server Development](../instructions/python-mcp-server.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython-mcp-server.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython-mcp-server.instructions.md) | Instructions for building Model Context Protocol (MCP) servers using the Python SDK | | [Quarkus](../instructions/quarkus.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fquarkus.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fquarkus.instructions.md) | Quarkus development standards and instructions | | [Quarkus MCP Server](../instructions/quarkus-mcp-server-sse.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fquarkus-mcp-server-sse.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fquarkus-mcp-server-sse.instructions.md) | Quarkus and MCP Server with HTTP SSE transport development standards and instructions | | [R Programming Language Instructions](../instructions/r.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fr.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fr.instructions.md) | R language and document formats (R, Rmd, Quarto): coding standards and Copilot guidance for idiomatic, safe, and consistent code generation. | | [React Controls & Platform Libraries](../instructions/pcf-react-platform-libraries.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-react-platform-libraries.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-react-platform-libraries.instructions.md) | React controls and platform libraries for PCF components | -| [ReactJS Development Instructions](../instructions/reactjs.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Freactjs.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Freactjs.instructions.md) | ReactJS development standards and best practices | | [Ruby MCP Server Development Guidelines](../instructions/ruby-mcp-server.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fruby-mcp-server.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fruby-mcp-server.instructions.md) | Best practices and patterns for building Model Context Protocol (MCP) servers in Ruby using the official MCP Ruby SDK gem. | | [Ruby on Rails](../instructions/ruby-on-rails.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fruby-on-rails.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fruby-on-rails.instructions.md) | Ruby on Rails coding conventions and guidelines | | [Rust Coding Conventions and Best Practices](../instructions/rust.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Frust.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Frust.instructions.md) | Rust programming language coding conventions and best practices | @@ -183,7 +179,6 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [TaskSync V5 Protocol](../instructions/tasksync.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftasksync.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftasksync.instructions.md) | TaskSync V5 - Allows you to give the agent new instructions or feedback after completing a task using terminal while agent is running. | | [Terraform Conventions](../instructions/terraform.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fterraform.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fterraform.instructions.md) | Terraform Conventions and Guidelines | | [Terraform on SAP BTP – Best Practices & Conventions](../instructions/terraform-sap-btp.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fterraform-sap-btp.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fterraform-sap-btp.instructions.md) | Terraform conventions and guidelines for SAP Business Technology Platform (SAP BTP). | -| [TypeScript Development](../instructions/typescript-5-es2022.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftypescript-5-es2022.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftypescript-5-es2022.instructions.md) | Guidelines for TypeScript Development targeting TypeScript 5.x and ES2022 output | | [TypeScript MCP Server Development](../instructions/typescript-mcp-server.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftypescript-mcp-server.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftypescript-mcp-server.instructions.md) | Instructions for building Model Context Protocol (MCP) servers using the TypeScript SDK | | [TypeSpec for Microsoft 365 Copilot Development Guidelines](../instructions/typespec-m365-copilot.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftypespec-m365-copilot.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftypespec-m365-copilot.instructions.md) | Guidelines and best practices for building TypeSpec-based declarative agents and API plugins for Microsoft 365 Copilot | | [Update Code from Shorthand](../instructions/update-code-from-shorthand.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fupdate-code-from-shorthand.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fupdate-code-from-shorthand.instructions.md) | Shorthand code will be in the file provided from the prompt or raw data in the prompt, and will be used to update the code file when the prompt has the text `UPDATE CODE FROM SHORTHAND`. | @@ -191,6 +186,5 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [Upgrading from .NET MAUI 9 to .NET MAUI 10](../instructions/dotnet-maui-9-to-dotnet-maui-10-upgrade.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-maui-9-to-dotnet-maui-10-upgrade.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-maui-9-to-dotnet-maui-10-upgrade.instructions.md) | Instructions for upgrading .NET MAUI applications from version 9 to version 10, including breaking changes, deprecated APIs, and migration strategies for ListView to CollectionView. | | [Use Code Components in Power Pages](../instructions/pcf-power-pages.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-power-pages.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-power-pages.instructions.md) | Using code components in Power Pages sites | | [Visual Studio Extension Development with Community.VisualStudio.Toolkit](../instructions/vsixtoolkit.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvsixtoolkit.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvsixtoolkit.instructions.md) | Guidelines for Visual Studio extension (VSIX) development using Community.VisualStudio.Toolkit | -| [VueJS 3 Development Instructions](../instructions/vuejs3.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvuejs3.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvuejs3.instructions.md) | VueJS 3 development standards and best practices with Composition API and TypeScript | | [WinUI 3 / Windows App SDK](../instructions/winui3.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwinui3.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwinui3.instructions.md) | WinUI 3 and Windows App SDK coding guidelines. Prevents common UWP API misuse, enforces correct XAML namespaces, threading, windowing, and MVVM patterns for desktop Windows apps. | | [WordPress Development — Copilot Instructions](../instructions/wordpress.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwordpress.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwordpress.instructions.md) | Coding, security, and testing rules for WordPress plugins and themes | diff --git a/docs/README.skills.md b/docs/README.skills.md index d9b1a621..fa97cb2f 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -86,7 +86,6 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to | [create-spring-boot-kotlin-project](../skills/create-spring-boot-kotlin-project/SKILL.md) | Create Spring Boot Kotlin Project Skeleton | None | | [create-technical-spike](../skills/create-technical-spike/SKILL.md) | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. | None | | [create-tldr-page](../skills/create-tldr-page/SKILL.md) | Create a tldr page from documentation URLs and command examples, requiring both URL and command name. | None | -| [create-web-form](../skills/create-web-form/SKILL.md) | Create robust, accessible web forms with best practices for HTML structure, CSS styling, JavaScript interactivity, form validation, and server-side processing. Use when asked to "create a form", "build a web form", "add a contact form", "make a signup form", or when building any HTML form with data handling. Covers PHP and Python backends, MySQL database integration, REST APIs, XML data exchange, accessibility (ARIA), and progressive web apps. | `references/accessibility.md`
`references/aria-form-role.md`
`references/css-styling.md`
`references/form-basics.md`
`references/form-controls.md`
`references/form-data-handling.md`
`references/html-form-elements.md`
`references/html-form-example.md`
`references/hypertext-transfer-protocol.md`
`references/javascript.md`
`references/php-cookies.md`
`references/php-forms.md`
`references/php-json.md`
`references/php-mysql-database.md`
`references/progressive-web-app.md`
`references/python-as-web-framework.md`
`references/python-contact-form.md`
`references/python-flask-app.md`
`references/python-flask.md`
`references/security.md`
`references/styling-web-forms.md`
`references/web-api.md`
`references/web-performance.md`
`references/xml.md` | | [creating-oracle-to-postgres-master-migration-plan](../skills/creating-oracle-to-postgres-master-migration-plan/SKILL.md) | Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies. | None | | [creating-oracle-to-postgres-migration-bug-report](../skills/creating-oracle-to-postgres-migration-bug-report/SKILL.md) | Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps. | `references/BUG-REPORT-TEMPLATE.md` | | [creating-oracle-to-postgres-migration-integration-tests](../skills/creating-oracle-to-postgres-migration-integration-tests/SKILL.md) | Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests. | None | @@ -242,7 +241,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to | [vscode-ext-localization](../skills/vscode-ext-localization/SKILL.md) | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices | None | | [web-coder](../skills/web-coder/SKILL.md) | Expert 10x engineer with comprehensive knowledge of web development, internet protocols, and web standards. Use when working with HTML, CSS, JavaScript, web APIs, HTTP/HTTPS, web security, performance optimization, accessibility, or any web/internet concepts. Specializes in translating web terminology accurately and implementing modern web standards across frontend and backend development. | `references/accessibility.md`
`references/architecture-patterns.md`
`references/browsers-engines.md`
`references/css-styling.md`
`references/data-formats-encoding.md`
`references/development-tools.md`
`references/glossary.md`
`references/html-markup.md`
`references/http-networking.md`
`references/javascript-programming.md`
`references/media-graphics.md`
`references/performance-optimization.md`
`references/security-authentication.md`
`references/servers-infrastructure.md`
`references/web-apis-dom.md`
`references/web-protocols-standards.md` | | [web-design-reviewer](../skills/web-design-reviewer/SKILL.md) | This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level. | `references/framework-fixes.md`
`references/visual-checklist.md` | -| [webapp-testing](../skills/webapp-testing/SKILL.md) | Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. | `test-helper.js` | +| [webapp-testing](../skills/webapp-testing/SKILL.md) | Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. | `assets/test-helper.js` | | [what-context-needed](../skills/what-context-needed/SKILL.md) | Ask Copilot what files it needs to see before answering a question | None | | [winapp-cli](../skills/winapp-cli/SKILL.md) | Windows App Development CLI (winapp) for building, packaging, and deploying Windows applications. Use when asked to initialize Windows app projects, create MSIX packages, generate AppxManifest.xml, manage development certificates, add package identity for debugging, sign packages, publish to the Microsoft Store, create external catalogs, or access Windows SDK build tools. Supports .NET (csproj), C++, Electron, Rust, Tauri, and cross-platform frameworks targeting Windows. | None | | [winmd-api-search](../skills/winmd-api-search/SKILL.md) | Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values). | `LICENSE.txt`
`scripts/Invoke-WinMdQuery.ps1`
`scripts/Update-WinMdCache.ps1`
`scripts/cache-generator` | diff --git a/instructions/angular.instructions.md b/instructions/angular.instructions.md deleted file mode 100644 index 12b7355a..00000000 --- a/instructions/angular.instructions.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -description: 'Angular-specific coding standards and best practices' -applyTo: '**/*.ts, **/*.html, **/*.scss, **/*.css' ---- - -# Angular Development Instructions - -Instructions for generating high-quality Angular applications with TypeScript, using Angular Signals for state management, adhering to Angular best practices as outlined at https://angular.dev. - -## Project Context -- Latest Angular version (use standalone components by default) -- TypeScript for type safety -- Angular CLI for project setup and scaffolding -- Follow Angular Style Guide (https://angular.dev/style-guide) -- Use Angular Material or other modern UI libraries for consistent styling (if specified) - -## Development Standards - -### Architecture -- Use standalone components unless modules are explicitly required -- Organize code by standalone feature modules or domains for scalability -- Implement lazy loading for feature modules to optimize performance -- Use Angular's built-in dependency injection system effectively -- Structure components with a clear separation of concerns (smart vs. presentational components) - -### TypeScript -- Enable strict mode in `tsconfig.json` for type safety -- Define clear interfaces and types for components, services, and models -- Use type guards and union types for robust type checking -- Implement proper error handling with RxJS operators (e.g., `catchError`) -- Use typed forms (e.g., `FormGroup`, `FormControl`) for reactive forms - -### Component Design -- Follow Angular's component lifecycle hooks best practices -- When using Angular >= 19, Use `input()` `output()`, `viewChild()`, `viewChildren()`, `contentChild()` and `contentChildren()` functions instead of decorators; otherwise use decorators -- Leverage Angular's change detection strategy (default or `OnPush` for performance) -- Keep templates clean and logic in component classes or services -- Use Angular directives and pipes for reusable functionality - -### Styling -- Use Angular's component-level CSS encapsulation (default: ViewEncapsulation.Emulated) -- Prefer SCSS for styling with consistent theming -- Implement responsive design using CSS Grid, Flexbox, or Angular CDK Layout utilities -- Follow Angular Material's theming guidelines if used -- Maintain accessibility (a11y) with ARIA attributes and semantic HTML - -### State Management -- Use Angular Signals for reactive state management in components and services -- Leverage `signal()`, `computed()`, and `effect()` for reactive state updates -- Use writable signals for mutable state and computed signals for derived state -- Handle loading and error states with signals and proper UI feedback -- Use Angular's `AsyncPipe` to handle observables in templates when combining signals with RxJS - -### Data Fetching -- Use Angular's `HttpClient` for API calls with proper typing -- Implement RxJS operators for data transformation and error handling -- Use Angular's `inject()` function for dependency injection in standalone components -- Implement caching strategies (e.g., `shareReplay` for observables) -- Store API response data in signals for reactive updates -- Handle API errors with global interceptors for consistent error handling - -### Security -- Sanitize user inputs using Angular's built-in sanitization -- Implement route guards for authentication and authorization -- Use Angular's `HttpInterceptor` for CSRF protection and API authentication headers -- Validate form inputs with Angular's reactive forms and custom validators -- Follow Angular's security best practices (e.g., avoid direct DOM manipulation) - -### Performance -- Enable production builds with `ng build --prod` for optimization -- Use lazy loading for routes to reduce initial bundle size -- Optimize change detection with `OnPush` strategy and signals for fine-grained reactivity -- Use trackBy in `ngFor` loops to improve rendering performance -- Implement server-side rendering (SSR) or static site generation (SSG) with Angular Universal (if specified) - -### Testing -- Write unit tests for components, services, and pipes using Jasmine and Karma -- Use Angular's `TestBed` for component testing with mocked dependencies -- Test signal-based state updates using Angular's testing utilities -- Write end-to-end tests with Cypress or Playwright (if specified) -- Mock HTTP requests using `provideHttpClientTesting` -- Ensure high test coverage for critical functionality - -## Implementation Process -1. Plan project structure and feature modules -2. Define TypeScript interfaces and models -3. Scaffold components, services, and pipes using Angular CLI -4. Implement data services and API integrations with signal-based state -5. Build reusable components with clear inputs and outputs -6. Add reactive forms and validation -7. Apply styling with SCSS and responsive design -8. Implement lazy-loaded routes and guards -9. Add error handling and loading states using signals -10. Write unit and end-to-end tests -11. Optimize performance and bundle size - -## Additional Guidelines -- Follow the Angular Style Guide for file naming conventions (see https://angular.dev/style-guide), e.g., use `feature.ts` for components and `feature-service.ts` for services. For legacy codebases, maintain consistency with existing pattern. -- Use Angular CLI commands for generating boilerplate code -- Document components and services with clear JSDoc comments -- Ensure accessibility compliance (WCAG 2.1) where applicable -- Use Angular's built-in i18n for internationalization (if specified) -- Keep code DRY by creating reusable utilities and shared modules -- Use signals consistently for state management to ensure reactive updates diff --git a/instructions/java.instructions.md b/instructions/java.instructions.md deleted file mode 100644 index 7a4258e1..00000000 --- a/instructions/java.instructions.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -description: 'Guidelines for building Java base applications' -applyTo: '**/*.java' ---- - -# Java Development - -## General Instructions - -- First, prompt the user if they want to integrate static analysis tools (SonarQube, PMD, Checkstyle) into their project setup. - - If yes, document a recommended static-analysis setup. - - Prefer SonarQube/SonarCloud (SonarLint in IDE + `sonar-scanner` in CI). - - Create a Sonar project key. - - Store the scanner token in CI secrets. - - Provide a sample CI job that runs the scanner. - - If the team declines Sonar, note this in the project README and continue. - - If Sonar is bound to the project: - - Use Sonar as the primary source of actionable issues. - - Reference Sonar rule keys in remediation guidance. - - If Sonar is unavailable: - - Perform up to 3 troubleshooting checks: - 1. Verify project binding and token. - 2. Ensure SonarScanner runs in CI. - 3. Confirm SonarLint is installed and configured. - - If still failing after 3 attempts: - - Enable SpotBugs, PMD, or Checkstyle as CI fallbacks. - - Open a short tracker issue documenting the blocker and next steps. -- If the user declines static analysis tools or wants to proceed without them, continue with implementing the Best practices, bug patterns and code smell prevention guidelines outlined below. -- Address code smells proactively during development rather than accumulating technical debt. -- Focus on readability, maintainability, and performance when refactoring identified issues. -- Use IDE / Code editor reported warnings and suggestions to catch common patterns early in development. - -## Best practices - -- **Records**: For classes primarily intended to store data (e.g., DTOs, immutable data structures), **Java Records should be used instead of traditional classes**. -- **Pattern Matching**: Utilize pattern matching for `instanceof` and `switch` expression to simplify conditional logic and type casting. -- **Type Inference**: Use `var` for local variable declarations to improve readability, but only when the type is explicitly clear from the right-hand side of the expression. -- **Immutability**: Favor immutable objects. Make classes and fields `final` where possible. Use collections from `List.of()`/`Map.of()` for fixed data. Use `Stream.toList()` to create immutable lists. -- **Streams and Lambdas**: Use the Streams API and lambda expressions for collection processing. Employ method references (e.g., `stream.map(Foo::toBar)`). -- **Null Handling**: Avoid returning or accepting `null`. Use `Optional` for possibly-absent values and `Objects` utility methods like `equals()` and `requireNonNull()`. - -### Naming Conventions - -- Follow Google's Java style guide: - - `UpperCamelCase` for class and interface names. - - `lowerCamelCase` for method and variable names. - - `UPPER_SNAKE_CASE` for constants. - - `lowercase` for package names. -- Use nouns for classes (`UserService`) and verbs for methods (`getUserById`). -- Avoid abbreviations and Hungarian notation. - -### Common Bug Patterns - -Below are concise, human-readable rules you can apply regardless of which static analysis tool you use. If you run Sonar/SonarLint, the IDE will show the matching rule and location — direct Sonar connections are preferred and should override this ruleset. - -- Resource management — Always close resources (files, sockets, streams). Use try-with-resources where possible so resources are closed automatically. -- Equality checks — Compare object equality with `.equals()` or `Objects.equals(...)` rather than `==` for non-primitives; this avoids reference-equality bugs. -- Redundant casts — Remove unnecessary casts; prefer correct generic typing and let the compiler infer types where possible. -- Reachable conditions — Avoid conditional expressions that are always true or false; they indicate bugs or dead code and should be corrected. - -For contributors who *do* use Sonar or SonarLint: the IDE/scan will show the specific rule key (for example, S2095 for resource leaks) and the affected file/line. Use that information to navigate to the exact location, then apply the recommended remediation. - -### Common Code Smells - -These patterns are phrased for humans; they map cleanly to checks in Sonar, SpotBugs, PMD, or Checkstyle but do not require those tools to be useful. - -- Parameter count — Keep method parameter lists short. If a method needs many params, consider grouping into a value object or using the builder pattern. -- Method size — Keep methods focused and small. Extract helper methods to improve readability and testability. -- Cognitive complexity — Reduce nested conditionals and heavy branching by extracting methods, using polymorphism, or applying the Strategy pattern. -- Duplicated literals — Extract repeated strings and numbers into named constants or enums to reduce errors and ease changes. -- Dead code — Remove unused variables and assignments. They confuse readers and can hide bugs. -- Magic numbers — Replace numeric literals with named constants that explain intent (e.g., MAX_RETRIES). - -If you run a static analyzer like Sonar or SonarLint — direct Sonar connections are preferred and should override this ruleset. Sonar rule keys are useful for automation and suppression, but they are not required in day-to-day developer guidance. - -## Build and Verification - -- After adding or modifying code, verify the project continues to build successfully. -- If the project uses Maven, run `mvn clean install`. -- If the project uses Gradle, run `./gradlew build` (or `gradlew.bat build` on Windows). -- Ensure all tests pass as part of the build. diff --git a/instructions/python.instructions.md b/instructions/python.instructions.md deleted file mode 100644 index a783f424..00000000 --- a/instructions/python.instructions.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -description: 'Python coding conventions and guidelines' -applyTo: '**/*.py' ---- - -# Python Coding Conventions - -## Python Instructions - -- Write clear and concise comments for each function. -- Ensure functions have descriptive names and include type hints. -- Provide docstrings following PEP 257 conventions. -- Use the `typing` module for type annotations (e.g., `List[str]`, `Dict[str, int]`). -- Break down complex functions into smaller, more manageable functions. - -## General Instructions - -- Always prioritize readability and clarity. -- For algorithm-related code, include explanations of the approach used. -- Write code with good maintainability practices, including comments on why certain design decisions were made. -- Handle edge cases and write clear exception handling. -- For libraries or external dependencies, mention their usage and purpose in comments. -- Use consistent naming conventions and follow language-specific best practices. -- Write concise, efficient, and idiomatic code that is also easily understandable. - -## Code Style and Formatting - -- Follow the **PEP 8** style guide for Python. -- Maintain proper indentation (use 4 spaces for each level of indentation). -- Ensure lines do not exceed 79 characters. -- Place function and class docstrings immediately after the `def` or `class` keyword. -- Use blank lines to separate functions, classes, and code blocks where appropriate. - -## Edge Cases and Testing - -- Always include test cases for critical paths of the application. -- Account for common edge cases like empty inputs, invalid data types, and large datasets. -- Include comments for edge cases and the expected behavior in those cases. -- Write unit tests for functions and document them with docstrings explaining the test cases. - -## Example of Proper Documentation - -```python -def calculate_area(radius: float) -> float: - """ - Calculate the area of a circle given the radius. - - Parameters: - radius (float): The radius of the circle. - - Returns: - float: The area of the circle, calculated as π * radius^2. - """ - import math - return math.pi * radius ** 2 -``` diff --git a/instructions/reactjs.instructions.md b/instructions/reactjs.instructions.md deleted file mode 100644 index 79bd2754..00000000 --- a/instructions/reactjs.instructions.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -description: 'ReactJS development standards and best practices' -applyTo: '**/*.jsx, **/*.tsx, **/*.js, **/*.ts, **/*.css, **/*.scss' ---- - -# ReactJS Development Instructions - -Instructions for building high-quality ReactJS applications with modern patterns, hooks, and best practices following the official React documentation at https://react.dev. - -## Project Context -- Latest React version (React 19+) -- TypeScript for type safety (when applicable) -- Functional components with hooks as default -- Follow React's official style guide and best practices -- Use modern build tools (Vite, Create React App, or custom Webpack setup) -- Implement proper component composition and reusability patterns - -## Development Standards - -### Architecture -- Use functional components with hooks as the primary pattern -- Implement component composition over inheritance -- Organize components by feature or domain for scalability -- Separate presentational and container components clearly -- Use custom hooks for reusable stateful logic -- Implement proper component hierarchies with clear data flow - -### TypeScript Integration -- Use TypeScript interfaces for props, state, and component definitions -- Define proper types for event handlers and refs -- Implement generic components where appropriate -- Use strict mode in `tsconfig.json` for type safety -- Leverage React's built-in types (`React.FC`, `React.ComponentProps`, etc.) -- Create union types for component variants and states - -### Component Design -- Follow the single responsibility principle for components -- Use descriptive and consistent naming conventions -- Implement proper prop validation with TypeScript or PropTypes -- Design components to be testable and reusable -- Keep components small and focused on a single concern -- Use composition patterns (render props, children as functions) - -### State Management -- Use `useState` for local component state -- Implement `useReducer` for complex state logic -- Leverage `useContext` for sharing state across component trees -- Consider external state management (Redux Toolkit, Zustand) for complex applications -- Implement proper state normalization and data structures -- Use React Query or SWR for server state management - -### Hooks and Effects -- Use `useEffect` with proper dependency arrays to avoid infinite loops -- Implement cleanup functions in effects to prevent memory leaks -- Use `useMemo` and `useCallback` for performance optimization when needed -- Create custom hooks for reusable stateful logic -- Follow the rules of hooks (only call at the top level) -- Use `useRef` for accessing DOM elements and storing mutable values - -### Styling -- Use CSS Modules, Styled Components, or modern CSS-in-JS solutions -- Implement responsive design with mobile-first approach -- Follow BEM methodology or similar naming conventions for CSS classes -- Use CSS custom properties (variables) for theming -- Implement consistent spacing, typography, and color systems -- Ensure accessibility with proper ARIA attributes and semantic HTML - -### Performance Optimization -- Use `React.memo` for component memoization when appropriate -- Implement code splitting with `React.lazy` and `Suspense` -- Optimize bundle size with tree shaking and dynamic imports -- Use `useMemo` and `useCallback` judiciously to prevent unnecessary re-renders -- Implement virtual scrolling for large lists -- Profile components with React DevTools to identify performance bottlenecks - -### Data Fetching -- Use modern data fetching libraries (React Query, SWR, Apollo Client) -- Implement proper loading, error, and success states -- Handle race conditions and request cancellation -- Use optimistic updates for better user experience -- Implement proper caching strategies -- Handle offline scenarios and network errors gracefully - -### Error Handling -- Implement Error Boundaries for component-level error handling -- Use proper error states in data fetching -- Implement fallback UI for error scenarios -- Log errors appropriately for debugging -- Handle async errors in effects and event handlers -- Provide meaningful error messages to users - -### Forms and Validation -- Use controlled components for form inputs -- Implement proper form validation with libraries like Formik, React Hook Form -- Handle form submission and error states appropriately -- Implement accessibility features for forms (labels, ARIA attributes) -- Use debounced validation for better user experience -- Handle file uploads and complex form scenarios - -### Routing -- Use React Router for client-side routing -- Implement nested routes and route protection -- Handle route parameters and query strings properly -- Implement lazy loading for route-based code splitting -- Use proper navigation patterns and back button handling -- Implement breadcrumbs and navigation state management - -### Testing -- Write unit tests for components using React Testing Library -- Test component behavior, not implementation details -- Use Jest for test runner and assertion library -- Implement integration tests for complex component interactions -- Mock external dependencies and API calls appropriately -- Test accessibility features and keyboard navigation - -### Security -- Sanitize user inputs to prevent XSS attacks -- Validate and escape data before rendering -- Use HTTPS for all external API calls -- Implement proper authentication and authorization patterns -- Avoid storing sensitive data in localStorage or sessionStorage -- Use Content Security Policy (CSP) headers - -### Accessibility -- Use semantic HTML elements appropriately -- Implement proper ARIA attributes and roles -- Ensure keyboard navigation works for all interactive elements -- Provide alt text for images and descriptive text for icons -- Implement proper color contrast ratios -- Test with screen readers and accessibility tools - -## Implementation Process -1. Plan component architecture and data flow -2. Set up project structure with proper folder organization -3. Define TypeScript interfaces and types -4. Implement core components with proper styling -5. Add state management and data fetching logic -6. Implement routing and navigation -7. Add form handling and validation -8. Implement error handling and loading states -9. Add testing coverage for components and functionality -10. Optimize performance and bundle size -11. Ensure accessibility compliance -12. Add documentation and code comments - -## Additional Guidelines -- Follow React's naming conventions (PascalCase for components, camelCase for functions) -- Use meaningful commit messages and maintain clean git history -- Implement proper code splitting and lazy loading strategies -- Document complex components and custom hooks with JSDoc -- Use ESLint and Prettier for consistent code formatting -- Keep dependencies up to date and audit for security vulnerabilities -- Implement proper environment configuration for different deployment stages -- Use React Developer Tools for debugging and performance analysis - -## Common Patterns -- Higher-Order Components (HOCs) for cross-cutting concerns -- Render props pattern for component composition -- Compound components for related functionality -- Provider pattern for context-based state sharing -- Container/Presentational component separation -- Custom hooks for reusable logic extraction diff --git a/instructions/typescript-5-es2022.instructions.md b/instructions/typescript-5-es2022.instructions.md deleted file mode 100644 index 1b530353..00000000 --- a/instructions/typescript-5-es2022.instructions.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -description: 'Guidelines for TypeScript Development targeting TypeScript 5.x and ES2022 output' -applyTo: '**/*.ts' ---- - -# TypeScript Development - -> These instructions assume projects are built with TypeScript 5.x (or newer) compiling to an ES2022 JavaScript baseline. Adjust guidance if your runtime requires older language targets or down-level transpilation. - -## Core Intent - -- Respect the existing architecture and coding standards. -- Prefer readable, explicit solutions over clever shortcuts. -- Extend current abstractions before inventing new ones. -- Prioritize maintainability and clarity, short methods and classes, clean code. - -## General Guardrails - -- Target TypeScript 5.x / ES2022 and prefer native features over polyfills. -- Use pure ES modules; never emit `require`, `module.exports`, or CommonJS helpers. -- Rely on the project's build, lint, and test scripts unless asked otherwise. -- Note design trade-offs when intent is not obvious. - -## Project Organization - -- Follow the repository's folder and responsibility layout for new code. -- Use kebab-case filenames (e.g., `user-session.ts`, `data-service.ts`) unless told otherwise. -- Keep tests, types, and helpers near their implementation when it aids discovery. -- Reuse or extend shared utilities before adding new ones. - -## Naming & Style - -- Use PascalCase for classes, interfaces, enums, and type aliases; camelCase for everything else. -- Skip interface prefixes like `I`; rely on descriptive names. -- Name things for their behavior or domain meaning, not implementation. - -## Formatting & Style - -- Run the repository's lint/format scripts (e.g., `npm run lint`) before submitting. -- Match the project's indentation, quote style, and trailing comma rules. -- Keep functions focused; extract helpers when logic branches grow. -- Favor immutable data and pure functions when practical. - -## Type System Expectations - -- Avoid `any` (implicit or explicit); prefer `unknown` plus narrowing. -- Use discriminated unions for realtime events and state machines. -- Centralize shared contracts instead of duplicating shapes. -- Express intent with TypeScript utility types (e.g., `Readonly`, `Partial`, `Record`). - -## Async, Events & Error Handling - -- Use `async/await`; wrap awaits in try/catch with structured errors. -- Guard edge cases early to avoid deep nesting. -- Send errors through the project's logging/telemetry utilities. -- Surface user-facing errors via the repository's notification pattern. -- Debounce configuration-driven updates and dispose resources deterministically. - -## Architecture & Patterns - -- Follow the repository's dependency injection or composition pattern; keep modules single-purpose. -- Observe existing initialization and disposal sequences when wiring into lifecycles. -- Keep transport, domain, and presentation layers decoupled with clear interfaces. -- Supply lifecycle hooks (e.g., `initialize`, `dispose`) and targeted tests when adding services. - -## External Integrations - -- Instantiate clients outside hot paths and inject them for testability. -- Never hardcode secrets; load them from secure sources. -- Apply retries, backoff, and cancellation to network or IO calls. -- Normalize external responses and map errors to domain shapes. - -## Security Practices - -- Validate and sanitize external input with schema validators or type guards. -- Avoid dynamic code execution and untrusted template rendering. -- Encode untrusted content before rendering HTML; use framework escaping or trusted types. -- Use parameterized queries or prepared statements to block injection. -- Keep secrets in secure storage, rotate them regularly, and request least-privilege scopes. -- Favor immutable flows and defensive copies for sensitive data. -- Use vetted crypto libraries only. -- Patch dependencies promptly and monitor advisories. - -## Configuration & Secrets - -- Reach configuration through shared helpers and validate with schemas or dedicated validators. -- Handle secrets via the project's secure storage; guard `undefined` and error states. -- Document new configuration keys and update related tests. - -## UI & UX Components - -- Sanitize user or external content before rendering. -- Keep UI layers thin; push heavy logic to services or state managers. -- Use messaging or events to decouple UI from business logic. - -## Testing Expectations - -- Add or update unit tests with the project's framework and naming style. -- Expand integration or end-to-end suites when behavior crosses modules or platform APIs. -- Run targeted test scripts for quick feedback before submitting. -- Avoid brittle timing assertions; prefer fake timers or injected clocks. - -## Performance & Reliability - -- Lazy-load heavy dependencies and dispose them when done. -- Defer expensive work until users need it. -- Batch or debounce high-frequency events to reduce thrash. -- Track resource lifetimes to prevent leaks. - -## Documentation & Comments - -- Add JSDoc to public APIs; include `@remarks` or `@example` when helpful. -- Write comments that capture intent, and remove stale notes during refactors. -- Update architecture or design docs when introducing significant patterns. diff --git a/instructions/vuejs3.instructions.md b/instructions/vuejs3.instructions.md deleted file mode 100644 index 879cf2c2..00000000 --- a/instructions/vuejs3.instructions.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -description: 'VueJS 3 development standards and best practices with Composition API and TypeScript' -applyTo: '**/*.vue, **/*.ts, **/*.js, **/*.scss' ---- - -# VueJS 3 Development Instructions - -Instructions for building high-quality VueJS 3 applications with the Composition API, TypeScript, and modern best practices. - -## Project Context -- Vue 3.x with Composition API as default -- TypeScript for type safety -- Single File Components (`.vue`) with ` -``` - ---- - -## `` - -> **Source:** - -### Description - -The `` element displays a progress indicator showing the completion of a task, typically rendered as a progress bar. - -### Key Attributes - -| Attribute | Description | -|-----------|-------------| -| `max` | Total amount of work required. Must be greater than 0 and a valid floating-point number. Default: `1`. | -| `value` | Completed amount (0 to `max`, or 0 to 1 if `max` is omitted). If omitted, shows an indeterminate progress bar. | - -### Difference from `` - -- Minimum value is always 0 (the `min` attribute is **not allowed** for ``). -- `` is specifically for task completion; `` is for scalar measurements. - -### Usage Notes - -- Both opening and closing tags are required. -- Implicit ARIA role: `progressbar`. -- Text between tags is fallback content for older browsers (not an accessible label). -- Use the `:indeterminate` pseudo-class to style indeterminate progress bars. -- Remove the `value` attribute (`element.removeAttribute('value')`) to make an indeterminate progress bar. - -### Accessibility Considerations - -- Always provide an accessible label using a `