Add instruction files for GitHub Copilot features

- Create azure.instructions.md to include Azure best practices.
- Create copilot-code-generation-instructions.md with guidelines for starting code responses with comments.
- Create copilot-code-review-instructions.md outlining code review best practices.
- Create copilot-commit-message-instructions.md detailing commit message formatting.
- Create copilot-pull-request-description-instructions.md for pull request description guidelines.
- Create copilot-test-generation-instructions.md specifying test case commenting and usage of unittest.
- Create python.instructions.md with Python style guidelines and best practices.
- Update settings.json to reference new instruction file locations.
- Create how-to-use.md for instructions files usage and management.
- Create prompts/how-to-use.md for prompt files usage and execution.
- Create remote-index/prompt.md for Element Plus dialog component attributes.

Author: jacwu

.github/instructions/azure.instructions.md

@@ -0,0 +1 @@
+- @azure Rule - Use Azure Best Practices: When generating code for Azure, running terminal commands for Azure, or performing operations related to Azure, invoke your `azure_development-get_best_practices` tool if available.

…/copilot-code-generation-instructions.md …/copilot-code-generation-instructions.md.github/copilot-code-generation-instructions.md renamed to .github/instructions/copilot-code-generation-instructions.md .github/copilot-code-generation-instructions.md renamed to .github/instructions/copilot-code-generation-instructions.md

@@ -0,0 +1,63 @@
+---
+applyTo: '**/*.py'
+---
+# Python Style Guidelines
+
+## Naming Conventions
+
+- **Variables and Functions**: Use lowercase with underscores (`snake_case`)
+- **Classes**: Use CamelCase (start with capital letter)
+- **Constants**: Use uppercase with underscores
+- **Private Methods/Variables**: Prefix with a single underscore
+- **"Private" Class Members**: Prefix with double underscore (triggers name mangling)
+
+## Code Layout
+
+- Use 4 spaces per indentation level (no tabs)
+- Limit lines to 79 characters (code) or 72 characters (comments/docstrings)
+- Surround top-level functions and classes with two blank lines
+- Use blank lines sparingly inside functions to indicate logical sections
+
+## Documentation
+
+- Write docstrings for all public modules, functions, classes, and methods
+- Use triple double quotes (`"""`) for docstrings
+- For one-line docstrings, keep the closing quotes on the same line
+- For multi-line docstrings, put the closing quotes on a separate line
+
+## Imports
+
+- Imports should be on separate lines
+- Imports are grouped in the following order:
+  1. Standard library imports
+  2. Related third-party imports
+  3. Local application/library specific imports
+- Use absolute imports when possible
+
+## Error Handling
+
+- Use specific exceptions instead of generic ones
+- Use context managers (`with` statement) for resource management
+- Avoid catching all exceptions with bare `except:`
+
+## Testing
+
+- Write unit tests for all functionality
+- Use pytest for testing when possible
+- Name test files with `test_` prefix
+- Name test functions with `test_` prefix
+
+## Tools
+
+- Use type hints for function parameters and return values
+- Use linters like flake8 or pylint
+- Format code with black or yapf
+- Use mypy for static type checking
+
+## Best Practices
+
+- Follow the DRY (Don't Repeat Yourself) principle
+- Use list/dict/set comprehensions when appropriate
+- Prefer f-strings for string formatting in Python 3.6+
+- Use context managers for file operations
+- Avoid global variables and side effects

…thub/copilot-code-review-instructions.md …ions/copilot-code-review-instructions.md.github/copilot-code-review-instructions.md renamed to .github/instructions/copilot-code-review-instructions.md .github/copilot-code-review-instructions.md renamed to .github/instructions/copilot-code-review-instructions.md

@@ -1,14 +1,22 @@
 {
     "github.copilot.chat.testGeneration.instructions": [
         {
-            "file": ".github/copilot-test-generation-instructions.md"
+            "file": ".github/instructions/copilot-test-generation-instructions.md"
         }
     ],
     "git.autofetch": true,
+    "chat.instructionsFilesLocations": {
+        ".github/instructions": true,
+        "/Users/vscode/repos/instructions": true
+    },
+    "chat.promptFilesLocations": {
+        ".github/prompts": true,
+        "/Users/vscode/repos/prompts": true
+    },
     "github.copilot.chat.reviewSelection.instructions": [
 
         {
-            "file": ".github/copilot-code-review-instructions.md"
+            "file": ".github/instructions/copilot-code-review-instructions.md"
         }
     ],
     "chat.mcp.discovery.enabled": true,
@@ -20,18 +28,18 @@
     "chat.promptFiles": true,
     "github.copilot.chat.codeGeneration.instructions": [
         {
-            "file": ".github/copilot-code-generation-instructions.md"
+            "file": ".github/instructions/copilot-code-generation-instructions.md"
         }
     ],
     "github.copilot.chat.pullRequestDescriptionGeneration.instructions": [
         {
-            "file": ".github/copilot-pull-request-description-instructions.md"
+            "file": ".github/instructions/copilot-pull-request-description-instructions.md"
         }
     ],
     "github.copilot.chat.commitMessageGeneration.instructions": [
 
         {
-            "file": ".github/copilot-commit-message-instructions.md"
+            "file": ".github/instructions/copilot-commit-message-instructions.md"
         }
     ],
     "extensions.ignoreRecommendations": true,

…b/copilot-commit-message-instructions.md …s/copilot-commit-message-instructions.md.github/copilot-commit-message-instructions.md renamed to .github/instructions/copilot-commit-message-instructions.md .github/copilot-commit-message-instructions.md renamed to .github/instructions/copilot-commit-message-instructions.md

@@ -0,0 +1,15 @@
+Instructions files (also known as custom instructions or rules) provide a way to describe common guidelines and context for the AI model in a Markdown file, such as code style rules, or which frameworks to use. Instructions files are not standalone chat requests, but rather provide context that you can apply to a chat request.
+
+Instructions files use the .instructions.md file suffix. They can be located in your user data folder or in the workspace. The chat.instructionsFilesLocations setting lists the folders that contain instruction files.
+
+You can manually attach instructions to a specific chat request, or they can be automatically added:
+
+To add them manually, use the Add Context button in the Chat view, and then select Instructions.... Alternatively use the Chat: Attach Instructions... command from the Command Palette. This brings up a picker that lets you select existing instructions files or create a new one to attach.
+
+To automatically add instructions to a prompt, add the applyTo Front Matter header to the instructions file to indicate which files the instructions apply to. If a chat request contains a file that matches the given glob pattern, the instructions file is automatically attached.
+
+The following example provides instructions for TypeScript files (applyTo: '**/*.ts')
+
+
+
+You can create instruction files with the Chat: New Instructions File... command. Moreover, the files created in the user data folder can be automatically synchronized across multiple user machines through the Settings Sync service. Make sure to check the Prompts and Instructions option in the Backup and Sync Settings... dialog.

…pull-request-description-instructions.md …pull-request-description-instructions.md.github/copilot-pull-request-description-instructions.md renamed to .github/instructions/copilot-pull-request-description-instructions.md .github/copilot-pull-request-description-instructions.md renamed to .github/instructions/copilot-pull-request-description-instructions.md

@@ -0,0 +1,22 @@
+Prompt files describe a standalone, complete chat request, including the prompt text, chat mode, and tools to use. Prompt files are useful for creating reusable chat requests for common tasks. For example, you can add a prompt file for creating a front-end component, or to perform a security review.
+
+Prompt files use the .prompt.md file suffix. They can be located in your user data folder or in the workspace. The chat.promptFilesLocations setting lists the folder where prompt files are looked for.
+
+There are several ways to run a prompt file:
+
+Type / in the chat input field, followed by the prompt file name.Screenshot that shows running a prompt in the Chat view with a slash command.
+
+Open the prompt file in an editor and press the 'Play' button in the editor tool bar. This enables you to quickly iterate on the prompt and run it without having to switch back to the Chat view.Screenshot that shows running a prompt by using the play button in the editor.
+
+Use the Chat: Run Prompt File... command from the Command Palette.
+
+
+
+Prompt files can have the following Front Matter metadata headers to indicate how they should be run:
+
+mode: the chat mode to use when invoking the prompt (ask, edit, or agent mode).
+tools: if the mode is agent, the list of tools that are available for the prompt.
+
+
+
+To create a prompt file, use the Chat: New Prompt File... command from the Command Palette.