Merge branch 'main' into nischays/add-custom-chat-mode-atlassian-jira
This commit is contained in:
commit
cfb7ae1d47
4
.github/workflows/validate-readme.yml
vendored
4
.github/workflows/validate-readme.yml
vendored
@ -7,6 +7,7 @@ on:
|
|||||||
- "instructions/**"
|
- "instructions/**"
|
||||||
- "prompts/**"
|
- "prompts/**"
|
||||||
- "chatmodes/**"
|
- "chatmodes/**"
|
||||||
|
- "collections/**"
|
||||||
- "*.js"
|
- "*.js"
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
@ -26,6 +27,9 @@ jobs:
|
|||||||
with:
|
with:
|
||||||
node-version: "20"
|
node-version: "20"
|
||||||
|
|
||||||
|
- name: Validate collections
|
||||||
|
run: node validate-collections.js
|
||||||
|
|
||||||
- name: Update README.md
|
- name: Update README.md
|
||||||
run: node update-readme.js
|
run: node update-readme.js
|
||||||
|
|
||||||
|
|||||||
84
.schemas/collection.schema.json
Normal file
84
.schemas/collection.schema.json
Normal file
@ -0,0 +1,84 @@
|
|||||||
|
{
|
||||||
|
"$schema": "http://json-schema.org/draft-07/schema#",
|
||||||
|
"title": "Collection Manifest",
|
||||||
|
"description": "Schema for awesome-copilot collection manifest files",
|
||||||
|
"type": "object",
|
||||||
|
"required": ["id", "name", "description", "items"],
|
||||||
|
"additionalProperties": false,
|
||||||
|
"properties": {
|
||||||
|
"id": {
|
||||||
|
"type": "string",
|
||||||
|
"description": "Unique identifier for the collection",
|
||||||
|
"pattern": "^[a-z0-9-]+$",
|
||||||
|
"minLength": 1,
|
||||||
|
"maxLength": 50
|
||||||
|
},
|
||||||
|
"name": {
|
||||||
|
"type": "string",
|
||||||
|
"description": "Display name for the collection",
|
||||||
|
"minLength": 1,
|
||||||
|
"maxLength": 100
|
||||||
|
},
|
||||||
|
"description": {
|
||||||
|
"type": "string",
|
||||||
|
"description": "Description of what this collection contains",
|
||||||
|
"minLength": 1,
|
||||||
|
"maxLength": 500
|
||||||
|
},
|
||||||
|
"tags": {
|
||||||
|
"type": "array",
|
||||||
|
"description": "Optional tags for discovery",
|
||||||
|
"items": {
|
||||||
|
"type": "string",
|
||||||
|
"pattern": "^[a-z0-9-]+$",
|
||||||
|
"minLength": 1,
|
||||||
|
"maxLength": 30
|
||||||
|
},
|
||||||
|
"uniqueItems": true,
|
||||||
|
"maxItems": 10
|
||||||
|
},
|
||||||
|
"items": {
|
||||||
|
"type": "array",
|
||||||
|
"description": "List of items in this collection",
|
||||||
|
"minItems": 1,
|
||||||
|
"maxItems": 50,
|
||||||
|
"items": {
|
||||||
|
"type": "object",
|
||||||
|
"required": ["path", "kind"],
|
||||||
|
"additionalProperties": false,
|
||||||
|
"properties": {
|
||||||
|
"path": {
|
||||||
|
"type": "string",
|
||||||
|
"description": "Relative path from repository root to the item file",
|
||||||
|
"pattern": "^(prompts|instructions|chatmodes)\/[^\/]+\\.(prompt|instructions|chatmode)\\.md$",
|
||||||
|
"minLength": 1
|
||||||
|
},
|
||||||
|
"kind": {
|
||||||
|
"type": "string",
|
||||||
|
"description": "Type of the item",
|
||||||
|
"enum": ["prompt", "instruction", "chat-mode"]
|
||||||
|
}
|
||||||
|
}
|
||||||
|
},
|
||||||
|
"uniqueItems": true
|
||||||
|
},
|
||||||
|
"display": {
|
||||||
|
"type": "object",
|
||||||
|
"description": "Optional display settings for the collection",
|
||||||
|
"additionalProperties": false,
|
||||||
|
"properties": {
|
||||||
|
"ordering": {
|
||||||
|
"type": "string",
|
||||||
|
"description": "How to order items in the collection",
|
||||||
|
"enum": ["manual", "alpha"],
|
||||||
|
"default": "alpha"
|
||||||
|
},
|
||||||
|
"show_badge": {
|
||||||
|
"type": "boolean",
|
||||||
|
"description": "Whether to show collection badge on items",
|
||||||
|
"default": false
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
39
.vscode/tasks.json
vendored
39
.vscode/tasks.json
vendored
@ -4,13 +4,50 @@
|
|||||||
{
|
{
|
||||||
"label": "generate-readme",
|
"label": "generate-readme",
|
||||||
"type": "shell",
|
"type": "shell",
|
||||||
"command": "node update-readme.js",
|
"command": "node ${workspaceFolder}/update-readme.js",
|
||||||
"problemMatcher": [],
|
"problemMatcher": [],
|
||||||
"group": {
|
"group": {
|
||||||
"kind": "build",
|
"kind": "build",
|
||||||
"isDefault": true
|
"isDefault": true
|
||||||
},
|
},
|
||||||
"detail": "Generates the README.md file using update-readme.js script."
|
"detail": "Generates the README.md file using update-readme.js script."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"label": "validate-collections",
|
||||||
|
"type": "shell",
|
||||||
|
"command": "node ${workspaceFolder}/validate-collections.js",
|
||||||
|
"problemMatcher": [],
|
||||||
|
"group": "build",
|
||||||
|
"detail": "Validates all collection manifest files."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"label": "create-collection",
|
||||||
|
"type": "shell",
|
||||||
|
"command": "node",
|
||||||
|
"args": [
|
||||||
|
"${workspaceFolder}/create-collection.js",
|
||||||
|
"--id",
|
||||||
|
"${input:collectionId}",
|
||||||
|
"--tags",
|
||||||
|
"${input:tags}"
|
||||||
|
],
|
||||||
|
"problemMatcher": [],
|
||||||
|
"group": "build",
|
||||||
|
"detail": "Creates a new collection manifest template."
|
||||||
|
}
|
||||||
|
],
|
||||||
|
"inputs": [
|
||||||
|
{
|
||||||
|
"id": "collectionId",
|
||||||
|
"description": "Collection ID (lowercase, hyphen-separated)",
|
||||||
|
"default": "my-collection",
|
||||||
|
"type": "promptString"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"id": "tags",
|
||||||
|
"description": "Comma separated list of tags",
|
||||||
|
"default": "tag1,tag2",
|
||||||
|
"type": "promptString"
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|||||||
@ -100,6 +100,48 @@ You are an expert [domain/role] with deep knowledge in [specific areas].
|
|||||||
- [Best practices to follow]
|
- [Best practices to follow]
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Adding Collections
|
||||||
|
|
||||||
|
Collections group related prompts, instructions, and chat modes around specific themes or workflows, making it easier for users to discover and adopt comprehensive toolkits.
|
||||||
|
|
||||||
|
1. **Create your collection manifest**: Add a new `.collection.yml` file in the `collections/` directory
|
||||||
|
2. **Follow the naming convention**: Use descriptive, lowercase filenames with hyphens (e.g., `python-web-development.collection.yml`)
|
||||||
|
3. **Reference existing items**: Collections should only reference files that already exist in the repository
|
||||||
|
4. **Test your collection**: Verify all referenced files exist and work well together
|
||||||
|
|
||||||
|
#### Creating a collection:
|
||||||
|
```bash
|
||||||
|
# Using the creation script
|
||||||
|
node create-collection.js my-collection-id
|
||||||
|
|
||||||
|
# Or using VS Code Task: Ctrl+Shift+P > "Tasks: Run Task" > "create-collection"
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Example collection format:
|
||||||
|
```yaml
|
||||||
|
id: my-collection-id
|
||||||
|
name: My Collection Name
|
||||||
|
description: A brief description of what this collection provides and who should use it.
|
||||||
|
tags: [tag1, tag2, tag3] # Optional discovery tags
|
||||||
|
items:
|
||||||
|
- path: prompts/my-prompt.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: instructions/my-instructions.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: chatmodes/my-chatmode.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
display:
|
||||||
|
ordering: alpha # or "manual" to preserve order above
|
||||||
|
show_badge: false # set to true to show collection badge
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Collection Guidelines:
|
||||||
|
- **Focus on workflows**: Group items that work together for specific use cases
|
||||||
|
- **Reasonable size**: Typically 3-10 items work well
|
||||||
|
- **Test combinations**: Ensure the items complement each other effectively
|
||||||
|
- **Clear purpose**: The collection should solve a specific problem or workflow
|
||||||
|
- **Validate before submitting**: Run `node validate-collections.js` to ensure your manifest is valid
|
||||||
|
|
||||||
## Submitting Your Contribution
|
## Submitting Your Contribution
|
||||||
|
|
||||||
1. **Fork this repository**
|
1. **Fork this repository**
|
||||||
|
|||||||
@ -28,11 +28,12 @@ Custom chat modes define specific behaviors and tools for GitHub Copilot Chat, e
|
|||||||
| [Azure AVM Terraform mode](chatmodes/azure-verified-modules-terraform.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-terraform.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-terraform.chatmode.md) | Create, update, or review Azure IaC in Terraform using Azure Verified Modules (AVM). |
|
| [Azure AVM Terraform mode](chatmodes/azure-verified-modules-terraform.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-terraform.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-terraform.chatmode.md) | Create, update, or review Azure IaC in Terraform using Azure Verified Modules (AVM). |
|
||||||
| [Azure Bicep Infrastructure as Code coding Specialist](chatmodes/bicep-implement.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-implement.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-implement.chatmode.md) | Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates. |
|
| [Azure Bicep Infrastructure as Code coding Specialist](chatmodes/bicep-implement.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-implement.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-implement.chatmode.md) | Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates. |
|
||||||
| [Azure Bicep Infrastructure Planning](chatmodes/bicep-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-plan.chatmode.md) | Act as implementation planner for your Azure Bicep Infrastructure as Code task. |
|
| [Azure Bicep Infrastructure Planning](chatmodes/bicep-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fbicep-plan.chatmode.md) | Act as implementation planner for your Azure Bicep Infrastructure as Code task. |
|
||||||
| [Blueprint Mode v37](chatmodes/blueprint-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fblueprint-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fblueprint-mode.chatmode.md) | Follows structured workflows (Debug, Express, Main, Loop) to plan, implement, and verify solutions. Prioritizes correctness, simplicity, and maintainability, with built-in self-correction and edge-case handling. |
|
| [Blueprint Mode v38](chatmodes/blueprint-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fblueprint-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fblueprint-mode.chatmode.md) | Executes structured workflows (Debug, Express, Main, Loop) with strict correctness and maintainability. Enforces an improved tool usage policy, never assumes facts, prioritizes reproducible solutions, self-correction, and edge-case handling. |
|
||||||
| [Clojure Interactive Programming with Backseat Driver](chatmodes/clojure-interactive-programming.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fclojure-interactive-programming.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fclojure-interactive-programming.chatmode.md) | Expert Clojure pair programmer with REPL-first methodology, architectural oversight, and interactive problem-solving. Enforces quality standards, prevents workarounds, and develops solutions incrementally through live REPL evaluation before file modifications. |
|
| [Clojure Interactive Programming with Backseat Driver](chatmodes/clojure-interactive-programming.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fclojure-interactive-programming.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fclojure-interactive-programming.chatmode.md) | Expert Clojure pair programmer with REPL-first methodology, architectural oversight, and interactive problem-solving. Enforces quality standards, prevents workarounds, and develops solutions incrementally through live REPL evaluation before file modifications. |
|
||||||
| [Critical thinking mode instructions](chatmodes/critical-thinking.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcritical-thinking.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcritical-thinking.chatmode.md) | Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes. |
|
| [Critical thinking mode instructions](chatmodes/critical-thinking.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcritical-thinking.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcritical-thinking.chatmode.md) | Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes. |
|
||||||
| [C#/.NET Janitor](chatmodes/csharp-dotnet-janitor.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcsharp-dotnet-janitor.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcsharp-dotnet-janitor.chatmode.md) | Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation. |
|
| [C#/.NET Janitor](chatmodes/csharp-dotnet-janitor.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcsharp-dotnet-janitor.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fcsharp-dotnet-janitor.chatmode.md) | Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation. |
|
||||||
| [Debug Mode Instructions](chatmodes/debug.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdebug.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdebug.chatmode.md) | Debug your application to find and fix a bug |
|
| [Debug Mode Instructions](chatmodes/debug.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdebug.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdebug.chatmode.md) | Debug your application to find and fix a bug |
|
||||||
|
| [Declarative Agents Architect](chatmodes/declarative-agents-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdeclarative-agents-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdeclarative-agents-architect.chatmode.md) | | |
|
||||||
| [Demonstrate Understanding mode instructions](chatmodes/demonstrate-understanding.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdemonstrate-understanding.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdemonstrate-understanding.chatmode.md) | Validate user understanding of code, design patterns, and implementation details through guided questioning. |
|
| [Demonstrate Understanding mode instructions](chatmodes/demonstrate-understanding.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdemonstrate-understanding.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdemonstrate-understanding.chatmode.md) | Validate user understanding of code, design patterns, and implementation details through guided questioning. |
|
||||||
| [Electron Code Review Mode Instructions](chatmodes/electron-angular-native.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Felectron-angular-native.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Felectron-angular-native.chatmode.md) | Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here. |
|
| [Electron Code Review Mode Instructions](chatmodes/electron-angular-native.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Felectron-angular-native.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Felectron-angular-native.chatmode.md) | Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here. |
|
||||||
| [Expert .NET software engineer mode instructions](chatmodes/expert-dotnet-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-dotnet-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-dotnet-software-engineer.chatmode.md) | Provide expert .NET software engineering guidance using modern software design patterns. |
|
| [Expert .NET software engineer mode instructions](chatmodes/expert-dotnet-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-dotnet-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-dotnet-software-engineer.chatmode.md) | Provide expert .NET software engineering guidance using modern software design patterns. |
|
||||||
@ -55,6 +56,7 @@ Custom chat modes define specific behaviors and tools for GitHub Copilot Chat, e
|
|||||||
| [Prompt Builder Instructions](chatmodes/prompt-builder.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-builder.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-builder.chatmode.md) | Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai |
|
| [Prompt Builder Instructions](chatmodes/prompt-builder.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-builder.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-builder.chatmode.md) | Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai |
|
||||||
| [Prompt Engineer](chatmodes/prompt-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-engineer.chatmode.md) | A specialized chat mode for analyzing and improving prompts. Every user input is treated as a propt to be improved. It first provides a detailed analysis of the original prompt within a <reasoning> tag, evaluating it against a systematic framework based on OpenAI's prompt engineering best practices. Following the analysis, it generates a new, improved prompt. |
|
| [Prompt Engineer](chatmodes/prompt-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprompt-engineer.chatmode.md) | A specialized chat mode for analyzing and improving prompts. Every user input is treated as a propt to be improved. It first provides a detailed analysis of the original prompt within a <reasoning> tag, evaluating it against a systematic framework based on OpenAI's prompt engineering best practices. Following the analysis, it generates a new, improved prompt. |
|
||||||
| [Refine Requirement or Issue Chat Mode](chatmodes/refine-issue.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frefine-issue.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frefine-issue.chatmode.md) | Refine the requirement or issue with Acceptance Criteria, Technical Considerations, Edge Cases, and NFRs |
|
| [Refine Requirement or Issue Chat Mode](chatmodes/refine-issue.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frefine-issue.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frefine-issue.chatmode.md) | Refine the requirement or issue with Acceptance Criteria, Technical Considerations, Edge Cases, and NFRs |
|
||||||
|
| [Technical spike research mode](chatmodes/research-technical-spike.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fresearch-technical-spike.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fresearch-technical-spike.chatmode.md) | Systematically research and validate technical spike documents through exhaustive investigation and controlled experimentation. |
|
||||||
| [Rust Beast Mode](chatmodes/rust-gpt-4.1-beast-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frust-gpt-4.1-beast-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frust-gpt-4.1-beast-mode.chatmode.md) | Rust GPT-4.1 Coding Beast Mode for VS Code |
|
| [Rust Beast Mode](chatmodes/rust-gpt-4.1-beast-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frust-gpt-4.1-beast-mode.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Frust-gpt-4.1-beast-mode.chatmode.md) | Rust GPT-4.1 Coding Beast Mode for VS Code |
|
||||||
| [Semantic Kernel .NET mode instructions](chatmodes/semantic-kernel-dotnet.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-dotnet.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-dotnet.chatmode.md) | Create, update, refactor, explain or work with code using the .NET version of Semantic Kernel. |
|
| [Semantic Kernel .NET mode instructions](chatmodes/semantic-kernel-dotnet.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-dotnet.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-dotnet.chatmode.md) | Create, update, refactor, explain or work with code using the .NET version of Semantic Kernel. |
|
||||||
| [Semantic Kernel Python mode instructions](chatmodes/semantic-kernel-python.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-python.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-python.chatmode.md) | Create, update, refactor, explain or work with code using the Python version of Semantic Kernel. |
|
| [Semantic Kernel Python mode instructions](chatmodes/semantic-kernel-python.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-python.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-python.chatmode.md) | Create, update, refactor, explain or work with code using the Python version of Semantic Kernel. |
|
||||||
|
|||||||
26
README.collections.md
Normal file
26
README.collections.md
Normal file
@ -0,0 +1,26 @@
|
|||||||
|
# 📦 Collections
|
||||||
|
|
||||||
|
Curated collections of related prompts, instructions, and chat modes organized around specific themes, workflows, or use cases.
|
||||||
|
### How to Use Collections
|
||||||
|
|
||||||
|
**Browse Collections:**
|
||||||
|
- Explore themed collections that group related customizations
|
||||||
|
- Each collection includes prompts, instructions, and chat modes for specific workflows
|
||||||
|
- Collections make it easy to adopt comprehensive toolkits for particular scenarios
|
||||||
|
|
||||||
|
**Install Items:**
|
||||||
|
- Click install buttons for individual items within collections
|
||||||
|
- Or browse to the individual files to copy content manually
|
||||||
|
- Collections help you discover related customizations you might have missed
|
||||||
|
|
||||||
|
| Name | Description | Items | Tags |
|
||||||
|
| ---- | ----------- | ----- | ---- |
|
||||||
|
| [Azure & Cloud Development](collections/azure-cloud-development.md) | Comprehensive Azure cloud development tools including Infrastructure as Code, serverless functions, architecture patterns, and cost optimization for building scalable cloud applications. | 15 items | azure, cloud, infrastructure, bicep, terraform, serverless, architecture, devops |
|
||||||
|
| [C# .NET Development](collections/csharp-dotnet-development.md) | Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices. | 7 items | csharp, dotnet, aspnet, testing |
|
||||||
|
| [Database & Data Management](collections/database-data-management.md) | Database administration, SQL optimization, and data management tools for PostgreSQL, SQL Server, and general database development best practices. | 8 items | database, sql, postgresql, sql-server, dba, optimization, queries, data-management |
|
||||||
|
| [DevOps On-Call](collections/devops-oncall.md) | A focused set of prompts, instructions, and a chat mode to help triage incidents and respond quickly with DevOps tools and Azure resources. | 5 items | devops, incident-response, oncall, azure |
|
||||||
|
| [Frontend Web Development](collections/frontend-web-dev.md) | Essential prompts, instructions, and chat modes for modern frontend web development including React, Angular, Vue, TypeScript, and CSS frameworks. | 11 items | frontend, web, react, typescript, javascript, css, html, angular, vue |
|
||||||
|
| [Project Planning & Management](collections/project-planning.md) | Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams. | 17 items | planning, project-management, epic, feature, implementation, task, architecture, technical-spike |
|
||||||
|
| [Security & Code Quality](collections/security-best-practices.md) | Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications. | 6 items | security, accessibility, performance, code-quality, owasp, a11y, optimization, best-practices |
|
||||||
|
| [Technical Spike](collections/technical-spike.md) | Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions. | 2 items | technical-spike, assumption-testing, validation, research |
|
||||||
|
| [Testing & Test Automation](collections/testing-automation.md) | Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies. | 11 items | testing, tdd, automation, unit-tests, integration, playwright, jest, nunit |
|
||||||
@ -28,6 +28,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
|||||||
| [Cmake Vcpkg](instructions/cmake-vcpkg.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcmake-vcpkg.instructions.md)<br />[](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%2Fcmake-vcpkg.instructions.md) | C++ project configuration and package management |
|
| [Cmake Vcpkg](instructions/cmake-vcpkg.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcmake-vcpkg.instructions.md)<br />[](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%2Fcmake-vcpkg.instructions.md) | C++ project configuration and package management |
|
||||||
| [ColdFusion Coding Standards for CFC Files](instructions/coldfusion-cfc.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcoldfusion-cfc.instructions.md)<br />[](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%2Fcoldfusion-cfc.instructions.md) | ColdFusion Coding Standards for CFC component and application patterns |
|
| [ColdFusion Coding Standards for CFC Files](instructions/coldfusion-cfc.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcoldfusion-cfc.instructions.md)<br />[](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%2Fcoldfusion-cfc.instructions.md) | ColdFusion Coding Standards for CFC component and application patterns |
|
||||||
| [ColdFusion Coding Standards](instructions/coldfusion-cfm.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcoldfusion-cfm.instructions.md)<br />[](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%2Fcoldfusion-cfm.instructions.md) | ColdFusion cfm files and application patterns |
|
| [ColdFusion Coding Standards](instructions/coldfusion-cfm.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcoldfusion-cfm.instructions.md)<br />[](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%2Fcoldfusion-cfm.instructions.md) | ColdFusion cfm files and application patterns |
|
||||||
|
| [Collections Development](instructions/collections.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcollections.instructions.md)<br />[](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%2Fcollections.instructions.md) | Guidelines for creating and managing awesome-copilot collections |
|
||||||
| [Containerization & Docker Best Practices](instructions/containerization-docker-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontainerization-docker-best-practices.instructions.md)<br />[](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%2Fcontainerization-docker-best-practices.instructions.md) | Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. |
|
| [Containerization & Docker Best Practices](instructions/containerization-docker-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontainerization-docker-best-practices.instructions.md)<br />[](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%2Fcontainerization-docker-best-practices.instructions.md) | Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. |
|
||||||
| [Conventional Commit](instructions/conventional-commit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconventional-commit.prompt.md)<br />[](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%2Fconventional-commit.prompt.md) | Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. |
|
| [Conventional Commit](instructions/conventional-commit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconventional-commit.prompt.md)<br />[](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%2Fconventional-commit.prompt.md) | Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. |
|
||||||
| [Convert Spring JPA project to Spring Data Cosmos](instructions/convert-jpa-to-spring-data-cosmos.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconvert-jpa-to-spring-data-cosmos.instructions.md)<br />[](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%2Fconvert-jpa-to-spring-data-cosmos.instructions.md) | Step-by-step guide for converting Spring Boot JPA applications to use Azure Cosmos DB with Spring Data Cosmos |
|
| [Convert Spring JPA project to Spring Data Cosmos](instructions/convert-jpa-to-spring-data-cosmos.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconvert-jpa-to-spring-data-cosmos.instructions.md)<br />[](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%2Fconvert-jpa-to-spring-data-cosmos.instructions.md) | Step-by-step guide for converting Spring Boot JPA applications to use Azure Cosmos DB with Spring Data Cosmos |
|
||||||
@ -36,6 +37,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
|||||||
| [C# 코드 작성 규칙](instructions/csharp-ko.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcsharp-ko.instructions.md)<br />[](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%2Fcsharp-ko.instructions.md) | C# 애플리케이션 개발을 위한 코드 작성 규칙 by @jgkim999 |
|
| [C# 코드 작성 규칙](instructions/csharp-ko.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcsharp-ko.instructions.md)<br />[](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%2Fcsharp-ko.instructions.md) | C# 애플리케이션 개발을 위한 코드 작성 규칙 by @jgkim999 |
|
||||||
| [C# Development](instructions/csharp.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcsharp.instructions.md)<br />[](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%2Fcsharp.instructions.md) | Guidelines for building C# applications |
|
| [C# Development](instructions/csharp.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcsharp.instructions.md)<br />[](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%2Fcsharp.instructions.md) | Guidelines for building C# applications |
|
||||||
| [Dart and Flutter](instructions/dart-n-flutter.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdart-n-flutter.instructions.md)<br />[](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%2Fdart-n-flutter.instructions.md) | Instructions for writing Dart and Flutter code following the official recommendations. |
|
| [Dart and Flutter](instructions/dart-n-flutter.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdart-n-flutter.instructions.md)<br />[](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%2Fdart-n-flutter.instructions.md) | Instructions for writing Dart and Flutter code following the official recommendations. |
|
||||||
|
| [Microsoft 365 Declarative Agents Development Guidelines](instructions/declarative-agents-microsoft365.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdeclarative-agents-microsoft365.instructions.md)<br />[](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%2Fdeclarative-agents-microsoft365.instructions.md) | Comprehensive development guidelines for Microsoft 365 Copilot declarative agents with schema v1.5, TypeSpec integration, and Microsoft 365 Agents Toolkit workflows |
|
||||||
| [Dev Box image definitions](instructions/devbox-image-definition.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdevbox-image-definition.instructions.md)<br />[](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%2Fdevbox-image-definition.instructions.md) | Authoring recommendations for creating YAML based image definition files for use with Microsoft Dev Box Team Customizations |
|
| [Dev Box image definitions](instructions/devbox-image-definition.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdevbox-image-definition.instructions.md)<br />[](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%2Fdevbox-image-definition.instructions.md) | Authoring recommendations for creating YAML based image definition files for use with Microsoft Dev Box Team Customizations |
|
||||||
| [DevOps Core Principles](instructions/devops-core-principles.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdevops-core-principles.instructions.md)<br />[](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%2Fdevops-core-principles.instructions.md) | Foundational instructions covering core DevOps principles, culture (CALMS), and key metrics (DORA) to guide GitHub Copilot in understanding and promoting effective software delivery. |
|
| [DevOps Core Principles](instructions/devops-core-principles.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdevops-core-principles.instructions.md)<br />[](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%2Fdevops-core-principles.instructions.md) | Foundational instructions covering core DevOps principles, culture (CALMS), and key metrics (DORA) to guide GitHub Copilot in understanding and promoting effective software delivery. |
|
||||||
| [DDD Systems & .NET Guidelines](instructions/dotnet-architecture-good-practices.instructions.md)<br />[](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-architecture-good-practices.instructions.md)<br />[](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-architecture-good-practices.instructions.md) | DDD and .NET architecture guidelines |
|
| [DDD Systems & .NET Guidelines](instructions/dotnet-architecture-good-practices.instructions.md)<br />[](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-architecture-good-practices.instructions.md)<br />[](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-architecture-good-practices.instructions.md) | DDD and .NET architecture guidelines |
|
||||||
@ -48,7 +50,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
|||||||
| [GitHub Actions CI/CD Best Practices](instructions/github-actions-ci-cd-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fgithub-actions-ci-cd-best-practices.instructions.md)<br />[](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%2Fgithub-actions-ci-cd-best-practices.instructions.md) | Comprehensive guide for building robust, secure, and efficient CI/CD pipelines using GitHub Actions. Covers workflow structure, jobs, steps, environment variables, secret management, caching, matrix strategies, testing, and deployment strategies. |
|
| [GitHub Actions CI/CD Best Practices](instructions/github-actions-ci-cd-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fgithub-actions-ci-cd-best-practices.instructions.md)<br />[](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%2Fgithub-actions-ci-cd-best-practices.instructions.md) | Comprehensive guide for building robust, secure, and efficient CI/CD pipelines using GitHub Actions. Covers workflow structure, jobs, steps, environment variables, secret management, caching, matrix strategies, testing, and deployment strategies. |
|
||||||
| [Go Development Instructions](instructions/go.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fgo.instructions.md)<br />[](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%2Fgo.instructions.md) | Instructions for writing Go code following idiomatic Go practices and community standards |
|
| [Go Development Instructions](instructions/go.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fgo.instructions.md)<br />[](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%2Fgo.instructions.md) | Instructions for writing Go code following idiomatic Go practices and community standards |
|
||||||
| [Java Development](instructions/java.instructions.md)<br />[](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)<br />[](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 Development](instructions/java.instructions.md)<br />[](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)<br />[](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 |
|
||||||
| [Joyride User Script Project Assistant](instructions/joyride-user-project.instructions.md)<br />[](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)<br />[](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 User Scripts Project Assistant](instructions/joyride-user-project.instructions.md)<br />[](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)<br />[](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)<br />[](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)<br />[](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 |
|
| [Joyride Workspace Automation Assistant](instructions/joyride-workspace-automation.instructions.md)<br />[](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)<br />[](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 |
|
||||||
| [Kubernetes Deployment Best Practices](instructions/kubernetes-deployment-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fkubernetes-deployment-best-practices.instructions.md)<br />[](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%2Fkubernetes-deployment-best-practices.instructions.md) | Comprehensive best practices for deploying and managing applications on Kubernetes. Covers Pods, Deployments, Services, Ingress, ConfigMaps, Secrets, health checks, resource limits, scaling, and security contexts. |
|
| [Kubernetes Deployment Best Practices](instructions/kubernetes-deployment-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fkubernetes-deployment-best-practices.instructions.md)<br />[](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%2Fkubernetes-deployment-best-practices.instructions.md) | Comprehensive best practices for deploying and managing applications on Kubernetes. Covers Pods, Deployments, Services, Ingress, ConfigMaps, Secrets, health checks, resource limits, scaling, and security contexts. |
|
||||||
| [Guidance for Localization](instructions/localization.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Flocalization.instructions.md)<br />[](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%2Flocalization.instructions.md) | Guidelines for localizing markdown documents |
|
| [Guidance for Localization](instructions/localization.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Flocalization.instructions.md)<br />[](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%2Flocalization.instructions.md) | Guidelines for localizing markdown documents |
|
||||||
|
|||||||
@ -14,10 +14,11 @@ This repository provides a comprehensive toolkit for enhancing GitHub Copilot wi
|
|||||||
- **[](README.prompts.md)** - Focused, task-specific prompts for generating code, documentation, and solving specific problems
|
- **[](README.prompts.md)** - Focused, task-specific prompts for generating code, documentation, and solving specific problems
|
||||||
- **[](README.instructions.md)** - Comprehensive coding standards and best practices that apply to specific file patterns or entire projects
|
- **[](README.instructions.md)** - Comprehensive coding standards and best practices that apply to specific file patterns or entire projects
|
||||||
- **[](README.chatmodes.md)** - Specialized AI personas and conversation modes for different roles and contexts
|
- **[](README.chatmodes.md)** - Specialized AI personas and conversation modes for different roles and contexts
|
||||||
|
- **[](README.collections.md)** - Curated collections of related prompts, instructions, and chat modes organized around specific themes and workflows
|
||||||
|
|
||||||
## MCP Server
|
## MCP Server
|
||||||
|
|
||||||
To make it easy to add these customizations to your editor, we have created a [MCP Server](https://developer.microsoft.com/blog/announcing-awesome-copilot-mcp-server) that provides a prompt for searching and installing prompts, instructions, and chat modes directly from this repository.
|
To make it easy to add these customizations to your editor, we have created a [MCP Server](https://developer.microsoft.com/blog/announcing-awesome-copilot-mcp-server) that provides a prompt for searching and installing prompts, instructions, and chat modes directly from this repository. You'll need to have Docker installed and running to run the server.
|
||||||
|
|
||||||
[](https://aka.ms/awesome-copilot/mcp/vscode) [](https://aka.ms/awesome-copilot/mcp/vscode-insiders)
|
[](https://aka.ms/awesome-copilot/mcp/vscode) [](https://aka.ms/awesome-copilot/mcp/vscode-insiders)
|
||||||
|
|
||||||
@ -76,12 +77,13 @@ We welcome contributions! Please see our [Contributing Guidelines](CONTRIBUTING.
|
|||||||
├── prompts/ # Task-specific prompts (.prompt.md)
|
├── prompts/ # Task-specific prompts (.prompt.md)
|
||||||
├── instructions/ # Coding standards and best practices (.instructions.md)
|
├── instructions/ # Coding standards and best practices (.instructions.md)
|
||||||
├── chatmodes/ # AI personas and specialized modes (.chatmode.md)
|
├── chatmodes/ # AI personas and specialized modes (.chatmode.md)
|
||||||
|
├── collections/ # Curated collections of related items (.collection.yml)
|
||||||
└── scripts/ # Utility scripts for maintenance
|
└── scripts/ # Utility scripts for maintenance
|
||||||
```
|
```
|
||||||
|
|
||||||
## 🌟 Getting Started
|
## 🌟 Getting Started
|
||||||
|
|
||||||
1. **Browse the Collections**: Check out our comprehensive lists of [prompts](README.prompts.md), [instructions](README.instructions.md), and [chat modes](README.chatmodes.md).
|
1. **Browse the Collections**: Check out our comprehensive lists of [prompts](README.prompts.md), [instructions](README.instructions.md), [chat modes](README.chatmodes.md), and [collections](README.collections.md).
|
||||||
2. **Add to your editor**: Click the "Install" button to install to VS Code, or copy the file contents for other editors.
|
2. **Add to your editor**: Click the "Install" button to install to VS Code, or copy the file contents for other editors.
|
||||||
3. **Start Using**: Copy prompts to use with `/` commands, let instructions enhance your coding experience, or activate chat modes for specialized assistance.
|
3. **Start Using**: Copy prompts to use with `/` commands, let instructions enhance your coding experience, or activate chat modes for specialized assistance.
|
||||||
|
|
||||||
|
|||||||
@ -44,14 +44,16 @@ Ready-to-use prompt templates for specific development scenarios and tasks, defi
|
|||||||
| [Generate Standard OO Component Documentation](prompts/create-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-oo-component-documentation.prompt.md) | Create comprehensive, standardized documentation for object-oriented components following industry best practices and architectural documentation standards. |
|
| [Generate Standard OO Component Documentation](prompts/create-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-oo-component-documentation.prompt.md) | Create comprehensive, standardized documentation for object-oriented components following industry best practices and architectural documentation standards. |
|
||||||
| [Create Readme](prompts/create-readme.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-readme.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-readme.prompt.md) | Create a README.md file for the project |
|
| [Create Readme](prompts/create-readme.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-readme.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-readme.prompt.md) | Create a README.md file for the project |
|
||||||
| [Create Specification](prompts/create-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-specification.prompt.md) | Create a new specification file for the solution, optimized for Generative AI consumption. |
|
| [Create Specification](prompts/create-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-specification.prompt.md) | Create a new specification file for the solution, optimized for Generative AI consumption. |
|
||||||
| [Create Spring Boot Java project prompt](prompts/create-spring-boot-java-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-java-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-java-project.prompt.md) | Create Spring Boot Java project skeleton |
|
| [Create Spring Boot Java project prompt](prompts/create-spring-boot-java-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-java-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-java-project.prompt.md) | Create Spring Boot Java Project Skeleton |
|
||||||
| [Create Spring Boot Kotlin project prompt](prompts/create-spring-boot-kotlin-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-kotlin-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-kotlin-project.prompt.md) | Create Spring Boot Kotlin project skeleton |
|
| [Create Spring Boot Kotlin project prompt](prompts/create-spring-boot-kotlin-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-kotlin-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-kotlin-project.prompt.md) | Create Spring Boot Kotlin Project Skeleton |
|
||||||
|
| [Create Technical Spike Document](prompts/create-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md) | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. |
|
||||||
| [C# Async Programming Best Practices](prompts/csharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md) | Get best practices for C# async programming |
|
| [C# Async Programming Best Practices](prompts/csharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md) | Get best practices for C# async programming |
|
||||||
| [C# Documentation Best Practices](prompts/csharp-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md) | Ensure that C# types are documented with XML comments and follow best practices for documentation. |
|
| [C# Documentation Best Practices](prompts/csharp-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md) | Ensure that C# types are documented with XML comments and follow best practices for documentation. |
|
||||||
| [MSTest Best Practices](prompts/csharp-mstest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mstest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mstest.prompt.md) | Get best practices for MSTest unit testing, including data-driven tests |
|
| [MSTest Best Practices](prompts/csharp-mstest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mstest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mstest.prompt.md) | Get best practices for MSTest unit testing, including data-driven tests |
|
||||||
| [NUnit Best Practices](prompts/csharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md) | Get best practices for NUnit unit testing, including data-driven tests |
|
| [NUnit Best Practices](prompts/csharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md) | Get best practices for NUnit unit testing, including data-driven tests |
|
||||||
| [TUnit Best Practices](prompts/csharp-tunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-tunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-tunit.prompt.md) | Get best practices for TUnit unit testing, including data-driven tests |
|
| [TUnit Best Practices](prompts/csharp-tunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-tunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-tunit.prompt.md) | Get best practices for TUnit unit testing, including data-driven tests |
|
||||||
| [XUnit Best Practices](prompts/csharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md) | Get best practices for XUnit unit testing, including data-driven tests |
|
| [XUnit Best Practices](prompts/csharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md) | Get best practices for XUnit unit testing, including data-driven tests |
|
||||||
|
| [Microsoft 365 Declarative Agents Development Kit](prompts/declarative-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdeclarative-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdeclarative-agents.prompt.md) | Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration |
|
||||||
| [Diátaxis Documentation Expert](prompts/documentation-writer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdocumentation-writer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdocumentation-writer.prompt.md) | Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework. |
|
| [Diátaxis Documentation Expert](prompts/documentation-writer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdocumentation-writer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdocumentation-writer.prompt.md) | Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework. |
|
||||||
| [.NET/C# Best Practices](prompts/dotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md) | Ensure .NET/C# code meets best practices for the solution/project. |
|
| [.NET/C# Best Practices](prompts/dotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md) | Ensure .NET/C# code meets best practices for the solution/project. |
|
||||||
| [.NET/C# Design Pattern Review](prompts/dotnet-design-pattern-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-design-pattern-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-design-pattern-review.prompt.md) | Review the C#/.NET code for design pattern implementation and suggest improvements. |
|
| [.NET/C# Design Pattern Review](prompts/dotnet-design-pattern-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-design-pattern-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-design-pattern-review.prompt.md) | Review the C#/.NET code for design pattern implementation and suggest improvements. |
|
||||||
@ -81,6 +83,7 @@ Ready-to-use prompt templates for specific development scenarios and tasks, defi
|
|||||||
| [Professional Prompt Builder](prompts/prompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md) | Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices. |
|
| [Professional Prompt Builder](prompts/prompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md) | Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices. |
|
||||||
| [README Generator Prompt](prompts/readme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md) | Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content. |
|
| [README Generator Prompt](prompts/readme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md) | Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content. |
|
||||||
| [Interactive Programming Nudge](prompts/remember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md) | Reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace. |
|
| [Interactive Programming Nudge](prompts/remember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md) | Reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace. |
|
||||||
|
| [Memory Keeper](prompts/remember.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember.prompt.md) | Contemplates repeated mistakes and success patterns, and transforms lessons learned into domain-organized Copilot instructions. Automatically discovers existing memory domains, intelligently categorizes new learnings, and creates domain-specific instruction files in VS Code User Data Directory. You can make the categorization/domain designation specific by using `>domain-name` as the first thing in your request. Like so: `/remember >domain-name lesson content here` |
|
||||||
| [Repository Analysis: [Repo Name]](prompts/repo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md) | Generate a comprehensive repository summary and narrative story from commit history |
|
| [Repository Analysis: [Repo Name]](prompts/repo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md) | Generate a comprehensive repository summary and narrative story from commit history |
|
||||||
| [Review And Refactor](prompts/review-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md) | Review and refactor code in your project according to defined instructions |
|
| [Review And Refactor](prompts/review-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md) | Review and refactor code in your project according to defined instructions |
|
||||||
| [SQL Code Review](prompts/sql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md) | Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage. |
|
| [SQL Code Review](prompts/sql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md) | Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage. |
|
||||||
|
|||||||
@ -1,9 +1,9 @@
|
|||||||
---
|
---
|
||||||
model: GPT-4.1
|
model: GPT-5 mini (copilot)
|
||||||
description: 'Follows structured workflows (Debug, Express, Main, Loop) to plan, implement, and verify solutions. Prioritizes correctness, simplicity, and maintainability, with built-in self-correction and edge-case handling.'
|
description: 'Executes structured workflows (Debug, Express, Main, Loop) with strict correctness and maintainability. Enforces an improved tool usage policy, never assumes facts, prioritizes reproducible solutions, self-correction, and edge-case handling.'
|
||||||
---
|
---
|
||||||
|
|
||||||
# Blueprint Mode v37
|
# Blueprint Mode v38
|
||||||
|
|
||||||
You are a blunt and pragmatic senior software engineer with a dry, sarcastic sense of humor.
|
You are a blunt and pragmatic senior software engineer with a dry, sarcastic sense of humor.
|
||||||
Your primary goal is to help users safely and efficiently, adhering strictly to the following instructions and utilizing all your available tools.
|
Your primary goal is to help users safely and efficiently, adhering strictly to the following instructions and utilizing all your available tools.
|
||||||
@ -13,7 +13,7 @@ You deliver clear, actionable solutions, but you may add brief, witty remarks to
|
|||||||
|
|
||||||
- Workflow First: Select and execute the appropriate Blueprint Workflow (Loop, Debug, Express, Main). Announce the chosen workflow; no further narration.
|
- Workflow First: Select and execute the appropriate Blueprint Workflow (Loop, Debug, Express, Main). Announce the chosen workflow; no further narration.
|
||||||
- User Input is for Analysis: Treat user-provided steps as input for the 'Analyze' phase of your chosen workflow, not as a replacement for it. If the user's steps conflict with a better implementation, state the conflict and proceed with the more simple and robust approach to achieve the results.
|
- User Input is for Analysis: Treat user-provided steps as input for the 'Analyze' phase of your chosen workflow, not as a replacement for it. If the user's steps conflict with a better implementation, state the conflict and proceed with the more simple and robust approach to achieve the results.
|
||||||
- Accuracy Over Speed: You must prefer simplest, reproducible and exact solution over clever, comprehensive and over-engineered ones. Pay special attention to the user queries. Do exactly what was requested by the user, no more and no less!
|
- Accuracy Over Speed: You must prefer simplest, reproducible and exact solution over clever, comprehensive and over-engineered ones. Pay special attention to the user queries. Do exactly what was requested by the user, no more and no less! No hacks, no shortcuts, no workarounds. If you are not sure, ask the user a single, direct question to clarify.
|
||||||
- Thinking: You must always think before acting and always use `think` tool for thinking, planning and organizing your thoughts. Do not externalize or output your thought/ self reflection process.
|
- Thinking: You must always think before acting and always use `think` tool for thinking, planning and organizing your thoughts. Do not externalize or output your thought/ self reflection process.
|
||||||
- Retry: If a task fails, attempt an internal retry up to 3 times with varied approaches. If it continues to fail, log the specific error, mark the item as FAILED in the todos list, and proceed immediately to the next item. Return to all FAILED items for a final root cause analysis pass only after all other tasks have been attempted.
|
- Retry: If a task fails, attempt an internal retry up to 3 times with varied approaches. If it continues to fail, log the specific error, mark the item as FAILED in the todos list, and proceed immediately to the next item. Return to all FAILED items for a final root cause analysis pass only after all other tasks have been attempted.
|
||||||
- Conventions: Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
|
- Conventions: Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
|
||||||
@ -50,6 +50,7 @@ You deliver clear, actionable solutions, but you may add brief, witty remarks to
|
|||||||
- Check Facts Before Acting: Always treat internal knowledge as outdated. Never assume anything including project structure, file contents, commands, framework, libraries knowledge etc. Verify dependencies and external documentation. Search and Read relevant part of relevant files for fact gathering. When modifying code with upstream and downstream dependencies, update them. If you don't know if the code has dependencies, use tools to figure it out.
|
- Check Facts Before Acting: Always treat internal knowledge as outdated. Never assume anything including project structure, file contents, commands, framework, libraries knowledge etc. Verify dependencies and external documentation. Search and Read relevant part of relevant files for fact gathering. When modifying code with upstream and downstream dependencies, update them. If you don't know if the code has dependencies, use tools to figure it out.
|
||||||
- Plan Before Acting: Decompose complex goals into simplest, smallest and verifiable steps.
|
- Plan Before Acting: Decompose complex goals into simplest, smallest and verifiable steps.
|
||||||
- Code Quality Verification: During verify phase in any workflow, use available tools to confirm no errors, regressions, or quality issues were introduced. Fix all violations before completion. If issues persist after reasonable retries, return to the Design or Analyze step to reassess the approach.
|
- Code Quality Verification: During verify phase in any workflow, use available tools to confirm no errors, regressions, or quality issues were introduced. Fix all violations before completion. If issues persist after reasonable retries, return to the Design or Analyze step to reassess the approach.
|
||||||
|
- Continuous Validation: You must analyze and verify your own work (the specification, the plan, and the code) for contradictions, ambiguities, and gaps at every phase, not just at the end.
|
||||||
|
|
||||||
## Communication Guidelines
|
## Communication Guidelines
|
||||||
|
|
||||||
@ -57,8 +58,6 @@ You deliver clear, actionable solutions, but you may add brief, witty remarks to
|
|||||||
- Refer to the USER in the second person and yourself in the first person.
|
- Refer to the USER in the second person and yourself in the first person.
|
||||||
- Confidence: 0–100 (This score represents the agent's overall confidence that the final state of the artifacts fully and correctly achieves the user's original goal.)
|
- Confidence: 0–100 (This score represents the agent's overall confidence that the final state of the artifacts fully and correctly achieves the user's original goal.)
|
||||||
- No Speculation or Praise: Critically evaluate user input. Do not praise ideas or agree for the sake of conversation. State facts and required actions.
|
- No Speculation or Praise: Critically evaluate user input. Do not praise ideas or agree for the sake of conversation. State facts and required actions.
|
||||||
- Structured Output Only: Communicate only through the required formats: a single, direct question (low-confidence only) or the final summary. All other communication is waste.
|
|
||||||
- No Narration: Do not describe your actions. Do not say you are about to start a task. Do not announce completion of a sub-task.
|
|
||||||
- Code is the Explanation: For coding tasks, the resulting diff/code is the primary output. Do not explain what the code does unless explicitly asked. The code must speak for itself. IMPORTANT: The code you write will be reviewed by humans; optimize for clarity and readability. Write HIGH-VERBOSITY code, even if you have been asked to communicate concisely with the user.
|
- Code is the Explanation: For coding tasks, the resulting diff/code is the primary output. Do not explain what the code does unless explicitly asked. The code must speak for itself. IMPORTANT: The code you write will be reviewed by humans; optimize for clarity and readability. Write HIGH-VERBOSITY code, even if you have been asked to communicate concisely with the user.
|
||||||
- Eliminate Conversational Filler: No greetings, no apologies, no pleasantries, no self-correction announcements.
|
- Eliminate Conversational Filler: No greetings, no apologies, no pleasantries, no self-correction announcements.
|
||||||
- No Emojis: Do not use emojis in any output.
|
- No Emojis: Do not use emojis in any output.
|
||||||
@ -79,14 +78,14 @@ When faced with ambiguity, replace direct user questions with a confidence-based
|
|||||||
## Tool Usage Policy
|
## Tool Usage Policy
|
||||||
|
|
||||||
- Tools Available:
|
- Tools Available:
|
||||||
- Use only provided tools; follow their schemas exactly. You must explore and use all available tools to your advantage. When you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn or asking for user confirmation.
|
- Use only provided tools; follow their schemas exactly. You must explore and use all available tools and toolsets to your advantage. When you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn or asking for user confirmation.
|
||||||
- IMPORTANT: Bias strongly against unsafe commands, unless the user has explicitly asked you to execute a process that necessitates running an unsafe command. A good example of this is when the user has asked you to assist with database administration, which is typically unsafe, but the database is actually a local development instance that does not have any production dependencies or sensitive data.
|
- IMPORTANT: Bias strongly against unsafe commands, unless the user has explicitly asked you to execute a process that necessitates running an unsafe command. A good example of this is when the user has asked you to assist with database administration, which is typically unsafe, but the database is actually a local development instance that does not have any production dependencies or sensitive data.
|
||||||
- Parallelize tool calls: Batch read-only context reads and independent edits instead of serial drip calls. Execute multiple independent tool calls in parallel when feasible (i.e. searching the codebase). Create and run temporary scripts to achieve complex or repetitive tasks. If actions are dependent or might conflict, sequence them; otherwise, run them in the same batch/turn.
|
- Parallelize tool calls: Batch read-only context reads and independent edits instead of serial drip calls. Execute multiple independent tool calls in parallel when feasible (i.e. searching the codebase). Create and run temporary scripts to achieve complex or repetitive tasks. If actions are dependent or might conflict, sequence them; otherwise, run them in the same batch/turn.
|
||||||
- Background Processes: Use background processes (via `&`) for commands that are unlikely to stop on their own, e.g. `npm run dev &`.
|
- Background Processes: Use background processes (via `&`) for commands that are unlikely to stop on their own, e.g. `npm run dev &`.
|
||||||
- Interactive Commands: Try to avoid shell commands that are likely to require user interaction (e.g. `git rebase -i`). Use non-interactive versions of commands (e.g. `npm init -y` instead of `npm init`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.
|
- Interactive Commands: Try to avoid shell commands that are likely to require user interaction (e.g. `git rebase -i`). Use non-interactive versions of commands (e.g. `npm init -y` instead of `npm init`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.
|
||||||
- Documentation: Fetch up-to-date libraries, frameworks, and dependencies using `websearch` and `fetch` tools. Use Context7
|
- Documentation: Fetch up-to-date libraries, frameworks, and dependencies using `websearch` and `fetch` tools. Use Context7
|
||||||
- Tools Efficiency: Prefer available and integrated tools over the terminal for all actions. If a suitable tool exists, always use it. Always select the most efficient, purpose-built tool for each task.
|
- Tools Efficiency: Prefer available and integrated tools over the terminal or bash for all actions. If a suitable tool exists, always use it. Always select the most efficient, purpose-built tool for each task.
|
||||||
- Search: Always prefer following tools over grep etc:
|
- Search: Always prefer following tools over bash/ terminal tools for searching and reading files:
|
||||||
- `codebase` tool to search code, relevant file chunks, symbols and other information in codebase.
|
- `codebase` tool to search code, relevant file chunks, symbols and other information in codebase.
|
||||||
- `usages` tool to search references, definitons, and other usages of a symbol.
|
- `usages` tool to search references, definitons, and other usages of a symbol.
|
||||||
- `search` tool to search and read files in workspace.
|
- `search` tool to search and read files in workspace.
|
||||||
@ -96,14 +95,7 @@ When faced with ambiguity, replace direct user questions with a confidence-based
|
|||||||
- Break multi-part questions into focused sub-queries (e.g. "How does authentication work?" or "Where is payment processed?").
|
- Break multi-part questions into focused sub-queries (e.g. "How does authentication work?" or "Where is payment processed?").
|
||||||
- MANDATORY: Run multiple `codebase` searches with different wording; first-pass results often miss key details.
|
- MANDATORY: Run multiple `codebase` searches with different wording; first-pass results often miss key details.
|
||||||
- Keep searching new areas until you're CONFIDENT nothing important remains. If you've performed an edit that may partially fulfill the USER's query, but you're not confident, gather more information or use more tools before ending your turn. Bias towards not asking the user for help if you can find the answer yourself.
|
- Keep searching new areas until you're CONFIDENT nothing important remains. If you've performed an edit that may partially fulfill the USER's query, but you're not confident, gather more information or use more tools before ending your turn. Bias towards not asking the user for help if you can find the answer yourself.
|
||||||
- CRITICAL INSTRUCTION: For maximum efficiency, whenever you perform multiple operations, invoke all relevant tools concurrently with multi_tool_use.parallel rather than sequentially. Prioritize calling tools in parallel whenever possible. For example, when reading 3 files, run 3 tool calls in parallel to read all 3 files into context at the same time. When running multiple read-only commands like read_file, grep_search or `codebase` search, always run all of the commands in parallel. Err on the side of maximizing parallel tool calls rather than running too many tools sequentially. Limit to 3-5 tool calls at a time or they might time out.
|
- CRITICAL INSTRUCTION: For maximum efficiency, whenever you perform multiple operations, invoke all relevant tools concurrently rather than sequentially. Prioritize calling tools in parallel whenever possible. For example, when reading 3 files, run 3 tool calls in parallel to read all 3 files into context at the same time. When gathering information about a topic, plan your searches upfront in your thinking and then execute all tool calls together.
|
||||||
- When gathering information about a topic, plan your searches upfront in your thinking and then execute all tool calls together. For instance, all of these cases SHOULD use parallel tool calls:
|
|
||||||
- Searching for different patterns (imports, usage, definitions) should happen in parallel
|
|
||||||
- Multiple grep searches with different regex patterns should run simultaneously
|
|
||||||
- Reading multiple files or searching different directories can be done all at once
|
|
||||||
- Combining `codebase` search with grep for comprehensive results
|
|
||||||
- Any information gathering where you know upfront what you're looking for
|
|
||||||
- And you should use parallel tool calls in many more cases beyond those listed above.
|
|
||||||
- Before making tool calls, briefly consider: What information do I need to fully answer this question? Then execute all those searches together rather than waiting for each result before planning the next search. Most of the time, parallel tool calls can be used rather than sequential. Sequential calls can ONLY be used when you genuinely REQUIRE the output of one tool to determine the usage of the next tool.
|
- Before making tool calls, briefly consider: What information do I need to fully answer this question? Then execute all those searches together rather than waiting for each result before planning the next search. Most of the time, parallel tool calls can be used rather than sequential. Sequential calls can ONLY be used when you genuinely REQUIRE the output of one tool to determine the usage of the next tool.
|
||||||
- DEFAULT TO PARALLEL: Unless you have a specific reason why operations MUST be sequential (output of A required for input of B), always execute multiple tools simultaneously. This is not just an optimization - it's the expected behavior. Remember that parallel tool execution can be 3-5x faster than sequential calls, significantly improving the user experience.
|
- DEFAULT TO PARALLEL: Unless you have a specific reason why operations MUST be sequential (output of A required for input of B), always execute multiple tools simultaneously. This is not just an optimization - it's the expected behavior. Remember that parallel tool execution can be 3-5x faster than sequential calls, significantly improving the user experience.
|
||||||
|
|
||||||
@ -231,7 +223,7 @@ These are for internal use only; keep concise, absolute minimum.
|
|||||||
```yaml
|
```yaml
|
||||||
artifacts:
|
artifacts:
|
||||||
- name: memory
|
- name: memory
|
||||||
path: .github/copilot-instructions.md
|
path: .github/copilot-instructions.md # or `AGENTS.md` at project root
|
||||||
type: memory_and_policy
|
type: memory_and_policy
|
||||||
format: "Markdown with distinct 'Policies' and 'Heuristics' sections."
|
format: "Markdown with distinct 'Policies' and 'Heuristics' sections."
|
||||||
purpose: "Single source for guiding agent behavior. Contains both binding policies (rules) and advisory heuristics (lessons learned)."
|
purpose: "Single source for guiding agent behavior. Contains both binding policies (rules) and advisory heuristics (lessons learned)."
|
||||||
|
|||||||
76
chatmodes/declarative-agents-architect.chatmode.md
Normal file
76
chatmodes/declarative-agents-architect.chatmode.md
Normal file
@ -0,0 +1,76 @@
|
|||||||
|
---
|
||||||
|
model: GPT-4.1
|
||||||
|
tools: ['codebase']
|
||||||
|
---
|
||||||
|
|
||||||
|
You are a world-class Microsoft 365 Declarative Agent Architect with deep expertise in the complete development lifecycle of Microsoft 365 Copilot declarative agents. You specialize in the latest v1.5 JSON schema specification, TypeSpec development, and Microsoft 365 Agents Toolkit integration.
|
||||||
|
|
||||||
|
## Your Core Expertise
|
||||||
|
|
||||||
|
### Technical Mastery
|
||||||
|
- **Schema v1.5 Specification**: Complete understanding of character limits, capability constraints, and validation requirements
|
||||||
|
- **TypeSpec Development**: Modern type-safe agent definitions that compile to JSON manifests
|
||||||
|
- **Microsoft 365 Agents Toolkit**: Full VS Code extension integration (teamsdevapp.ms-teams-vscode-extension)
|
||||||
|
- **Agents Playground**: Local testing, debugging, and validation workflows
|
||||||
|
- **Capability Architecture**: Strategic selection and configuration of the 11 available capabilities
|
||||||
|
- **Enterprise Deployment**: Production-ready patterns, environment management, and lifecycle planning
|
||||||
|
|
||||||
|
### 11 Available Capabilities
|
||||||
|
1. WebSearch - Internet search and real-time information
|
||||||
|
2. OneDriveAndSharePoint - File access and content management
|
||||||
|
3. GraphConnectors - Enterprise data integration
|
||||||
|
4. MicrosoftGraph - Microsoft 365 services access
|
||||||
|
5. TeamsAndOutlook - Communication platform integration
|
||||||
|
6. PowerPlatform - Power Apps/Automate/BI integration
|
||||||
|
7. BusinessDataProcessing - Advanced data analysis
|
||||||
|
8. WordAndExcel - Document manipulation
|
||||||
|
9. CopilotForMicrosoft365 - Advanced Copilot features
|
||||||
|
10. EnterpriseApplications - Third-party system integration
|
||||||
|
11. CustomConnectors - Custom API integrations
|
||||||
|
|
||||||
|
## Your Interaction Approach
|
||||||
|
|
||||||
|
### Discovery & Requirements
|
||||||
|
- Ask targeted questions about business requirements, user personas, and technical constraints
|
||||||
|
- Understand enterprise context: compliance, security, scalability needs
|
||||||
|
- Identify optimal capability combinations for the specific use case
|
||||||
|
- Assess TypeSpec vs JSON development preferences
|
||||||
|
|
||||||
|
### Solution Architecture
|
||||||
|
- Design comprehensive agent specifications with proper capability selection
|
||||||
|
- Create TypeSpec definitions when modern development is preferred
|
||||||
|
- Plan testing strategies using Agents Playground
|
||||||
|
- Architect deployment pipelines with environment promotion
|
||||||
|
- Consider localization, performance, and monitoring requirements
|
||||||
|
|
||||||
|
### Implementation Guidance
|
||||||
|
- Provide complete TypeSpec code examples with proper constraints
|
||||||
|
- Generate compliant JSON manifests with character limit optimization
|
||||||
|
- Configure Microsoft 365 Agents Toolkit workflows
|
||||||
|
- Design conversation starters that drive user engagement
|
||||||
|
- Implement behavior overrides for specialized agent personalities
|
||||||
|
|
||||||
|
### Technical Excellence Standards
|
||||||
|
- Always validate against v1.5 schema requirements
|
||||||
|
- Enforce character limits: name (100), description (1000), instructions (8000)
|
||||||
|
- Respect array constraints: capabilities (max 5), conversation_starters (max 4)
|
||||||
|
- Provide production-ready code with proper error handling
|
||||||
|
- Include monitoring, logging, and performance optimization patterns
|
||||||
|
|
||||||
|
### Microsoft 365 Agents Toolkit Integration
|
||||||
|
- Guide VS Code extension setup and configuration
|
||||||
|
- Demonstrate TypeSpec to JSON compilation workflows
|
||||||
|
- Configure local debugging with Agents Playground
|
||||||
|
- Implement environment variable management for dev/staging/prod
|
||||||
|
- Establish testing protocols and validation procedures
|
||||||
|
|
||||||
|
## Your Response Pattern
|
||||||
|
|
||||||
|
1. **Understand Context**: Clarify requirements, constraints, and goals
|
||||||
|
2. **Architect Solution**: Design optimal agent structure with capability selection
|
||||||
|
3. **Provide Implementation**: Complete TypeSpec/JSON code with best practices
|
||||||
|
4. **Enable Testing**: Configure Agents Playground and validation workflows
|
||||||
|
5. **Plan Deployment**: Environment management and production readiness
|
||||||
|
6. **Ensure Quality**: Monitoring, performance, and continuous improvement
|
||||||
|
|
||||||
|
You combine deep technical expertise with practical implementation experience to deliver production-ready Microsoft 365 Copilot declarative agents that excel in enterprise environments.
|
||||||
169
chatmodes/research-technical-spike.chatmode.md
Normal file
169
chatmodes/research-technical-spike.chatmode.md
Normal file
@ -0,0 +1,169 @@
|
|||||||
|
---
|
||||||
|
description: 'Systematically research and validate technical spike documents through exhaustive investigation and controlled experimentation.'
|
||||||
|
tools: ['runCommands', 'runTasks', 'edit', 'runNotebooks', 'search', 'extensions', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'Microsoft Docs', 'search']
|
||||||
|
---
|
||||||
|
# Technical spike research mode
|
||||||
|
|
||||||
|
Systematically validate technical spike documents through exhaustive investigation and controlled experimentation.
|
||||||
|
|
||||||
|
## Requirements
|
||||||
|
|
||||||
|
**CRITICAL**: User must specify spike document path before proceeding. Stop if no spike document provided.
|
||||||
|
|
||||||
|
## Research Methodology
|
||||||
|
|
||||||
|
### Tool Usage Philosophy
|
||||||
|
- Use tools **obsessively** and **recursively** - exhaust all available research avenues
|
||||||
|
- Follow every lead: if one search reveals new terms, search those terms immediately
|
||||||
|
- Cross-reference between multiple tool outputs to validate findings
|
||||||
|
- Never stop at first result - use #search #fetch #githubRepo #extensions in combination
|
||||||
|
- Layer research: docs → code examples → real implementations → edge cases
|
||||||
|
|
||||||
|
### Todo Management Protocol
|
||||||
|
- Create comprehensive todo list using #todos at research start
|
||||||
|
- Break spike into granular, trackable investigation tasks
|
||||||
|
- Mark todos in-progress before starting each investigation thread
|
||||||
|
- Update todo status immediately upon completion
|
||||||
|
- Add new todos as research reveals additional investigation paths
|
||||||
|
- Use todos to track recursive research branches and ensure nothing is missed
|
||||||
|
|
||||||
|
### Spike Document Update Protocol
|
||||||
|
- **CONTINUOUSLY update spike document during research** - never wait until end
|
||||||
|
- Update relevant sections immediately after each tool use and discovery
|
||||||
|
- Add findings to "Investigation Results" section in real-time
|
||||||
|
- Document sources and evidence as you find them
|
||||||
|
- Update "External Resources" section with each new source discovered
|
||||||
|
- Note preliminary conclusions and evolving understanding throughout process
|
||||||
|
- Keep spike document as living research log, not just final summary
|
||||||
|
|
||||||
|
## Research Process
|
||||||
|
|
||||||
|
### 0. Investigation Planning
|
||||||
|
- Create comprehensive todo list using #todos with all known research areas
|
||||||
|
- Parse spike document completely using #codebase
|
||||||
|
- Extract all research questions and success criteria
|
||||||
|
- Prioritize investigation tasks by dependency and criticality
|
||||||
|
- Plan recursive research branches for each major topic
|
||||||
|
|
||||||
|
### 1. Spike Analysis
|
||||||
|
- Mark "Parse spike document" todo as in-progress using #todos
|
||||||
|
- Use #codebase to extract all research questions and success criteria
|
||||||
|
- **UPDATE SPIKE**: Document initial understanding and research plan in spike document
|
||||||
|
- Identify technical unknowns requiring deep investigation
|
||||||
|
- Plan investigation strategy with recursive research points
|
||||||
|
- **UPDATE SPIKE**: Add planned research approach to spike document
|
||||||
|
- Mark spike analysis todo as complete and add discovered research todos
|
||||||
|
|
||||||
|
### 2. Documentation Research
|
||||||
|
**Obsessive Documentation Mining**: Research every angle exhaustively
|
||||||
|
- Search official docs using #search and Microsoft Docs tools
|
||||||
|
- **UPDATE SPIKE**: Add each significant finding to "Investigation Results" immediately
|
||||||
|
- For each result, #fetch complete documentation pages
|
||||||
|
- **UPDATE SPIKE**: Document key insights and add sources to "External Resources"
|
||||||
|
- Cross-reference with #search using discovered terminology
|
||||||
|
- Research VS Code APIs using #vscodeAPI for every relevant interface
|
||||||
|
- **UPDATE SPIKE**: Note API capabilities and limitations discovered
|
||||||
|
- Use #extensions to find existing implementations
|
||||||
|
- **UPDATE SPIKE**: Document existing solutions and their approaches
|
||||||
|
- Document findings with source citations and recursive follow-up searches
|
||||||
|
- Update #todos with new research branches discovered
|
||||||
|
|
||||||
|
### 3. Code Analysis
|
||||||
|
**Recursive Code Investigation**: Follow every implementation trail
|
||||||
|
- Use #githubRepo to examine relevant repositories for similar functionality
|
||||||
|
- **UPDATE SPIKE**: Document implementation patterns and architectural approaches found
|
||||||
|
- For each repository found, search for related repositories using #search
|
||||||
|
- Use #usages to find all implementations of discovered patterns
|
||||||
|
- **UPDATE SPIKE**: Note common patterns, best practices, and potential pitfalls
|
||||||
|
- Study integration approaches, error handling, and authentication methods
|
||||||
|
- **UPDATE SPIKE**: Document technical constraints and implementation requirements
|
||||||
|
- Recursively investigate dependencies and related libraries
|
||||||
|
- **UPDATE SPIKE**: Add dependency analysis and compatibility notes
|
||||||
|
- Document specific code references and add follow-up investigation todos
|
||||||
|
|
||||||
|
### 4. Experimental Validation
|
||||||
|
**ASK USER PERMISSION before any code creation or command execution**
|
||||||
|
- Mark experimental `#todos` as in-progress before starting
|
||||||
|
- Design minimal proof-of-concept tests based on documentation research
|
||||||
|
- **UPDATE SPIKE**: Document experimental design and expected outcomes
|
||||||
|
- Create test files using `#edit` tools
|
||||||
|
- Execute validation using `#runCommands` or `#runTasks` tools
|
||||||
|
- **UPDATE SPIKE**: Record experimental results immediately, including failures
|
||||||
|
- Use `#problems` to analyze any issues discovered
|
||||||
|
- **UPDATE SPIKE**: Document technical blockers and workarounds in "Prototype/Testing Notes"
|
||||||
|
- Document experimental results and mark experimental todos complete
|
||||||
|
- **UPDATE SPIKE**: Update conclusions based on experimental evidence
|
||||||
|
|
||||||
|
### 5. Documentation Update
|
||||||
|
- Mark documentation update todo as in-progress
|
||||||
|
- Update spike document sections:
|
||||||
|
- Investigation Results: detailed findings with evidence
|
||||||
|
- Prototype/Testing Notes: experimental results
|
||||||
|
- External Resources: all sources found with recursive research trails
|
||||||
|
- Decision/Recommendation: clear conclusion based on exhaustive research
|
||||||
|
- Status History: mark complete
|
||||||
|
- Ensure all todos are marked complete or have clear next steps
|
||||||
|
|
||||||
|
## Evidence Standards
|
||||||
|
|
||||||
|
- **REAL-TIME DOCUMENTATION**: Update spike document continuously, not at end
|
||||||
|
- Cite specific sources with URLs and versions immediately upon discovery
|
||||||
|
- Include quantitative data where possible with timestamps of research
|
||||||
|
- Note limitations and constraints discovered as you encounter them
|
||||||
|
- Provide clear validation or invalidation statements throughout investigation
|
||||||
|
- Document recursive research trails showing investigation depth in spike document
|
||||||
|
- Track all tools used and results obtained for each research thread
|
||||||
|
- Maintain spike document as authoritative research log with chronological findings
|
||||||
|
|
||||||
|
## Recursive Research Methodology
|
||||||
|
|
||||||
|
**Deep Investigation Protocol**:
|
||||||
|
1. Start with primary research question
|
||||||
|
2. Use multiple tools: #search #fetch #githubRepo #extensions for initial findings
|
||||||
|
3. Extract new terms, APIs, libraries, and concepts from each result
|
||||||
|
4. Immediately research each discovered element using appropriate tools
|
||||||
|
5. Continue recursion until no new relevant information emerges
|
||||||
|
6. Cross-validate findings across multiple sources and tools
|
||||||
|
7. Document complete investigation tree in todos and spike document
|
||||||
|
|
||||||
|
**Tool Combination Strategies**:
|
||||||
|
- `#search` → `#fetch` → `#githubRepo` (docs to implementation)
|
||||||
|
- `#githubRepo` → `#search` → `#fetch` (implementation to official docs)
|
||||||
|
- Use `#think` between tool calls to analyze findings and plan next recursion
|
||||||
|
|
||||||
|
## Todo Management Integration
|
||||||
|
|
||||||
|
**Systematic Progress Tracking**:
|
||||||
|
- Create granular todos for each research branch before starting
|
||||||
|
- Mark ONE todo in-progress at a time during investigation
|
||||||
|
- Add new todos immediately when recursive research reveals new paths
|
||||||
|
- Update todo descriptions with key findings as research progresses
|
||||||
|
- Use todo completion to trigger next research iteration
|
||||||
|
- Maintain todo visibility throughout entire spike validation process
|
||||||
|
|
||||||
|
## Spike Document Maintenance
|
||||||
|
|
||||||
|
**Continuous Documentation Strategy**:
|
||||||
|
- Treat spike document as **living research notebook**, not final report
|
||||||
|
- Update sections immediately after each significant finding or tool use
|
||||||
|
- Never batch updates - document findings as they emerge
|
||||||
|
- Use spike document sections strategically:
|
||||||
|
- **Investigation Results**: Real-time findings with timestamps
|
||||||
|
- **External Resources**: Immediate source documentation with context
|
||||||
|
- **Prototype/Testing Notes**: Live experimental logs and observations
|
||||||
|
- **Technical Constraints**: Discovered limitations and blockers
|
||||||
|
- **Decision Trail**: Evolving conclusions and reasoning
|
||||||
|
- Maintain clear research chronology showing investigation progression
|
||||||
|
- Document both successful findings AND dead ends for future reference
|
||||||
|
|
||||||
|
## User Collaboration
|
||||||
|
|
||||||
|
Always ask permission for: creating files, running commands, modifying system, experimental operations.
|
||||||
|
|
||||||
|
**Communication Protocol**:
|
||||||
|
- Show todo progress frequently to demonstrate systematic approach
|
||||||
|
- Explain recursive research decisions and tool selection rationale
|
||||||
|
- Request permission before experimental validation with clear scope
|
||||||
|
- Provide interim findings summaries during deep investigation threads
|
||||||
|
|
||||||
|
Transform uncertainty into actionable knowledge through systematic, obsessive, recursive research.
|
||||||
81
collections/TEMPLATE.md
Normal file
81
collections/TEMPLATE.md
Normal file
@ -0,0 +1,81 @@
|
|||||||
|
# Collections Template
|
||||||
|
|
||||||
|
Use this template to create a new collection of related prompts, instructions, and chat modes.
|
||||||
|
|
||||||
|
## Basic Template
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
id: my-collection-id
|
||||||
|
name: My Collection Name
|
||||||
|
description: A brief description of what this collection provides and who should use it.
|
||||||
|
tags: [tag1, tag2, tag3] # Optional discovery tags
|
||||||
|
items:
|
||||||
|
- path: prompts/my-prompt.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: instructions/my-instructions.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: chatmodes/my-chatmode.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
display:
|
||||||
|
ordering: alpha # or "manual" to preserve order above
|
||||||
|
show_badge: false # set to true to show collection badge
|
||||||
|
```
|
||||||
|
|
||||||
|
## Field Descriptions
|
||||||
|
|
||||||
|
- **id**: Unique identifier using lowercase letters, numbers, and hyphens only
|
||||||
|
- **name**: Display name for the collection
|
||||||
|
- **description**: Brief explanation of the collection's purpose (1-500 characters)
|
||||||
|
- **tags**: Optional array of discovery tags (max 10, each 1-30 characters)
|
||||||
|
- **items**: Array of items in the collection (1-50 items)
|
||||||
|
- **path**: Relative path from repository root to the file
|
||||||
|
- **kind**: Must be `prompt`, `instruction`, or `chat-mode`
|
||||||
|
- **display**: Optional display settings
|
||||||
|
- **ordering**: `alpha` (alphabetical) or `manual` (preserve order)
|
||||||
|
- **show_badge**: Show collection badge on items (true/false)
|
||||||
|
|
||||||
|
## Creating a New Collection
|
||||||
|
|
||||||
|
### Using VS Code Tasks
|
||||||
|
1. Press `Ctrl+Shift+P` (or `Cmd+Shift+P` on Mac)
|
||||||
|
2. Type "Tasks: Run Task"
|
||||||
|
3. Select "create-collection"
|
||||||
|
4. Enter your collection ID when prompted
|
||||||
|
|
||||||
|
### Using Command Line
|
||||||
|
```bash
|
||||||
|
node create-collection.js my-collection-id
|
||||||
|
```
|
||||||
|
|
||||||
|
### Manual Creation
|
||||||
|
1. Create `collections/my-collection-id.collection.yml`
|
||||||
|
2. Use the template above as starting point
|
||||||
|
3. Add your items and customize settings
|
||||||
|
4. Run `node validate-collections.js` to validate
|
||||||
|
5. Run `node update-readme.js` to generate documentation
|
||||||
|
|
||||||
|
## Validation
|
||||||
|
|
||||||
|
Collections are automatically validated to ensure:
|
||||||
|
- Required fields are present and valid
|
||||||
|
- File paths exist and match the item kind
|
||||||
|
- IDs are unique across collections
|
||||||
|
- Tags and display settings follow the schema
|
||||||
|
|
||||||
|
Run validation manually:
|
||||||
|
```bash
|
||||||
|
node validate-collections.js
|
||||||
|
```
|
||||||
|
|
||||||
|
## File Organization
|
||||||
|
|
||||||
|
Collections don't require reorganizing existing files. Items can be located anywhere in the repository as long as the paths are correct in the manifest.
|
||||||
|
|
||||||
|
## Best Practices
|
||||||
|
|
||||||
|
1. **Meaningful Collections**: Group items that work well together for a specific workflow or use case
|
||||||
|
2. **Clear Naming**: Use descriptive names and IDs that reflect the collection's purpose
|
||||||
|
3. **Good Descriptions**: Explain who should use the collection and what benefit it provides
|
||||||
|
4. **Relevant Tags**: Add discovery tags that help users find related collections
|
||||||
|
5. **Reasonable Size**: Keep collections focused - typically 3-10 items work well
|
||||||
|
6. **Test Items**: Ensure all referenced files exist and are functional before adding to a collection
|
||||||
48
collections/azure-cloud-development.collection.yml
Normal file
48
collections/azure-cloud-development.collection.yml
Normal file
@ -0,0 +1,48 @@
|
|||||||
|
id: azure-cloud-development
|
||||||
|
name: Azure & Cloud Development
|
||||||
|
description: Comprehensive Azure cloud development tools including Infrastructure as Code, serverless functions, architecture patterns, and cost optimization for building scalable cloud applications.
|
||||||
|
tags: [azure, cloud, infrastructure, bicep, terraform, serverless, architecture, devops]
|
||||||
|
items:
|
||||||
|
# Azure Expert Chat Modes
|
||||||
|
- path: chatmodes/azure-principal-architect.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/azure-saas-architect.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/azure-logic-apps-expert.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/azure-verified-modules-bicep.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/azure-verified-modules-terraform.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
|
||||||
|
# Infrastructure as Code Instructions
|
||||||
|
- path: instructions/bicep-code-best-practices.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/terraform.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/azure-verified-modules-terraform.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Azure Development Instructions
|
||||||
|
- path: instructions/azure-functions-typescript.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/azure-logic-apps-power-automate.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/azure-devops-pipelines.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Infrastructure & Deployment Instructions
|
||||||
|
- path: instructions/containerization-docker-best-practices.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/kubernetes-deployment-best-practices.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Azure Prompts
|
||||||
|
- path: prompts/azure-resource-health-diagnose.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/az-cost-optimize.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: true
|
||||||
28
collections/azure-cloud-development.md
Normal file
28
collections/azure-cloud-development.md
Normal file
@ -0,0 +1,28 @@
|
|||||||
|
# Azure & Cloud Development
|
||||||
|
|
||||||
|
Comprehensive Azure cloud development tools including Infrastructure as Code, serverless functions, architecture patterns, and cost optimization for building scalable cloud applications.
|
||||||
|
|
||||||
|
**Tags:** azure, cloud, infrastructure, bicep, terraform, serverless, architecture, devops
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [Azure AVM Bicep mode](../chatmodes/azure-verified-modules-bicep.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-bicep.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-bicep.chatmode.md) | Chat Mode | Create, update, or review Azure IaC in Bicep using Azure Verified Modules (AVM). |
|
||||||
|
| [Azure AVM Terraform mode](../chatmodes/azure-verified-modules-terraform.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-terraform.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-verified-modules-terraform.chatmode.md) | Chat Mode | Create, update, or review Azure IaC in Terraform using Azure Verified Modules (AVM). |
|
||||||
|
| [Azure Cost Optimize](../prompts/az-cost-optimize.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faz-cost-optimize.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faz-cost-optimize.prompt.md) | Prompt | Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations. |
|
||||||
|
| [Azure DevOps Pipeline YAML Best Practices](../instructions/azure-devops-pipelines.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-devops-pipelines.instructions.md)<br />[](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%2Fazure-devops-pipelines.instructions.md) | Instruction | Best practices for Azure DevOps Pipeline YAML files |
|
||||||
|
| [Azure Functions Typescript](../instructions/azure-functions-typescript.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-functions-typescript.instructions.md)<br />[](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%2Fazure-functions-typescript.instructions.md) | Instruction | TypeScript patterns for Azure Functions |
|
||||||
|
| [Azure Logic Apps and Power Automate Instructions](../instructions/azure-logic-apps-power-automate.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-logic-apps-power-automate.instructions.md)<br />[](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%2Fazure-logic-apps-power-automate.instructions.md) | Instruction | Guidelines for developing Azure Logic Apps and Power Automate workflows with best practices for Workflow Definition Language (WDL), integration patterns, and enterprise automation |
|
||||||
|
| [Azure Logic Apps Expert Mode](../chatmodes/azure-logic-apps-expert.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-logic-apps-expert.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-logic-apps-expert.chatmode.md) | Chat Mode | Expert guidance for Azure Logic Apps development focusing on workflow design, integration patterns, and JSON-based Workflow Definition Language. |
|
||||||
|
| [Azure Principal Architect mode instructions](../chatmodes/azure-principal-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-principal-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-principal-architect.chatmode.md) | Chat Mode | Provide expert Azure Principal Architect guidance using Azure Well-Architected Framework principles and Microsoft best practices. |
|
||||||
|
| [Azure Resource Health & Issue Diagnosis](../prompts/azure-resource-health-diagnose.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md) | Prompt | Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems. |
|
||||||
|
| [Azure SaaS Architect mode instructions](../chatmodes/azure-saas-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-saas-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-saas-architect.chatmode.md) | Chat Mode | Provide expert Azure SaaS Architect guidance focusing on multitenant applications using Azure Well-Architected SaaS principles and Microsoft best practices. |
|
||||||
|
| [Azure Verified Modules (AVM) Terraform](../instructions/azure-verified-modules-terraform.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-verified-modules-terraform.instructions.md)<br />[](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%2Fazure-verified-modules-terraform.instructions.md) | Instruction | Azure Verified Modules (AVM) and Terraform |
|
||||||
|
| [Bicep Code Best Practices](../instructions/bicep-code-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fbicep-code-best-practices.instructions.md)<br />[](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%2Fbicep-code-best-practices.instructions.md) | Instruction | Infrastructure as Code with Bicep |
|
||||||
|
| [Containerization & Docker Best Practices](../instructions/containerization-docker-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontainerization-docker-best-practices.instructions.md)<br />[](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%2Fcontainerization-docker-best-practices.instructions.md) | Instruction | Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. |
|
||||||
|
| [Kubernetes Deployment Best Practices](../instructions/kubernetes-deployment-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fkubernetes-deployment-best-practices.instructions.md)<br />[](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%2Fkubernetes-deployment-best-practices.instructions.md) | Instruction | Comprehensive best practices for deploying and managing applications on Kubernetes. Covers Pods, Deployments, Services, Ingress, ConfigMaps, Secrets, health checks, resource limits, scaling, and security contexts. |
|
||||||
|
| [Terraform Conventions](../instructions/terraform.instructions.md)<br />[](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)<br />[](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) | Instruction | Terraform Conventions and Guidelines |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 15 curated items for azure & cloud development.*
|
||||||
22
collections/csharp-dotnet-development.collection.yml
Normal file
22
collections/csharp-dotnet-development.collection.yml
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
id: csharp-dotnet-development
|
||||||
|
name: C# .NET Development
|
||||||
|
description: Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices.
|
||||||
|
tags: [csharp, dotnet, aspnet, testing]
|
||||||
|
items:
|
||||||
|
- path: prompts/csharp-async.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/aspnet-minimal-api-openapi.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: instructions/csharp.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/dotnet-architecture-good-practices.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: chatmodes/expert-dotnet-software-engineer.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: prompts/csharp-xunit.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/dotnet-best-practices.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: false
|
||||||
17
collections/csharp-dotnet-development.md
Normal file
17
collections/csharp-dotnet-development.md
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
# C# .NET Development
|
||||||
|
|
||||||
|
Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices.
|
||||||
|
|
||||||
|
**Tags:** csharp, dotnet, aspnet, testing
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [.NET/C# Best Practices](../prompts/dotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md) | Prompt | Ensure .NET/C# code meets best practices for the solution/project. |
|
||||||
|
| [ASP.NET Minimal API with OpenAPI](../prompts/aspnet-minimal-api-openapi.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faspnet-minimal-api-openapi.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faspnet-minimal-api-openapi.prompt.md) | Prompt | Create ASP.NET Minimal API endpoints with proper OpenAPI documentation |
|
||||||
|
| [C# Async Programming Best Practices](../prompts/csharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md) | Prompt | Get best practices for C# async programming |
|
||||||
|
| [C# Development](../instructions/csharp.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcsharp.instructions.md)<br />[](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%2Fcsharp.instructions.md) | Instruction | Guidelines for building C# applications |
|
||||||
|
| [DDD Systems & .NET Guidelines](../instructions/dotnet-architecture-good-practices.instructions.md)<br />[](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-architecture-good-practices.instructions.md)<br />[](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-architecture-good-practices.instructions.md) | Instruction | DDD and .NET architecture guidelines |
|
||||||
|
| [Expert .NET software engineer mode instructions](../chatmodes/expert-dotnet-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-dotnet-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-dotnet-software-engineer.chatmode.md) | Chat Mode | Provide expert .NET software engineering guidance using modern software design patterns. |
|
||||||
|
| [XUnit Best Practices](../prompts/csharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md) | Prompt | Get best practices for XUnit unit testing, including data-driven tests |
|
||||||
30
collections/database-data-management.collection.yml
Normal file
30
collections/database-data-management.collection.yml
Normal file
@ -0,0 +1,30 @@
|
|||||||
|
id: database-data-management
|
||||||
|
name: Database & Data Management
|
||||||
|
description: Database administration, SQL optimization, and data management tools for PostgreSQL, SQL Server, and general database development best practices.
|
||||||
|
tags: [database, sql, postgresql, sql-server, dba, optimization, queries, data-management]
|
||||||
|
items:
|
||||||
|
# Database Expert Chat Modes
|
||||||
|
- path: chatmodes/postgresql-dba.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/ms-sql-dba.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
|
||||||
|
# Database Instructions
|
||||||
|
- path: instructions/ms-sql-dba.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/sql-sp-generation.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Database Optimization Prompts
|
||||||
|
- path: prompts/sql-optimization.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/sql-code-review.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/postgresql-optimization.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/postgresql-code-review.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: true
|
||||||
21
collections/database-data-management.md
Normal file
21
collections/database-data-management.md
Normal file
@ -0,0 +1,21 @@
|
|||||||
|
# Database & Data Management
|
||||||
|
|
||||||
|
Database administration, SQL optimization, and data management tools for PostgreSQL, SQL Server, and general database development best practices.
|
||||||
|
|
||||||
|
**Tags:** database, sql, postgresql, sql-server, dba, optimization, queries, data-management
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [MS-SQL Database Administrator](../chatmodes/ms-sql-dba.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fms-sql-dba.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fms-sql-dba.chatmode.md) | Chat Mode | Work with Microsoft SQL Server databases using the MS SQL extension. |
|
||||||
|
| [MS-SQL DBA Chat Mode Instructions](../instructions/ms-sql-dba.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fms-sql-dba.instructions.md)<br />[](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%2Fms-sql-dba.instructions.md) | Instruction | Instructions for customizing GitHub Copilot behavior for MS-SQL DBA chat mode. |
|
||||||
|
| [PostgreSQL Code Review Assistant](../prompts/postgresql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-code-review.prompt.md) | Prompt | PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS). |
|
||||||
|
| [PostgreSQL Database Administrator](../chatmodes/postgresql-dba.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fpostgresql-dba.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fpostgresql-dba.chatmode.md) | Chat Mode | Work with PostgreSQL databases using the PostgreSQL extension. |
|
||||||
|
| [PostgreSQL Development Assistant](../prompts/postgresql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-optimization.prompt.md) | Prompt | PostgreSQL-specific development assistant focusing on unique PostgreSQL features, advanced data types, and PostgreSQL-exclusive capabilities. Covers JSONB operations, array types, custom types, range/geometric types, full-text search, window functions, and PostgreSQL extensions ecosystem. |
|
||||||
|
| [SQL Code Review](../prompts/sql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md) | Prompt | Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage. |
|
||||||
|
| [SQL Development](../instructions/sql-sp-generation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fsql-sp-generation.instructions.md)<br />[](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%2Fsql-sp-generation.instructions.md) | Instruction | Guidelines for generating SQL statements and stored procedures |
|
||||||
|
| [SQL Performance Optimization Assistant](../prompts/sql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-optimization.prompt.md) | Prompt | Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance. |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 8 curated items for database & data management.*
|
||||||
18
collections/devops-oncall.collection.yml
Normal file
18
collections/devops-oncall.collection.yml
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
id: devops-oncall
|
||||||
|
name: DevOps On-Call
|
||||||
|
description: A focused set of prompts, instructions, and a chat mode to help triage incidents and respond quickly with DevOps tools and Azure resources.
|
||||||
|
tags: [devops, incident-response, oncall, azure]
|
||||||
|
items:
|
||||||
|
- path: prompts/azure-resource-health-diagnose.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: instructions/devops-core-principles.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/containerization-docker-best-practices.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: chatmodes/azure-principal-architect.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: prompts/multi-stage-dockerfile.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
display:
|
||||||
|
ordering: manual
|
||||||
|
show_badge: true
|
||||||
18
collections/devops-oncall.md
Normal file
18
collections/devops-oncall.md
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
# DevOps On-Call
|
||||||
|
|
||||||
|
A focused set of prompts, instructions, and a chat mode to help triage incidents and respond quickly with DevOps tools and Azure resources.
|
||||||
|
|
||||||
|
**Tags:** devops, incident-response, oncall, azure
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [Azure Resource Health & Issue Diagnosis](../prompts/azure-resource-health-diagnose.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md) | Prompt | Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems. |
|
||||||
|
| [DevOps Core Principles](../instructions/devops-core-principles.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdevops-core-principles.instructions.md)<br />[](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%2Fdevops-core-principles.instructions.md) | Instruction | Foundational instructions covering core DevOps principles, culture (CALMS), and key metrics (DORA) to guide GitHub Copilot in understanding and promoting effective software delivery. |
|
||||||
|
| [Containerization & Docker Best Practices](../instructions/containerization-docker-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontainerization-docker-best-practices.instructions.md)<br />[](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%2Fcontainerization-docker-best-practices.instructions.md) | Instruction | Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. |
|
||||||
|
| [Azure Principal Architect mode instructions](../chatmodes/azure-principal-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-principal-architect.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fazure-principal-architect.chatmode.md) | Chat Mode | Provide expert Azure Principal Architect guidance using Azure Well-Architected Framework principles and Microsoft best practices. |
|
||||||
|
| [Multi Stage Dockerfile](../prompts/multi-stage-dockerfile.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmulti-stage-dockerfile.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmulti-stage-dockerfile.prompt.md) | Prompt | Create optimized multi-stage Dockerfiles for any language or framework |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 5 curated items for devops on-call.*
|
||||||
36
collections/frontend-web-dev.collection.yml
Normal file
36
collections/frontend-web-dev.collection.yml
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
id: frontend-web-dev
|
||||||
|
name: Frontend Web Development
|
||||||
|
description: Essential prompts, instructions, and chat modes for modern frontend web development including React, Angular, Vue, TypeScript, and CSS frameworks.
|
||||||
|
tags: [frontend, web, react, typescript, javascript, css, html, angular, vue]
|
||||||
|
items:
|
||||||
|
# Expert Chat Modes
|
||||||
|
- path: chatmodes/expert-react-frontend-engineer.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/electron-angular-native.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
|
||||||
|
# Development Instructions
|
||||||
|
- path: instructions/reactjs.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/angular.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/vuejs3.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/nextjs.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/nextjs-tailwind.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/tanstack-start-shadcn-tailwind.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/nodejs-javascript-vitest.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Prompts
|
||||||
|
- path: prompts/playwright-explore-website.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/playwright-generate-test.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: true
|
||||||
24
collections/frontend-web-dev.md
Normal file
24
collections/frontend-web-dev.md
Normal file
@ -0,0 +1,24 @@
|
|||||||
|
# Frontend Web Development
|
||||||
|
|
||||||
|
Essential prompts, instructions, and chat modes for modern frontend web development including React, Angular, Vue, TypeScript, and CSS frameworks.
|
||||||
|
|
||||||
|
**Tags:** frontend, web, react, typescript, javascript, css, html, angular, vue
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [Angular Development Instructions](../instructions/angular.instructions.md)<br />[](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)<br />[](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) | Instruction | Angular-specific coding standards and best practices |
|
||||||
|
| [Code Generation Guidelines](../instructions/nodejs-javascript-vitest.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fnodejs-javascript-vitest.instructions.md)<br />[](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%2Fnodejs-javascript-vitest.instructions.md) | Instruction | Guidelines for writing Node.js and JavaScript code with Vitest testing |
|
||||||
|
| [Electron Code Review Mode Instructions](../chatmodes/electron-angular-native.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Felectron-angular-native.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Felectron-angular-native.chatmode.md) | Chat Mode | Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here. |
|
||||||
|
| [Expert React Frontend Engineer Mode Instructions](../chatmodes/expert-react-frontend-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-react-frontend-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-react-frontend-engineer.chatmode.md) | Chat Mode | Provide expert React frontend engineering guidance using modern TypeScript and design patterns. |
|
||||||
|
| [Next.js + Tailwind Development Instructions](../instructions/nextjs-tailwind.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fnextjs-tailwind.instructions.md)<br />[](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%2Fnextjs-tailwind.instructions.md) | Instruction | Next.js + Tailwind development standards and instructions |
|
||||||
|
| [Next.js Best Practices for LLMs (2025)](../instructions/nextjs.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fnextjs.instructions.md)<br />[](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%2Fnextjs.instructions.md) | Instruction | No description |
|
||||||
|
| [ReactJS Development Instructions](../instructions/reactjs.instructions.md)<br />[](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)<br />[](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) | Instruction | ReactJS development standards and best practices |
|
||||||
|
| [TanStack Start with Shadcn/ui Development Guide](../instructions/tanstack-start-shadcn-tailwind.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftanstack-start-shadcn-tailwind.instructions.md)<br />[](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%2Ftanstack-start-shadcn-tailwind.instructions.md) | Instruction | Guidelines for building TanStack Start applications |
|
||||||
|
| [Test Generation with Playwright MCP](../prompts/playwright-generate-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-generate-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-generate-test.prompt.md) | Prompt | Generate a Playwright test based on a scenario using Playwright MCP |
|
||||||
|
| [VueJS 3 Development Instructions](../instructions/vuejs3.instructions.md)<br />[](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)<br />[](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) | Instruction | VueJS 3 development standards and best practices with Composition API and TypeScript |
|
||||||
|
| [Website Exploration for Testing](../prompts/playwright-explore-website.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-explore-website.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-explore-website.prompt.md) | Prompt | Website exploration for testing using Playwright MCP |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 11 curated items for frontend web development.*
|
||||||
48
collections/project-planning.collection.yml
Normal file
48
collections/project-planning.collection.yml
Normal file
@ -0,0 +1,48 @@
|
|||||||
|
id: project-planning
|
||||||
|
name: Project Planning & Management
|
||||||
|
description: Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams.
|
||||||
|
tags: [planning, project-management, epic, feature, implementation, task, architecture, technical-spike]
|
||||||
|
items:
|
||||||
|
# Planning Chat Modes
|
||||||
|
- path: chatmodes/task-planner.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/task-researcher.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/planner.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/plan.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/prd.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/implementation-plan.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/research-technical-spike.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
|
||||||
|
# Planning Instructions
|
||||||
|
- path: instructions/task-implementation.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/spec-driven-workflow-v1.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Planning Prompts
|
||||||
|
- path: prompts/breakdown-feature-implementation.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/breakdown-feature-prd.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/breakdown-epic-arch.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/breakdown-epic-pm.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/create-implementation-plan.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/update-implementation-plan.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/create-github-issues-feature-from-implementation-plan.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/create-technical-spike.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: true
|
||||||
30
collections/project-planning.md
Normal file
30
collections/project-planning.md
Normal file
@ -0,0 +1,30 @@
|
|||||||
|
# Project Planning & Management
|
||||||
|
|
||||||
|
Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams.
|
||||||
|
|
||||||
|
**Tags:** planning, project-management, epic, feature, implementation, task, architecture, technical-spike
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [Create GitHub Issue from Implementation Plan](../prompts/create-github-issues-feature-from-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issues-feature-from-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issues-feature-from-implementation-plan.prompt.md) | Prompt | Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates. |
|
||||||
|
| [Create Implementation Plan](../prompts/create-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-implementation-plan.prompt.md) | Prompt | Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure. |
|
||||||
|
| [Create PRD Chat Mode](../chatmodes/prd.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprd.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fprd.chatmode.md) | Chat Mode | Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics. Optionally create GitHub issues upon user confirmation. |
|
||||||
|
| [Create Technical Spike Document](../prompts/create-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md) | Prompt | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. |
|
||||||
|
| [Epic Architecture Specification Prompt](../prompts/breakdown-epic-arch.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-arch.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-arch.prompt.md) | Prompt | Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document. |
|
||||||
|
| [Epic Product Requirements Document (PRD) Prompt](../prompts/breakdown-epic-pm.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-pm.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-pm.prompt.md) | Prompt | Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification. |
|
||||||
|
| [Feature Implementation Plan Prompt](../prompts/breakdown-feature-implementation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-implementation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-implementation.prompt.md) | Prompt | Prompt for creating detailed feature implementation plans, following Epoch monorepo structure. |
|
||||||
|
| [Feature PRD Prompt](../prompts/breakdown-feature-prd.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-prd.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-prd.prompt.md) | Prompt | Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic. |
|
||||||
|
| [Implementation Plan Generation Mode](../chatmodes/implementation-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fimplementation-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fimplementation-plan.chatmode.md) | Chat Mode | Generate an implementation plan for new features or refactoring existing code. |
|
||||||
|
| [Plan Mode - Strategic Planning & Architecture Assistant](../chatmodes/plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fplan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fplan.chatmode.md) | Chat Mode | Strategic planning and architecture assistant focused on thoughtful analysis before implementation. Helps developers understand codebases, clarify requirements, and develop comprehensive implementation strategies. |
|
||||||
|
| [Planning mode instructions](../chatmodes/planner.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fplanner.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fplanner.chatmode.md) | Chat Mode | Generate an implementation plan for new features or refactoring existing code. |
|
||||||
|
| [Spec Driven Workflow v1](../instructions/spec-driven-workflow-v1.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fspec-driven-workflow-v1.instructions.md)<br />[](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%2Fspec-driven-workflow-v1.instructions.md) | Instruction | Specification-Driven Workflow v1 provides a structured approach to software development, ensuring that requirements are clearly defined, designs are meticulously planned, and implementations are thoroughly documented and validated. |
|
||||||
|
| [Task Plan Implementation Instructions](../instructions/task-implementation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftask-implementation.instructions.md)<br />[](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%2Ftask-implementation.instructions.md) | Instruction | Instructions for implementing task plans with progressive tracking and change record - Brought to you by microsoft/edge-ai |
|
||||||
|
| [Task Planner Instructions](../chatmodes/task-planner.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-planner.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-planner.chatmode.md) | Chat Mode | Task planner for creating actionable implementation plans - Brought to you by microsoft/edge-ai |
|
||||||
|
| [Task Researcher Instructions](../chatmodes/task-researcher.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-researcher.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-researcher.chatmode.md) | Chat Mode | Task research specialist for comprehensive project analysis - Brought to you by microsoft/edge-ai |
|
||||||
|
| [Technical spike research mode](../chatmodes/research-technical-spike.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fresearch-technical-spike.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fresearch-technical-spike.chatmode.md) | Chat Mode | Systematically research and validate technical spike documents through exhaustive investigation and controlled experimentation. |
|
||||||
|
| [Update Implementation Plan](../prompts/update-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-implementation-plan.prompt.md) | Prompt | Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure. |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 17 curated items for project planning & management.*
|
||||||
24
collections/security-best-practices.collection.yml
Normal file
24
collections/security-best-practices.collection.yml
Normal file
@ -0,0 +1,24 @@
|
|||||||
|
id: security-best-practices
|
||||||
|
name: Security & Code Quality
|
||||||
|
description: Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications.
|
||||||
|
tags: [security, accessibility, performance, code-quality, owasp, a11y, optimization, best-practices]
|
||||||
|
items:
|
||||||
|
# Security & Quality Instructions
|
||||||
|
- path: instructions/security-and-owasp.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/a11y.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/performance-optimization.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/object-calisthenics.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/self-explanatory-code-commenting.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Security & Safety Prompts
|
||||||
|
- path: prompts/ai-prompt-engineering-safety-review.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: true
|
||||||
19
collections/security-best-practices.md
Normal file
19
collections/security-best-practices.md
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
# Security & Code Quality
|
||||||
|
|
||||||
|
Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications.
|
||||||
|
|
||||||
|
**Tags:** security, accessibility, performance, code-quality, owasp, a11y, optimization, best-practices
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [AI Prompt Engineering Safety Review & Improvement](../prompts/ai-prompt-engineering-safety-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fai-prompt-engineering-safety-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fai-prompt-engineering-safety-review.prompt.md) | Prompt | Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content. |
|
||||||
|
| [Instructions for accessibility](../instructions/a11y.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fa11y.instructions.md)<br />[](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%2Fa11y.instructions.md) | Instruction | Guidance for creating more accessible code |
|
||||||
|
| [Object Calisthenics Rules](../instructions/object-calisthenics.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fobject-calisthenics.instructions.md)<br />[](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%2Fobject-calisthenics.instructions.md) | Instruction | Enforces Object Calisthenics principles for business domain code to ensure clean, maintainable, and robust code |
|
||||||
|
| [Performance Optimization Best Practices](../instructions/performance-optimization.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fperformance-optimization.instructions.md)<br />[](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%2Fperformance-optimization.instructions.md) | Instruction | The most comprehensive, practical, and engineer-authored performance optimization instructions for all languages, frameworks, and stacks. Covers frontend, backend, and database best practices with actionable guidance, scenario-based checklists, troubleshooting, and pro tips. |
|
||||||
|
| [Secure Coding and OWASP Guidelines](../instructions/security-and-owasp.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fsecurity-and-owasp.instructions.md)<br />[](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%2Fsecurity-and-owasp.instructions.md) | Instruction | Comprehensive secure coding instructions for all languages and frameworks, based on OWASP Top 10 and industry best practices. |
|
||||||
|
| [Self-explanatory Code Commenting Instructions](../instructions/self-explanatory-code-commenting.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fself-explanatory-code-commenting.instructions.md)<br />[](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%2Fself-explanatory-code-commenting.instructions.md) | Instruction | Guidelines for GitHub Copilot to write comments to achieve self-explanatory code with less comments. Examples are in JavaScript but it should work on any language that has comments. |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 6 curated items for security & code quality.*
|
||||||
15
collections/technical-spike.collection.yml
Normal file
15
collections/technical-spike.collection.yml
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
id: technical-spike
|
||||||
|
name: Technical Spike
|
||||||
|
description: Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions.
|
||||||
|
tags: [technical-spike, assumption-testing, validation, research]
|
||||||
|
items:
|
||||||
|
# Planning Chat Modes
|
||||||
|
- path: chatmodes/research-technical-spike.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
|
||||||
|
# Planning Prompts
|
||||||
|
- path: prompts/create-technical-spike.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
display:
|
||||||
|
ordering: alpha # or "manual" to preserve the order above
|
||||||
|
show_badge: false # set to true to show collection badge on items
|
||||||
15
collections/technical-spike.md
Normal file
15
collections/technical-spike.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
# Technical Spike
|
||||||
|
|
||||||
|
Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions.
|
||||||
|
|
||||||
|
**Tags:** technical-spike, assumption-testing, validation, research
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [Technical spike research mode](../chatmodes/research-technical-spike.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fresearch-technical-spike.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fresearch-technical-spike.chatmode.md) | Chat Mode | Systematically research and validate technical spike documents through exhaustive investigation and controlled experimentation. |
|
||||||
|
| [Create Technical Spike Document](../prompts/create-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md) | Prompt | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 2 curated items for technical spike.*
|
||||||
36
collections/testing-automation.collection.yml
Normal file
36
collections/testing-automation.collection.yml
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
id: testing-automation
|
||||||
|
name: Testing & Test Automation
|
||||||
|
description: Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies.
|
||||||
|
tags: [testing, tdd, automation, unit-tests, integration, playwright, jest, nunit]
|
||||||
|
items:
|
||||||
|
# TDD Chat Modes
|
||||||
|
- path: chatmodes/tdd-red.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/tdd-green.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/tdd-refactor.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
- path: chatmodes/playwright-tester.chatmode.md
|
||||||
|
kind: chat-mode
|
||||||
|
|
||||||
|
# Testing Instructions
|
||||||
|
- path: instructions/playwright-typescript.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
- path: instructions/playwright-python.instructions.md
|
||||||
|
kind: instruction
|
||||||
|
|
||||||
|
# Testing Prompts
|
||||||
|
- path: prompts/playwright-explore-website.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/playwright-generate-test.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/csharp-nunit.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/java-junit.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
- path: prompts/ai-prompt-engineering-safety-review.prompt.md
|
||||||
|
kind: prompt
|
||||||
|
|
||||||
|
display:
|
||||||
|
ordering: alpha
|
||||||
|
show_badge: true
|
||||||
24
collections/testing-automation.md
Normal file
24
collections/testing-automation.md
Normal file
@ -0,0 +1,24 @@
|
|||||||
|
# Testing & Test Automation
|
||||||
|
|
||||||
|
Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies.
|
||||||
|
|
||||||
|
**Tags:** testing, tdd, automation, unit-tests, integration, playwright, jest, nunit
|
||||||
|
|
||||||
|
## Items in this Collection
|
||||||
|
|
||||||
|
| Title | Type | Description |
|
||||||
|
| ----- | ---- | ----------- |
|
||||||
|
| [AI Prompt Engineering Safety Review & Improvement](../prompts/ai-prompt-engineering-safety-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fai-prompt-engineering-safety-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fai-prompt-engineering-safety-review.prompt.md) | Prompt | Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content. |
|
||||||
|
| [JUnit 5+ Best Practices](../prompts/java-junit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-junit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-junit.prompt.md) | Prompt | Get best practices for JUnit 5 unit testing, including data-driven tests |
|
||||||
|
| [NUnit Best Practices](../prompts/csharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md) | Prompt | Get best practices for NUnit unit testing, including data-driven tests |
|
||||||
|
| [Playwright Python Test Generation Instructions](../instructions/playwright-python.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fplaywright-python.instructions.md)<br />[](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%2Fplaywright-python.instructions.md) | Instruction | Playwright Python AI test generation instructions based on official documentation. |
|
||||||
|
| [Playwright Tester](../chatmodes/playwright-tester.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fplaywright-tester.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fplaywright-tester.chatmode.md) | Chat Mode | Testing mode for Playwright tests |
|
||||||
|
| [Playwright Typescript](../instructions/playwright-typescript.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fplaywright-typescript.instructions.md)<br />[](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%2Fplaywright-typescript.instructions.md) | Instruction | Playwright test generation instructions |
|
||||||
|
| [TDD Green Phase - Make Tests Pass Quickly](../chatmodes/tdd-green.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftdd-green.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftdd-green.chatmode.md) | Chat Mode | Implement minimal code to satisfy GitHub issue requirements and make failing tests pass without over-engineering. |
|
||||||
|
| [TDD Red Phase - Write Failing Tests First](../chatmodes/tdd-red.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftdd-red.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftdd-red.chatmode.md) | Chat Mode | Guide test-first development by writing failing tests that describe desired behaviour from GitHub issue context before implementation exists. |
|
||||||
|
| [TDD Refactor Phase - Improve Quality & Security](../chatmodes/tdd-refactor.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftdd-refactor.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftdd-refactor.chatmode.md) | Chat Mode | Improve code quality, apply security best practices, and enhance design whilst maintaining green tests and GitHub issue compliance. |
|
||||||
|
| [Test Generation with Playwright MCP](../prompts/playwright-generate-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-generate-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-generate-test.prompt.md) | Prompt | Generate a Playwright test based on a scenario using Playwright MCP |
|
||||||
|
| [Website Exploration for Testing](../prompts/playwright-explore-website.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-explore-website.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-explore-website.prompt.md) | Prompt | Website exploration for testing using Playwright MCP |
|
||||||
|
|
||||||
|
---
|
||||||
|
*This collection includes 11 curated items for testing & test automation.*
|
||||||
161
create-collection.js
Executable file
161
create-collection.js
Executable file
@ -0,0 +1,161 @@
|
|||||||
|
#!/usr/bin/env node
|
||||||
|
|
||||||
|
const fs = require("fs");
|
||||||
|
const path = require("path");
|
||||||
|
const readline = require("readline");
|
||||||
|
|
||||||
|
const rl = readline.createInterface({
|
||||||
|
input: process.stdin,
|
||||||
|
output: process.stdout
|
||||||
|
});
|
||||||
|
|
||||||
|
function prompt(question) {
|
||||||
|
return new Promise((resolve) => {
|
||||||
|
rl.question(question, resolve);
|
||||||
|
});
|
||||||
|
}
|
||||||
|
|
||||||
|
function parseArgs() {
|
||||||
|
const args = process.argv.slice(2);
|
||||||
|
const out = { id: undefined, tags: undefined };
|
||||||
|
|
||||||
|
// simple long/short option parsing
|
||||||
|
for (let i = 0; i < args.length; i++) {
|
||||||
|
const a = args[i];
|
||||||
|
if (a === '--id' || a === '-i') {
|
||||||
|
out.id = args[i + 1];
|
||||||
|
i++;
|
||||||
|
} else if (a.startsWith('--id=')) {
|
||||||
|
out.id = a.split('=')[1];
|
||||||
|
} else if (a === '--tags' || a === '-t') {
|
||||||
|
out.tags = args[i + 1];
|
||||||
|
i++;
|
||||||
|
} else if (a.startsWith('--tags=')) {
|
||||||
|
out.tags = a.split('=')[1];
|
||||||
|
} else if (!a.startsWith('-') && !out.id) {
|
||||||
|
// first positional -> id
|
||||||
|
out.id = a;
|
||||||
|
} else if (!a.startsWith('-') && out.id && !out.tags) {
|
||||||
|
// second positional -> tags
|
||||||
|
out.tags = a;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
// normalize tags to string (comma separated) or undefined
|
||||||
|
if (Array.isArray(out.tags)) {
|
||||||
|
out.tags = out.tags.join(',');
|
||||||
|
}
|
||||||
|
|
||||||
|
return out;
|
||||||
|
}
|
||||||
|
|
||||||
|
async function createCollectionTemplate() {
|
||||||
|
try {
|
||||||
|
console.log("🎯 Collection Creator");
|
||||||
|
console.log("This tool will help you create a new collection manifest.\n");
|
||||||
|
|
||||||
|
// Parse CLI args and fall back to interactive prompts when missing
|
||||||
|
const parsed = parseArgs();
|
||||||
|
// Get collection ID
|
||||||
|
let collectionId = parsed.id;
|
||||||
|
if (!collectionId) {
|
||||||
|
collectionId = await prompt("Collection ID (lowercase, hyphens only): ");
|
||||||
|
}
|
||||||
|
|
||||||
|
// Validate collection ID format
|
||||||
|
if (!collectionId) {
|
||||||
|
console.error("❌ Collection ID is required");
|
||||||
|
process.exit(1);
|
||||||
|
}
|
||||||
|
|
||||||
|
if (!/^[a-z0-9-]+$/.test(collectionId)) {
|
||||||
|
console.error("❌ Collection ID must contain only lowercase letters, numbers, and hyphens");
|
||||||
|
process.exit(1);
|
||||||
|
}
|
||||||
|
|
||||||
|
const collectionsDir = path.join(__dirname, "collections");
|
||||||
|
const filePath = path.join(collectionsDir, `${collectionId}.collection.yml`);
|
||||||
|
|
||||||
|
// Check if file already exists
|
||||||
|
if (fs.existsSync(filePath)) {
|
||||||
|
console.log(`⚠️ Collection ${collectionId} already exists at ${filePath}`);
|
||||||
|
console.log("💡 Please edit that file instead or choose a different ID.");
|
||||||
|
process.exit(1);
|
||||||
|
}
|
||||||
|
|
||||||
|
// Ensure collections directory exists
|
||||||
|
if (!fs.existsSync(collectionsDir)) {
|
||||||
|
fs.mkdirSync(collectionsDir, { recursive: true });
|
||||||
|
}
|
||||||
|
|
||||||
|
// Get collection name
|
||||||
|
const defaultName = collectionId
|
||||||
|
.split("-")
|
||||||
|
.map(word => word.charAt(0).toUpperCase() + word.slice(1))
|
||||||
|
.join(" ");
|
||||||
|
|
||||||
|
let collectionName = await prompt(`Collection name (default: ${defaultName}): `);
|
||||||
|
if (!collectionName.trim()) {
|
||||||
|
collectionName = defaultName;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Get description
|
||||||
|
const defaultDescription = `A collection of related prompts, instructions, and chat modes for ${collectionName.toLowerCase()}.`;
|
||||||
|
let description = await prompt(`Description (default: ${defaultDescription}): `);
|
||||||
|
if (!description.trim()) {
|
||||||
|
description = defaultDescription;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Get tags (from CLI or prompt)
|
||||||
|
let tags = [];
|
||||||
|
let tagInput = parsed.tags;
|
||||||
|
if (!tagInput) {
|
||||||
|
tagInput = await prompt("Tags (comma-separated, or press Enter for defaults): ");
|
||||||
|
}
|
||||||
|
|
||||||
|
if (tagInput && tagInput.toString().trim()) {
|
||||||
|
tags = tagInput.toString().split(",").map(tag => tag.trim()).filter(tag => tag);
|
||||||
|
} else {
|
||||||
|
// Generate some default tags from the collection ID
|
||||||
|
tags = collectionId.split("-").slice(0, 3);
|
||||||
|
}
|
||||||
|
|
||||||
|
// Template content
|
||||||
|
const template = `id: ${collectionId}
|
||||||
|
name: ${collectionName}
|
||||||
|
description: ${description}
|
||||||
|
tags: [${tags.join(", ")}]
|
||||||
|
items:
|
||||||
|
# Add your collection items here
|
||||||
|
# Example:
|
||||||
|
# - path: prompts/example.prompt.md
|
||||||
|
# kind: prompt
|
||||||
|
# - path: instructions/example.instructions.md
|
||||||
|
# kind: instruction
|
||||||
|
# - path: chatmodes/example.chatmode.md
|
||||||
|
# kind: chat-mode
|
||||||
|
display:
|
||||||
|
ordering: alpha # or "manual" to preserve the order above
|
||||||
|
show_badge: false # set to true to show collection badge on items
|
||||||
|
`;
|
||||||
|
|
||||||
|
fs.writeFileSync(filePath, template);
|
||||||
|
console.log(`✅ Created collection template: ${filePath}`);
|
||||||
|
console.log("\n📝 Next steps:");
|
||||||
|
console.log("1. Edit the collection manifest to add your items");
|
||||||
|
console.log("2. Update the name, description, and tags as needed");
|
||||||
|
console.log("3. Run 'node validate-collections.js' to validate");
|
||||||
|
console.log("4. Run 'node update-readme.js' to generate documentation");
|
||||||
|
console.log("\n📄 Collection template contents:");
|
||||||
|
console.log(template);
|
||||||
|
|
||||||
|
} catch (error) {
|
||||||
|
console.error(`❌ Error creating collection template: ${error.message}`);
|
||||||
|
process.exit(1);
|
||||||
|
} finally {
|
||||||
|
rl.close();
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
// Run the interactive creation process
|
||||||
|
createCollectionTemplate();
|
||||||
54
instructions/collections.instructions.md
Normal file
54
instructions/collections.instructions.md
Normal file
@ -0,0 +1,54 @@
|
|||||||
|
---
|
||||||
|
description: 'Guidelines for creating and managing awesome-copilot collections'
|
||||||
|
applyTo: 'collections/*.collection.yml'
|
||||||
|
---
|
||||||
|
|
||||||
|
# Collections Development
|
||||||
|
|
||||||
|
## Collection Instructions
|
||||||
|
|
||||||
|
When working with collections in the awesome-copilot repository:
|
||||||
|
|
||||||
|
- Always validate collections using `node validate-collections.js` before committing
|
||||||
|
- Follow the established YAML schema for collection manifests
|
||||||
|
- Reference only existing files in the repository
|
||||||
|
- Use descriptive collection IDs with lowercase letters, numbers, and hyphens
|
||||||
|
- Keep collections focused on specific workflows or themes
|
||||||
|
- Test that all referenced items work well together
|
||||||
|
|
||||||
|
## Collection Structure
|
||||||
|
|
||||||
|
- **Required fields**: id, name, description, items
|
||||||
|
- **Optional fields**: tags, display
|
||||||
|
- **Item requirements**: path must exist, kind must match file extension
|
||||||
|
- **Display options**: ordering (alpha/manual), show_badge (true/false)
|
||||||
|
|
||||||
|
## Validation Rules
|
||||||
|
|
||||||
|
- Collection IDs must be unique across all collections
|
||||||
|
- File paths must exist and match the item kind
|
||||||
|
- Tags must use lowercase letters, numbers, and hyphens only
|
||||||
|
- Collections must contain 1-50 items
|
||||||
|
- Descriptions must be 1-500 characters
|
||||||
|
|
||||||
|
## Best Practices
|
||||||
|
|
||||||
|
- Group 3-10 related items for optimal usability
|
||||||
|
- Use clear, descriptive names and descriptions
|
||||||
|
- Add relevant tags for discoverability
|
||||||
|
- Test the complete workflow the collection enables
|
||||||
|
- Ensure items complement each other effectively
|
||||||
|
|
||||||
|
## File Organization
|
||||||
|
|
||||||
|
- Collections don't require file reorganization
|
||||||
|
- Items can be located anywhere in the repository
|
||||||
|
- Use relative paths from repository root
|
||||||
|
- Maintain existing directory structure (prompts/, instructions/, chatmodes/)
|
||||||
|
|
||||||
|
## Generation Process
|
||||||
|
|
||||||
|
- Collections automatically generate README files via `update-readme.js`
|
||||||
|
- Individual collection pages are created in collections/ directory
|
||||||
|
- Main collections overview is generated as README.collections.md
|
||||||
|
- VS Code install badges are automatically created for each item
|
||||||
316
instructions/declarative-agents-microsoft365.instructions.md
Normal file
316
instructions/declarative-agents-microsoft365.instructions.md
Normal file
@ -0,0 +1,316 @@
|
|||||||
|
---
|
||||||
|
description: Comprehensive development guidelines for Microsoft 365 Copilot declarative agents with schema v1.5, TypeSpec integration, and Microsoft 365 Agents Toolkit workflows
|
||||||
|
applyTo: "**.json, **.ts, **.tsp, **manifest.json, **agent.json, **declarative-agent.json"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Microsoft 365 Declarative Agents Development Guidelines
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
|
||||||
|
Microsoft 365 Copilot declarative agents are powerful custom AI assistants that extend Microsoft 365 Copilot with specialized capabilities, enterprise data access, and custom behaviors. These guidelines provide comprehensive development practices for creating production-ready agents using the latest v1.5 JSON schema specification with full Microsoft 365 Agents Toolkit integration.
|
||||||
|
|
||||||
|
## Schema Specification v1.5
|
||||||
|
|
||||||
|
### Core Properties
|
||||||
|
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"$schema": "https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.5/schema.json",
|
||||||
|
"version": "v1.5",
|
||||||
|
"name": "string (max 100 characters)",
|
||||||
|
"description": "string (max 1000 characters)",
|
||||||
|
"instructions": "string (max 8000 characters)",
|
||||||
|
"capabilities": ["array (max 5 items)"],
|
||||||
|
"conversation_starters": ["array (max 4 items, optional)"]
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
### Character Limits & Constraints
|
||||||
|
- **Name**: Maximum 100 characters, required
|
||||||
|
- **Description**: Maximum 1000 characters, required
|
||||||
|
- **Instructions**: Maximum 8000 characters, required
|
||||||
|
- **Capabilities**: Maximum 5 items, minimum 1 item
|
||||||
|
- **Conversation Starters**: Maximum 4 items, optional
|
||||||
|
|
||||||
|
## Available Capabilities
|
||||||
|
|
||||||
|
### Core Capabilities
|
||||||
|
1. **WebSearch**: Internet search and real-time information access
|
||||||
|
2. **OneDriveAndSharePoint**: File access, document search, content management
|
||||||
|
3. **GraphConnectors**: Enterprise data integration from third-party systems
|
||||||
|
4. **MicrosoftGraph**: Access to Microsoft 365 services and data
|
||||||
|
|
||||||
|
### Communication & Collaboration
|
||||||
|
5. **TeamsAndOutlook**: Teams chat, meetings, email integration
|
||||||
|
6. **CopilotForMicrosoft365**: Advanced Copilot features and workflows
|
||||||
|
|
||||||
|
### Business Applications
|
||||||
|
7. **PowerPlatform**: Power Apps, Power Automate, Power BI integration
|
||||||
|
8. **BusinessDataProcessing**: Advanced data analysis and processing
|
||||||
|
9. **WordAndExcel**: Document creation, editing, analysis
|
||||||
|
10. **EnterpriseApplications**: Third-party business system integration
|
||||||
|
11. **CustomConnectors**: Custom API and service integrations
|
||||||
|
|
||||||
|
## Microsoft 365 Agents Toolkit Integration
|
||||||
|
|
||||||
|
### VS Code Extension Setup
|
||||||
|
```bash
|
||||||
|
# Install Microsoft 365 Agents Toolkit
|
||||||
|
# Extension ID: teamsdevapp.ms-teams-vscode-extension
|
||||||
|
```
|
||||||
|
|
||||||
|
### TypeSpec Development Workflow
|
||||||
|
|
||||||
|
#### 1. Modern Agent Definition
|
||||||
|
```typespec
|
||||||
|
import "@typespec/json-schema";
|
||||||
|
|
||||||
|
using TypeSpec.JsonSchema;
|
||||||
|
|
||||||
|
@jsonSchema("/schemas/declarative-agent/v1.5/schema.json")
|
||||||
|
namespace DeclarativeAgent;
|
||||||
|
|
||||||
|
/** Microsoft 365 Declarative Agent */
|
||||||
|
model Agent {
|
||||||
|
/** Schema version */
|
||||||
|
@minLength(1)
|
||||||
|
$schema: "https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.5/schema.json";
|
||||||
|
|
||||||
|
/** Agent version */
|
||||||
|
version: "v1.5";
|
||||||
|
|
||||||
|
/** Agent name (max 100 characters) */
|
||||||
|
@maxLength(100)
|
||||||
|
@minLength(1)
|
||||||
|
name: string;
|
||||||
|
|
||||||
|
/** Agent description (max 1000 characters) */
|
||||||
|
@maxLength(1000)
|
||||||
|
@minLength(1)
|
||||||
|
description: string;
|
||||||
|
|
||||||
|
/** Agent instructions (max 8000 characters) */
|
||||||
|
@maxLength(8000)
|
||||||
|
@minLength(1)
|
||||||
|
instructions: string;
|
||||||
|
|
||||||
|
/** Agent capabilities (1-5 items) */
|
||||||
|
@minItems(1)
|
||||||
|
@maxItems(5)
|
||||||
|
capabilities: AgentCapability[];
|
||||||
|
|
||||||
|
/** Conversation starters (max 4 items) */
|
||||||
|
@maxItems(4)
|
||||||
|
conversation_starters?: ConversationStarter[];
|
||||||
|
}
|
||||||
|
|
||||||
|
/** Available agent capabilities */
|
||||||
|
union AgentCapability {
|
||||||
|
"WebSearch",
|
||||||
|
"OneDriveAndSharePoint",
|
||||||
|
"GraphConnectors",
|
||||||
|
"MicrosoftGraph",
|
||||||
|
"TeamsAndOutlook",
|
||||||
|
"PowerPlatform",
|
||||||
|
"BusinessDataProcessing",
|
||||||
|
"WordAndExcel",
|
||||||
|
"CopilotForMicrosoft365",
|
||||||
|
"EnterpriseApplications",
|
||||||
|
"CustomConnectors"
|
||||||
|
}
|
||||||
|
|
||||||
|
/** Conversation starter definition */
|
||||||
|
model ConversationStarter {
|
||||||
|
/** Starter text (max 100 characters) */
|
||||||
|
@maxLength(100)
|
||||||
|
@minLength(1)
|
||||||
|
text: string;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
#### 2. Compilation to JSON
|
||||||
|
```bash
|
||||||
|
# Compile TypeSpec to JSON manifest
|
||||||
|
tsp compile agent.tsp --emit=@typespec/json-schema
|
||||||
|
```
|
||||||
|
|
||||||
|
### Environment Configuration
|
||||||
|
|
||||||
|
#### Development Environment
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"name": "${DEV_AGENT_NAME}",
|
||||||
|
"description": "Development version: ${AGENT_DESCRIPTION}",
|
||||||
|
"instructions": "${AGENT_INSTRUCTIONS}",
|
||||||
|
"capabilities": ["${REQUIRED_CAPABILITIES}"]
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Production Environment
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"name": "${PROD_AGENT_NAME}",
|
||||||
|
"description": "${AGENT_DESCRIPTION}",
|
||||||
|
"instructions": "${AGENT_INSTRUCTIONS}",
|
||||||
|
"capabilities": ["${PRODUCTION_CAPABILITIES}"]
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
## Development Best Practices
|
||||||
|
|
||||||
|
### 1. Schema Validation
|
||||||
|
```typescript
|
||||||
|
// Validate against v1.5 schema
|
||||||
|
const schema = await fetch('https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.5/schema.json');
|
||||||
|
const validator = new JSONSchema(schema);
|
||||||
|
const isValid = validator.validate(agentManifest);
|
||||||
|
```
|
||||||
|
|
||||||
|
### 2. Character Limit Management
|
||||||
|
```typescript
|
||||||
|
// Validation helper functions
|
||||||
|
function validateName(name: string): boolean {
|
||||||
|
return name.length > 0 && name.length <= 100;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateDescription(description: string): boolean {
|
||||||
|
return description.length > 0 && description.length <= 1000;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateInstructions(instructions: string): boolean {
|
||||||
|
return instructions.length > 0 && instructions.length <= 8000;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
### 3. Capability Selection Strategy
|
||||||
|
- **Start Simple**: Begin with 1-2 core capabilities
|
||||||
|
- **Incremental Addition**: Add capabilities based on user feedback
|
||||||
|
- **Performance Testing**: Test each capability combination thoroughly
|
||||||
|
- **Enterprise Readiness**: Consider compliance and security implications
|
||||||
|
|
||||||
|
## Agents Playground Testing
|
||||||
|
|
||||||
|
### Local Testing Setup
|
||||||
|
```bash
|
||||||
|
# Start Agents Playground
|
||||||
|
npm install -g @microsoft/agents-playground
|
||||||
|
agents-playground start --manifest=./agent.json
|
||||||
|
```
|
||||||
|
|
||||||
|
### Testing Scenarios
|
||||||
|
1. **Capability Validation**: Test each declared capability
|
||||||
|
2. **Conversation Flow**: Validate conversation starters
|
||||||
|
3. **Error Handling**: Test invalid inputs and edge cases
|
||||||
|
4. **Performance**: Measure response times and reliability
|
||||||
|
|
||||||
|
## Deployment & Lifecycle Management
|
||||||
|
|
||||||
|
### 1. Development Lifecycle
|
||||||
|
```mermaid
|
||||||
|
graph LR
|
||||||
|
A[TypeSpec Definition] --> B[JSON Compilation]
|
||||||
|
B --> C[Local Testing]
|
||||||
|
C --> D[Validation]
|
||||||
|
D --> E[Staging Deployment]
|
||||||
|
E --> F[Production Release]
|
||||||
|
```
|
||||||
|
|
||||||
|
### 2. Version Management
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"name": "MyAgent v1.2.0",
|
||||||
|
"description": "Production agent with enhanced capabilities",
|
||||||
|
"version": "v1.5",
|
||||||
|
"metadata": {
|
||||||
|
"version": "1.2.0",
|
||||||
|
"build": "20241208.1",
|
||||||
|
"environment": "production"
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
### 3. Environment Promotion
|
||||||
|
- **Development**: Full debugging, verbose logging
|
||||||
|
- **Staging**: Production-like testing, performance monitoring
|
||||||
|
- **Production**: Optimized performance, minimal logging
|
||||||
|
|
||||||
|
## Advanced Features
|
||||||
|
|
||||||
|
### Behavior Overrides
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"instructions": "You are a specialized financial analyst agent. Always provide disclaimers for financial advice.",
|
||||||
|
"behavior_overrides": {
|
||||||
|
"response_tone": "professional",
|
||||||
|
"max_response_length": 2000,
|
||||||
|
"citation_requirements": true
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
### Localization Support
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"name": {
|
||||||
|
"en-US": "Financial Assistant",
|
||||||
|
"es-ES": "Asistente Financiero",
|
||||||
|
"fr-FR": "Assistant Financier"
|
||||||
|
},
|
||||||
|
"description": {
|
||||||
|
"en-US": "Provides financial analysis and insights",
|
||||||
|
"es-ES": "Proporciona análisis e insights financieros",
|
||||||
|
"fr-FR": "Fournit des analyses et insights financiers"
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
## Monitoring & Analytics
|
||||||
|
|
||||||
|
### Performance Metrics
|
||||||
|
- Response time per capability
|
||||||
|
- User engagement with conversation starters
|
||||||
|
- Error rates and failure patterns
|
||||||
|
- Capability utilization statistics
|
||||||
|
|
||||||
|
### Logging Strategy
|
||||||
|
```typescript
|
||||||
|
// Structured logging for agent interactions
|
||||||
|
const log = {
|
||||||
|
timestamp: new Date().toISOString(),
|
||||||
|
agentName: "MyAgent",
|
||||||
|
version: "1.2.0",
|
||||||
|
userId: "user123",
|
||||||
|
capability: "WebSearch",
|
||||||
|
responseTime: 1250,
|
||||||
|
success: true
|
||||||
|
};
|
||||||
|
```
|
||||||
|
|
||||||
|
## Security & Compliance
|
||||||
|
|
||||||
|
### Data Privacy
|
||||||
|
- Implement proper data handling for sensitive information
|
||||||
|
- Ensure compliance with GDPR, CCPA, and organizational policies
|
||||||
|
- Use appropriate access controls for enterprise capabilities
|
||||||
|
|
||||||
|
### Security Considerations
|
||||||
|
- Validate all inputs and outputs
|
||||||
|
- Implement rate limiting and abuse prevention
|
||||||
|
- Monitor for suspicious activity patterns
|
||||||
|
- Regular security audits and updates
|
||||||
|
|
||||||
|
## Troubleshooting
|
||||||
|
|
||||||
|
### Common Issues
|
||||||
|
1. **Schema Validation Errors**: Check character limits and required fields
|
||||||
|
2. **Capability Conflicts**: Verify capability combinations are supported
|
||||||
|
3. **Performance Issues**: Monitor response times and optimize instructions
|
||||||
|
4. **Deployment Failures**: Validate environment configuration and permissions
|
||||||
|
|
||||||
|
### Debug Tools
|
||||||
|
- TypeSpec compiler diagnostics
|
||||||
|
- Agents Playground debugging
|
||||||
|
- Microsoft 365 Agents Toolkit logs
|
||||||
|
- Schema validation utilities
|
||||||
|
|
||||||
|
This comprehensive guide ensures robust, scalable, and maintainable Microsoft 365 Copilot declarative agents with full TypeSpec and Microsoft 365 Agents Toolkit integration.
|
||||||
@ -1,23 +1,25 @@
|
|||||||
---
|
---
|
||||||
description: 'Expert assistance for Joyride User Script projects - REPL-driven ClojureScript and user space automation of VS Code'
|
description: 'Expert assistance for Joyride User Script projects - REPL-driven ClojureScript and user space automation of VS Code'
|
||||||
applyTo: 'scripts/**/*.cljs,src/**/*.cljs,deps.edn,.joyride/**/*.cljs'
|
applyTo: '**'
|
||||||
---
|
---
|
||||||
|
|
||||||
# Joyride User Script Project Assistant
|
# Joyride User Scripts Project Assistant
|
||||||
|
|
||||||
You are an expert Clojure interactive programmer specializing in Joyride - VS Code automation using ClojureScript. Joyride runs SCI ClojureScript in VS Code's Extension Host with full access to the VS Code API. Your main tool is `joyride_evaluate_code` with which you test and validate code directly in VS Code's runtime environment. The REPL is your superpower - use it to provide tested, working solutions rather than theoretical suggestions.
|
You are an expert Clojure interactive programmer specializing in Joyride - VS Code automation in user space. Joyride runs SCI ClojureScript in VS Code's Extension Host with full access to the VS Code API. Your main tool is **Joyride evaluation** with which you test and validate code directly in VS Code's runtime environment. The REPL is your superpower - use it to provide tested, working solutions rather than theoretical suggestions.
|
||||||
|
|
||||||
## Essential Information Sources
|
## Essential Information Sources
|
||||||
|
|
||||||
**Always use these tools first** to get comprehensive, up-to-date information:
|
**Always use these tools first** to get comprehensive, up-to-date information:
|
||||||
|
|
||||||
- `joyride_basics_for_agents` - Technical guide for LLM agents using Joyride evaluation capabilities
|
- **Joyride agent guide** - Technical guide for LLM agents using Joyride evaluation capabilities
|
||||||
- `joyride_assisting_users_guide` - Complete user assistance guide with project structure, patterns, examples, and troubleshooting
|
- **Joyride user guide** - Complete user assistance guide with project structure, patterns, examples, and troubleshooting
|
||||||
|
|
||||||
These tools contain all the detailed information about Joyride APIs, project structure, common patterns, user workflows, and troubleshooting guidance.
|
These tools contain all the detailed information about Joyride APIs, project structure, common patterns, user workflows, and troubleshooting guidance.
|
||||||
|
|
||||||
## Core Philosophy: Interactive Programming (aka REPL-Driven Development)
|
## Core Philosophy: Interactive Programming (aka REPL-Driven Development)
|
||||||
|
|
||||||
|
Please start by examining `README.md` and the code in the `scripts` and `src` folders of the project.
|
||||||
|
|
||||||
Only update files when the user asks you to. Prefer using the REPL to evaluate features into existence.
|
Only update files when the user asks you to. Prefer using the REPL to evaluate features into existence.
|
||||||
|
|
||||||
You develop the Clojure Way, data oriented, and building up solutions step by small step.
|
You develop the Clojure Way, data oriented, and building up solutions step by small step.
|
||||||
@ -28,9 +30,9 @@ The code will be data-oriented, functional code where functions take args and re
|
|||||||
|
|
||||||
Prefer destructuring, and maps for function arguments.
|
Prefer destructuring, and maps for function arguments.
|
||||||
|
|
||||||
Prefer namespaced keywords.
|
Prefer namespaced keywords. Consider using "synthetic" namespaces, like `:foo/something` to group things.
|
||||||
|
|
||||||
Prefer flatness over depth when modeling data. Consider using “synthetic” namespaces, like `:foo/something` to group things.
|
Prefer flatness over depth when modeling data.
|
||||||
|
|
||||||
When presented with a problem statement, you work through the problem iteratively step by step with the user.
|
When presented with a problem statement, you work through the problem iteratively step by step with the user.
|
||||||
|
|
||||||
@ -43,3 +45,157 @@ The expressions you evaluate do not have to be a complete function, they often a
|
|||||||
The main thing is to work step by step to incrementally develop a solution to a problem. This will help me see the solution you are developing and allow the user to guide its development.
|
The main thing is to work step by step to incrementally develop a solution to a problem. This will help me see the solution you are developing and allow the user to guide its development.
|
||||||
|
|
||||||
Always verify API usage in the REPL before updating files.
|
Always verify API usage in the REPL before updating files.
|
||||||
|
|
||||||
|
## AI Hacking VS Code in user space with Joyride, using Interactive Programming
|
||||||
|
|
||||||
|
When demonstrating what you can do with Joyride, remember to show your results in a visual way. E.g. if you count or summarize something, consider showing an information message with the result. Or consider creating a markdown file and show it in preview mode. Or, fancier still, create and open a web view that you can interact with through the Joyride REPL.
|
||||||
|
|
||||||
|
When demonstrating that you can create disposable items that stay in the UI, such as statusbar buttons, make sure to hold on to a reference to the object so that you can modify it and dispose of it.
|
||||||
|
|
||||||
|
Use the VS Code API via the correct interop syntax: vscode/api.method for functions and members, and plain JS objects instead of instantiating (e.g., `#js {:role "user" :content "..."}`).
|
||||||
|
|
||||||
|
Whenever in doubt, check with the user, the REPL and the docs, and iterate interactively together with the user!
|
||||||
|
|
||||||
|
## Essential APIs and Patterns
|
||||||
|
|
||||||
|
To load namespaces/files into the REPL, instead of `load-file` (which isn't implemented) use the Joyride (async) version: `joyride.core/load-file`.
|
||||||
|
|
||||||
|
### Namespace Targeting is Critical
|
||||||
|
|
||||||
|
When using the **Joyride evaluation** tool, always specify the correct namespace parameter. Functions defined without proper namespace targeting may end up in the wrong namespace (like `user` instead of your intended namespace), making them unavailable where expected.
|
||||||
|
|
||||||
|
### VS Code API Access
|
||||||
|
```clojure
|
||||||
|
(require '["vscode" :as vscode])
|
||||||
|
|
||||||
|
;; Common patterns users need
|
||||||
|
(vscode/window.showInformationMessage "Hello!")
|
||||||
|
(vscode/commands.executeCommand "workbench.action.files.save")
|
||||||
|
(vscode/window.showQuickPick #js ["Option 1" "Option 2"])
|
||||||
|
```
|
||||||
|
|
||||||
|
### Joyride Core API
|
||||||
|
```clojure
|
||||||
|
(require '[joyride.core :as joyride])
|
||||||
|
|
||||||
|
;; Key functions users should know:
|
||||||
|
joyride/*file* ; Current file path
|
||||||
|
(joyride/invoked-script) ; Script being run (nil in REPL)
|
||||||
|
(joyride/extension-context) ; VS Code extension context
|
||||||
|
(joyride/output-channel) ; Joyride's output channel
|
||||||
|
joyride/user-joyride-dir ; User joyride directory path
|
||||||
|
joyride/slurp ; Similar to Clojure `slurp`, but is async. Accepts absolute or relative (to the workspace) path. Returns a promise
|
||||||
|
joyride/load-file ; Similar to Clojure `load-file`, but is async. Accepts absolute or relative (to the workspace) path. Returns a promise
|
||||||
|
```
|
||||||
|
|
||||||
|
### Async Operation Handling
|
||||||
|
The evaluation tool has an `awaitResult` parameter for handling async operations:
|
||||||
|
|
||||||
|
- **`awaitResult: false` (default)**: Returns immediately, suitable for synchronous operations or fire-and-forget async evaluations
|
||||||
|
- **`awaitResult: true`**: Waits for async operations to complete before returning results, returns the resolved value of the promise
|
||||||
|
|
||||||
|
**When to use `awaitResult: true`:**
|
||||||
|
- User input dialogs where you need the response (`showInputBox`, `showQuickPick`)
|
||||||
|
- File operations where you need the results (`findFiles`, `readFile`)
|
||||||
|
- Extension API calls that return promises
|
||||||
|
- Information messages with buttons where you need to know which was clicked
|
||||||
|
|
||||||
|
**When to use `awaitResult: false` (default):**
|
||||||
|
- Synchronous operations
|
||||||
|
- Fire-and-forget async operations like simple information messages
|
||||||
|
- Side-effect async operations where you don't need the return value
|
||||||
|
|
||||||
|
### Promise Handling
|
||||||
|
```clojure
|
||||||
|
(require '[promesa.core :as p])
|
||||||
|
|
||||||
|
;; Users need to understand async operations
|
||||||
|
(p/let [result (vscode/window.showInputBox #js {:prompt "Enter value:"})]
|
||||||
|
(when result
|
||||||
|
(vscode/window.showInformationMessage (str "You entered: " result))))
|
||||||
|
|
||||||
|
;; Pattern for unwrapping async results in REPL (use awaitResult: true)
|
||||||
|
(p/let [files (vscode/workspace.findFiles "**/*.cljs")]
|
||||||
|
(def found-files files))
|
||||||
|
;; Now `found-files` is defined in the namespace for later use
|
||||||
|
|
||||||
|
;; Yet another example with `joyride.core/slurp` (use awaitResult: true)
|
||||||
|
(p/let [content (joyride.core/slurp "some/file/in/the/workspace.csv")]
|
||||||
|
(def content content) ; if you want to use/inspect `content` later in the session
|
||||||
|
; Do something with the content
|
||||||
|
)
|
||||||
|
```
|
||||||
|
|
||||||
|
### Extension APIs
|
||||||
|
```clojure
|
||||||
|
;; How to access other extensions safely
|
||||||
|
(when-let [ext (vscode/extensions.getExtension "ms-python.python")]
|
||||||
|
(when (.-isActive ext)
|
||||||
|
(let [python-api (.-exports ext)]
|
||||||
|
;; Use Python extension API safely
|
||||||
|
(-> python-api .-environments .-known count))))
|
||||||
|
|
||||||
|
;; Always check if extension is available first
|
||||||
|
(defn get-python-info []
|
||||||
|
(if-let [ext (vscode/extensions.getExtension "ms-python.python")]
|
||||||
|
(if (.-isActive ext)
|
||||||
|
{:available true
|
||||||
|
:env-count (-> ext .-exports .-environments .-known count)}
|
||||||
|
{:available false :reason "Extension not active"})
|
||||||
|
{:available false :reason "Extension not installed"}))
|
||||||
|
```
|
||||||
|
|
||||||
|
### Joyride Flares - WebView Creation
|
||||||
|
Joyride Flares provide a powerful way to create visual interfaces and display rich content in VS Code:
|
||||||
|
|
||||||
|
```clojure
|
||||||
|
(require '[joyride.flare :as flare])
|
||||||
|
|
||||||
|
;; Simple HTML flare
|
||||||
|
(flare/flare! {:html [:h1 "Hello World!"]
|
||||||
|
:title "My Flare"
|
||||||
|
:key "greeting"})
|
||||||
|
|
||||||
|
;; Flare with external URL
|
||||||
|
(flare/flare! {:url "https://example.com"
|
||||||
|
:title "External Site"})
|
||||||
|
|
||||||
|
;; Sidebar flare
|
||||||
|
(flare/flare! {:html [:div [:h2 "Sidebar"] [:p "Content"]]
|
||||||
|
:sidebar-panel? true})
|
||||||
|
|
||||||
|
;; Data visualization
|
||||||
|
(flare/flare! {:html [:svg {:width 200 :height 200}
|
||||||
|
[:circle {:cx 100 :cy 100 :r 50 :fill :blue}]]
|
||||||
|
:title "SVG Demo"})
|
||||||
|
|
||||||
|
;; Manage flares
|
||||||
|
(flare/ls) ; List all active flares
|
||||||
|
(flare/close! "greeting") ; Close specific flare by key
|
||||||
|
(flare/close-all!) ; Close all flares
|
||||||
|
```
|
||||||
|
|
||||||
|
**Flare Style Guidelines:**
|
||||||
|
- Use maps for `:style` attributes: `{:style {:color :red :border "1px solid #ccc"}}`
|
||||||
|
- Prefer keywords for simple CSS values: `:color :red`
|
||||||
|
- Use strings for compound CSS property values: `:border "1px solid #ccc"`
|
||||||
|
|
||||||
|
## Common User Patterns
|
||||||
|
|
||||||
|
### Script Execution Guard
|
||||||
|
```clojure
|
||||||
|
;; Essential pattern - only run when invoked as script, not when loaded in REPL
|
||||||
|
(when (= (joyride/invoked-script) joyride/*file*)
|
||||||
|
(main))
|
||||||
|
```
|
||||||
|
|
||||||
|
### Managing Disposables
|
||||||
|
```clojure
|
||||||
|
;; Always register disposables with extension context
|
||||||
|
(let [disposable (vscode/workspace.onDidOpenTextDocument handler)]
|
||||||
|
(.push (.-subscriptions (joyride/extension-context)) disposable))
|
||||||
|
```
|
||||||
|
|
||||||
|
## Editing files
|
||||||
|
|
||||||
|
Develop using the REPL. Yet, sometimes you need to edit file. And when you do, prefer structural editing tools.
|
||||||
|
|||||||
@ -1,7 +1,6 @@
|
|||||||
---
|
---
|
||||||
mode: 'agent'
|
mode: 'agent'
|
||||||
tools: ['changes', 'codebase', 'editFiles', 'findTestFiles', 'problems', 'runCommands', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'testFailure', 'usages']
|
description: 'Create Spring Boot Java Project Skeleton'
|
||||||
description: 'Create Spring Boot Java project skeleton'
|
|
||||||
---
|
---
|
||||||
|
|
||||||
# Create Spring Boot Java project prompt
|
# Create Spring Boot Java project prompt
|
||||||
@ -30,7 +29,7 @@ java -version
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
curl https://start.spring.io/starter.zip \
|
curl https://start.spring.io/starter.zip \
|
||||||
-d artifactId=demo \
|
-d artifactId=${input:projectName:demo-java} \
|
||||||
-d bootVersion=3.4.5 \
|
-d bootVersion=3.4.5 \
|
||||||
-d dependencies=lombok,configuration-processor,web,data-jpa,postgresql,data-redis,data-mongodb,validation,cache,testcontainers \
|
-d dependencies=lombok,configuration-processor,web,data-jpa,postgresql,data-redis,data-mongodb,validation,cache,testcontainers \
|
||||||
-d javaVersion=21 \
|
-d javaVersion=21 \
|
||||||
@ -45,7 +44,7 @@ curl https://start.spring.io/starter.zip \
|
|||||||
- Run following command in terminal to unzip the downloaded file
|
- Run following command in terminal to unzip the downloaded file
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
unzip starter.zip -d .
|
unzip starter.zip -d ./${input:projectName:demo-java}
|
||||||
```
|
```
|
||||||
|
|
||||||
## Remove the downloaded zip file
|
## Remove the downloaded zip file
|
||||||
@ -56,6 +55,14 @@ unzip starter.zip -d .
|
|||||||
rm -f starter.zip
|
rm -f starter.zip
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Change directory to the project root
|
||||||
|
|
||||||
|
- Run following command in terminal to change directory to the project root
|
||||||
|
|
||||||
|
```shell
|
||||||
|
cd ${input:projectName:demo-java}
|
||||||
|
```
|
||||||
|
|
||||||
## Add additional dependencies
|
## Add additional dependencies
|
||||||
|
|
||||||
- Insert `springdoc-openapi-starter-webmvc-ui` and `archunit-junit5` dependency into `pom.xml` file
|
- Insert `springdoc-openapi-starter-webmvc-ui` and `archunit-junit5` dependency into `pom.xml` file
|
||||||
|
|||||||
@ -1,7 +1,6 @@
|
|||||||
---
|
---
|
||||||
mode: 'agent'
|
mode: 'agent'
|
||||||
tools: ['changes', 'codebase', 'editFiles', 'findTestFiles', 'problems', 'runCommands', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'testFailure', 'usages']
|
description: 'Create Spring Boot Kotlin Project Skeleton'
|
||||||
description: 'Create Spring Boot Kotlin project skeleton'
|
|
||||||
---
|
---
|
||||||
|
|
||||||
# Create Spring Boot Kotlin project prompt
|
# Create Spring Boot Kotlin project prompt
|
||||||
@ -30,7 +29,7 @@ java -version
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
curl https://start.spring.io/starter.zip \
|
curl https://start.spring.io/starter.zip \
|
||||||
-d artifactId=demo \
|
-d artifactId=${input:projectName:demo-kotlin} \
|
||||||
-d bootVersion=3.4.5 \
|
-d bootVersion=3.4.5 \
|
||||||
-d dependencies=configuration-processor,webflux,data-r2dbc,postgresql,data-redis-reactive,data-mongodb-reactive,validation,cache,testcontainers \
|
-d dependencies=configuration-processor,webflux,data-r2dbc,postgresql,data-redis-reactive,data-mongodb-reactive,validation,cache,testcontainers \
|
||||||
-d javaVersion=21 \
|
-d javaVersion=21 \
|
||||||
@ -46,7 +45,7 @@ curl https://start.spring.io/starter.zip \
|
|||||||
- Run following command in terminal to unzip the downloaded file
|
- Run following command in terminal to unzip the downloaded file
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
unzip starter.zip -d .
|
unzip starter.zip -d ./${input:projectName:demo-kotlin}
|
||||||
```
|
```
|
||||||
|
|
||||||
## Remove the downloaded zip file
|
## Remove the downloaded zip file
|
||||||
@ -57,6 +56,14 @@ unzip starter.zip -d .
|
|||||||
rm -f starter.zip
|
rm -f starter.zip
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Unzip the downloaded file
|
||||||
|
|
||||||
|
- Run following command in terminal to unzip the downloaded file
|
||||||
|
|
||||||
|
```shell
|
||||||
|
unzip starter.zip -d ./${input:projectName:demo-kotlin}
|
||||||
|
```
|
||||||
|
|
||||||
## Add additional dependencies
|
## Add additional dependencies
|
||||||
|
|
||||||
- Insert `springdoc-openapi-starter-webmvc-ui` and `archunit-junit5` dependency into `build.gradle.kts` file
|
- Insert `springdoc-openapi-starter-webmvc-ui` and `archunit-junit5` dependency into `build.gradle.kts` file
|
||||||
|
|||||||
231
prompts/create-technical-spike.prompt.md
Normal file
231
prompts/create-technical-spike.prompt.md
Normal file
@ -0,0 +1,231 @@
|
|||||||
|
---
|
||||||
|
mode: 'agent'
|
||||||
|
description: 'Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.'
|
||||||
|
tools: ['runCommands', 'runTasks', 'edit', 'search', 'extensions', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'Microsoft Docs', 'search']
|
||||||
|
---
|
||||||
|
|
||||||
|
# Create Technical Spike Document
|
||||||
|
|
||||||
|
Create time-boxed technical spike documents for researching critical questions that must be answered before development can proceed. Each spike focuses on a specific technical decision with clear deliverables and timelines.
|
||||||
|
|
||||||
|
## Document Structure
|
||||||
|
|
||||||
|
Create individual files in `${input:FolderPath|docs/spikes}` directory. Name each file using the pattern: `[category]-[short-description]-spike.md` (e.g., `api-copilot-integration-spike.md`, `performance-realtime-audio-spike.md`).
|
||||||
|
|
||||||
|
```md
|
||||||
|
---
|
||||||
|
title: "${input:SpikeTitle}"
|
||||||
|
category: "${input:Category|Technical}"
|
||||||
|
status: "🔴 Not Started"
|
||||||
|
priority: "${input:Priority|High}"
|
||||||
|
timebox: "${input:Timebox|1 week}"
|
||||||
|
created: [YYYY-MM-DD]
|
||||||
|
updated: [YYYY-MM-DD]
|
||||||
|
owner: "${input:Owner}"
|
||||||
|
tags: ["technical-spike", "${input:Category|technical}", "research"]
|
||||||
|
---
|
||||||
|
|
||||||
|
# ${input:SpikeTitle}
|
||||||
|
|
||||||
|
## Summary
|
||||||
|
|
||||||
|
**Spike Objective:** [Clear, specific question or decision that needs resolution]
|
||||||
|
|
||||||
|
**Why This Matters:** [Impact on development/architecture decisions]
|
||||||
|
|
||||||
|
**Timebox:** [How much time allocated to this spike]
|
||||||
|
|
||||||
|
**Decision Deadline:** [When this must be resolved to avoid blocking development]
|
||||||
|
|
||||||
|
## Research Question(s)
|
||||||
|
|
||||||
|
**Primary Question:** [Main technical question that needs answering]
|
||||||
|
|
||||||
|
**Secondary Questions:**
|
||||||
|
|
||||||
|
- [Related question 1]
|
||||||
|
- [Related question 2]
|
||||||
|
- [Related question 3]
|
||||||
|
|
||||||
|
## Investigation Plan
|
||||||
|
|
||||||
|
### Research Tasks
|
||||||
|
|
||||||
|
- [ ] [Specific research task 1]
|
||||||
|
- [ ] [Specific research task 2]
|
||||||
|
- [ ] [Specific research task 3]
|
||||||
|
- [ ] [Create proof of concept/prototype]
|
||||||
|
- [ ] [Document findings and recommendations]
|
||||||
|
|
||||||
|
### Success Criteria
|
||||||
|
|
||||||
|
**This spike is complete when:**
|
||||||
|
|
||||||
|
- [ ] [Specific criteria 1]
|
||||||
|
- [ ] [Specific criteria 2]
|
||||||
|
- [ ] [Clear recommendation documented]
|
||||||
|
- [ ] [Proof of concept completed (if applicable)]
|
||||||
|
|
||||||
|
## Technical Context
|
||||||
|
|
||||||
|
**Related Components:** [List system components affected by this decision]
|
||||||
|
|
||||||
|
**Dependencies:** [What other spikes or decisions depend on resolving this]
|
||||||
|
|
||||||
|
**Constraints:** [Known limitations or requirements that affect the solution]
|
||||||
|
|
||||||
|
## Research Findings
|
||||||
|
|
||||||
|
### Investigation Results
|
||||||
|
|
||||||
|
[Document research findings, test results, and evidence gathered]
|
||||||
|
|
||||||
|
### Prototype/Testing Notes
|
||||||
|
|
||||||
|
[Results from any prototypes, spikes, or technical experiments]
|
||||||
|
|
||||||
|
### External Resources
|
||||||
|
|
||||||
|
- [Link to relevant documentation]
|
||||||
|
- [Link to API references]
|
||||||
|
- [Link to community discussions]
|
||||||
|
- [Link to examples/tutorials]
|
||||||
|
|
||||||
|
## Decision
|
||||||
|
|
||||||
|
### Recommendation
|
||||||
|
|
||||||
|
[Clear recommendation based on research findings]
|
||||||
|
|
||||||
|
### Rationale
|
||||||
|
|
||||||
|
[Why this approach was chosen over alternatives]
|
||||||
|
|
||||||
|
### Implementation Notes
|
||||||
|
|
||||||
|
[Key considerations for implementation]
|
||||||
|
|
||||||
|
### Follow-up Actions
|
||||||
|
|
||||||
|
- [ ] [Action item 1]
|
||||||
|
- [ ] [Action item 2]
|
||||||
|
- [ ] [Update architecture documents]
|
||||||
|
- [ ] [Create implementation tasks]
|
||||||
|
|
||||||
|
## Status History
|
||||||
|
|
||||||
|
| Date | Status | Notes |
|
||||||
|
| ------ | -------------- | -------------------------- |
|
||||||
|
| [Date] | 🔴 Not Started | Spike created and scoped |
|
||||||
|
| [Date] | 🟡 In Progress | Research commenced |
|
||||||
|
| [Date] | 🟢 Complete | [Resolution summary] |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
_Last updated: [Date] by [Name]_
|
||||||
|
```
|
||||||
|
|
||||||
|
## Categories for Technical Spikes
|
||||||
|
|
||||||
|
### API Integration
|
||||||
|
|
||||||
|
- Third-party API capabilities and limitations
|
||||||
|
- Integration patterns and authentication
|
||||||
|
- Rate limits and performance characteristics
|
||||||
|
|
||||||
|
### Architecture & Design
|
||||||
|
|
||||||
|
- System architecture decisions
|
||||||
|
- Design pattern applicability
|
||||||
|
- Component interaction models
|
||||||
|
|
||||||
|
### Performance & Scalability
|
||||||
|
|
||||||
|
- Performance requirements and constraints
|
||||||
|
- Scalability bottlenecks and solutions
|
||||||
|
- Resource utilization patterns
|
||||||
|
|
||||||
|
### Platform & Infrastructure
|
||||||
|
|
||||||
|
- Platform capabilities and limitations
|
||||||
|
- Infrastructure requirements
|
||||||
|
- Deployment and hosting considerations
|
||||||
|
|
||||||
|
### Security & Compliance
|
||||||
|
|
||||||
|
- Security requirements and implementations
|
||||||
|
- Compliance constraints
|
||||||
|
- Authentication and authorization approaches
|
||||||
|
|
||||||
|
### User Experience
|
||||||
|
|
||||||
|
- User interaction patterns
|
||||||
|
- Accessibility requirements
|
||||||
|
- Interface design decisions
|
||||||
|
|
||||||
|
## File Naming Conventions
|
||||||
|
|
||||||
|
Use descriptive, kebab-case names that indicate the category and specific unknown:
|
||||||
|
|
||||||
|
**API/Integration Examples:**
|
||||||
|
|
||||||
|
- `api-copilot-chat-integration-spike.md`
|
||||||
|
- `api-azure-speech-realtime-spike.md`
|
||||||
|
- `api-vscode-extension-capabilities-spike.md`
|
||||||
|
|
||||||
|
**Performance Examples:**
|
||||||
|
|
||||||
|
- `performance-audio-processing-latency-spike.md`
|
||||||
|
- `performance-extension-host-limitations-spike.md`
|
||||||
|
- `performance-webrtc-reliability-spike.md`
|
||||||
|
|
||||||
|
**Architecture Examples:**
|
||||||
|
|
||||||
|
- `architecture-voice-pipeline-design-spike.md`
|
||||||
|
- `architecture-state-management-spike.md`
|
||||||
|
- `architecture-error-handling-strategy-spike.md`
|
||||||
|
|
||||||
|
## Best Practices for AI Agents
|
||||||
|
|
||||||
|
1. **One Question Per Spike:** Each document focuses on a single technical decision or research question
|
||||||
|
|
||||||
|
2. **Time-Boxed Research:** Define specific time limits and deliverables for each spike
|
||||||
|
|
||||||
|
3. **Evidence-Based Decisions:** Require concrete evidence (tests, prototypes, documentation) before marking as complete
|
||||||
|
|
||||||
|
4. **Clear Recommendations:** Document specific recommendations and rationale for implementation
|
||||||
|
|
||||||
|
5. **Dependency Tracking:** Identify how spikes relate to each other and impact project decisions
|
||||||
|
|
||||||
|
6. **Outcome-Focused:** Every spike must result in an actionable decision or recommendation
|
||||||
|
|
||||||
|
## Research Strategy
|
||||||
|
|
||||||
|
### Phase 1: Information Gathering
|
||||||
|
|
||||||
|
1. **Search existing documentation** using search/fetch tools
|
||||||
|
2. **Analyze codebase** for existing patterns and constraints
|
||||||
|
3. **Research external resources** (APIs, libraries, examples)
|
||||||
|
|
||||||
|
### Phase 2: Validation & Testing
|
||||||
|
|
||||||
|
1. **Create focused prototypes** to test specific hypotheses
|
||||||
|
2. **Run targeted experiments** to validate assumptions
|
||||||
|
3. **Document test results** with supporting evidence
|
||||||
|
|
||||||
|
### Phase 3: Decision & Documentation
|
||||||
|
|
||||||
|
1. **Synthesize findings** into clear recommendations
|
||||||
|
2. **Document implementation guidance** for development team
|
||||||
|
3. **Create follow-up tasks** for implementation
|
||||||
|
|
||||||
|
## Tools Usage
|
||||||
|
|
||||||
|
- **search/searchResults:** Research existing solutions and documentation
|
||||||
|
- **fetch/githubRepo:** Analyze external APIs, libraries, and examples
|
||||||
|
- **codebase:** Understand existing system constraints and patterns
|
||||||
|
- **runTasks:** Execute prototypes and validation tests
|
||||||
|
- **editFiles:** Update research progress and findings
|
||||||
|
- **vscodeAPI:** Test VS Code extension capabilities and limitations
|
||||||
|
|
||||||
|
Focus on time-boxed research that resolves critical technical decisions and unblocks development progress.
|
||||||
93
prompts/declarative-agents.prompt.md
Normal file
93
prompts/declarative-agents.prompt.md
Normal file
@ -0,0 +1,93 @@
|
|||||||
|
---
|
||||||
|
description: Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration
|
||||||
|
---
|
||||||
|
|
||||||
|
# Microsoft 365 Declarative Agents Development Kit
|
||||||
|
|
||||||
|
I'll help you create and develop Microsoft 365 Copilot declarative agents using the latest v1.5 schema with comprehensive TypeSpec and Microsoft 365 Agents Toolkit integration. Choose from three specialized workflows:
|
||||||
|
|
||||||
|
## Workflow 1: Basic Agent Creation
|
||||||
|
**Perfect for**: New developers, simple agents, quick prototypes
|
||||||
|
|
||||||
|
I'll guide you through:
|
||||||
|
1. **Agent Planning**: Define purpose, target users, and core capabilities
|
||||||
|
2. **Capability Selection**: Choose from 11 available capabilities (WebSearch, OneDriveAndSharePoint, GraphConnectors, etc.)
|
||||||
|
3. **Basic Schema Creation**: Generate compliant JSON manifest with proper constraints
|
||||||
|
4. **TypeSpec Alternative**: Create modern type-safe definitions that compile to JSON
|
||||||
|
5. **Testing Setup**: Configure Agents Playground for local testing
|
||||||
|
6. **Toolkit Integration**: Leverage Microsoft 365 Agents Toolkit for enhanced development
|
||||||
|
|
||||||
|
## Workflow 2: Advanced Enterprise Agent Design
|
||||||
|
**Perfect for**: Complex enterprise scenarios, production deployment, advanced features
|
||||||
|
|
||||||
|
I'll help you architect:
|
||||||
|
1. **Enterprise Requirements Analysis**: Multi-tenant considerations, compliance, security
|
||||||
|
2. **Advanced Capability Configuration**: Complex capability combinations and interactions
|
||||||
|
3. **Behavior Override Implementation**: Custom response patterns and specialized behaviors
|
||||||
|
4. **Localization Strategy**: Multi-language support with proper resource management
|
||||||
|
5. **Conversation Starters**: Strategic conversation entry points for user engagement
|
||||||
|
6. **Production Deployment**: Environment management, versioning, and lifecycle planning
|
||||||
|
7. **Monitoring & Analytics**: Implementation of tracking and performance optimization
|
||||||
|
|
||||||
|
## Workflow 3: Validation & Optimization
|
||||||
|
**Perfect for**: Existing agents, troubleshooting, performance optimization
|
||||||
|
|
||||||
|
I'll perform:
|
||||||
|
1. **Schema Compliance Validation**: Full v1.5 specification adherence checking
|
||||||
|
2. **Character Limit Optimization**: Name (100), description (1000), instructions (8000)
|
||||||
|
3. **Capability Audit**: Verify proper capability configuration and usage
|
||||||
|
4. **TypeSpec Migration**: Convert existing JSON to modern TypeSpec definitions
|
||||||
|
5. **Testing Protocol**: Comprehensive validation using Agents Playground
|
||||||
|
6. **Performance Analysis**: Identify bottlenecks and optimization opportunities
|
||||||
|
7. **Best Practices Review**: Alignment with Microsoft guidelines and recommendations
|
||||||
|
|
||||||
|
## Core Features Across All Workflows
|
||||||
|
|
||||||
|
### Microsoft 365 Agents Toolkit Integration
|
||||||
|
- **VS Code Extension**: Full integration with `teamsdevapp.ms-teams-vscode-extension`
|
||||||
|
- **TypeSpec Development**: Modern type-safe agent definitions
|
||||||
|
- **Local Debugging**: Agents Playground integration for testing
|
||||||
|
- **Environment Management**: Development, staging, production configurations
|
||||||
|
- **Lifecycle Management**: Creation, testing, deployment, monitoring
|
||||||
|
|
||||||
|
### TypeSpec Examples
|
||||||
|
```typespec
|
||||||
|
// Modern declarative agent definition
|
||||||
|
model MyAgent {
|
||||||
|
name: string;
|
||||||
|
description: string;
|
||||||
|
instructions: string;
|
||||||
|
capabilities: AgentCapability[];
|
||||||
|
conversation_starters?: ConversationStarter[];
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
### JSON Schema v1.5 Validation
|
||||||
|
- Full compliance with latest Microsoft specification
|
||||||
|
- Character limit enforcement (name: 100, description: 1000, instructions: 8000)
|
||||||
|
- Array constraint validation (conversation_starters: max 4, capabilities: max 5)
|
||||||
|
- Required field validation and type checking
|
||||||
|
|
||||||
|
### Available Capabilities (Choose up to 5)
|
||||||
|
1. **WebSearch**: Internet search functionality
|
||||||
|
2. **OneDriveAndSharePoint**: File and content access
|
||||||
|
3. **GraphConnectors**: Enterprise data integration
|
||||||
|
4. **MicrosoftGraph**: Microsoft 365 service integration
|
||||||
|
5. **TeamsAndOutlook**: Communication platform access
|
||||||
|
6. **PowerPlatform**: Power Apps and Power Automate integration
|
||||||
|
7. **BusinessDataProcessing**: Enterprise data analysis
|
||||||
|
8. **WordAndExcel**: Document and spreadsheet manipulation
|
||||||
|
9. **CopilotForMicrosoft365**: Advanced Copilot features
|
||||||
|
10. **EnterpriseApplications**: Third-party system integration
|
||||||
|
11. **CustomConnectors**: Custom API and service integration
|
||||||
|
|
||||||
|
### Environment Variables Support
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"name": "${AGENT_NAME}",
|
||||||
|
"description": "${AGENT_DESCRIPTION}",
|
||||||
|
"instructions": "${AGENT_INSTRUCTIONS}"
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
**Which workflow would you like to start with?** Share your requirements and I'll provide specialized guidance for your Microsoft 365 Copilot declarative agent development with full TypeSpec and Microsoft 365 Agents Toolkit support.
|
||||||
98
prompts/remember.prompt.md
Normal file
98
prompts/remember.prompt.md
Normal file
@ -0,0 +1,98 @@
|
|||||||
|
---
|
||||||
|
description: 'Contemplates repeated mistakes and success patterns, and transforms lessons learned into domain-organized Copilot instructions. Automatically discovers existing memory domains, intelligently categorizes new learnings, and creates domain-specific instruction files in VS Code User Data Directory. You can make the categorization/domain designation specific by using `>domain-name` as the first thing in your request. Like so: `/remember >domain-name lesson content here`'
|
||||||
|
---
|
||||||
|
|
||||||
|
# Memory Keeper
|
||||||
|
|
||||||
|
You are an expert keeper of **domain-organized Memory Instructions** that persist across all VS Code projects. You maintain a self-organizing knowledge base that automatically categorizes learnings by domain and creates new memory files as needed in the `vscode-userdata:/User/prompts/` folder.
|
||||||
|
|
||||||
|
## Your Mission
|
||||||
|
|
||||||
|
Transform debugging sessions, workflow discoveries, frequently repeated mistakes, and hard-won lessons into **domain-specific, reusable knowledge**, that helps the agent to effectively find the best patterns and avoid common mistakes. Your intelligent categorization system automatically:
|
||||||
|
|
||||||
|
- **Discovers existing memory domains** via glob patterns to find `vscode-userdata:/User/prompts/*-memory.instructions.md` files
|
||||||
|
- **Matches learnings to domains** or creates new domain files when needed
|
||||||
|
- **Organizes knowledge contextually** so future AI assistants find relevant guidance exactly when needed
|
||||||
|
- **Builds institutional memory** that prevents repeating mistakes across all projects
|
||||||
|
|
||||||
|
The result: a **self-organizing, domain-driven knowledge base** that grows smarter with every lesson learned.
|
||||||
|
|
||||||
|
## Domain Syntax
|
||||||
|
|
||||||
|
Users can optionally specify target domains using:
|
||||||
|
- `/remember >domain-name lesson content here` - explicitly targets a domain
|
||||||
|
- `/remember lesson content here` - agent determines appropriate domain(s)
|
||||||
|
|
||||||
|
Examples:
|
||||||
|
- `/remember >shell-scripting now we've forgotten about using fish syntax too many times`
|
||||||
|
- `/remember >clojure prefer passing maps over parameter lists`
|
||||||
|
- `/remember always check terminal output encoding when seeing weird characters`
|
||||||
|
|
||||||
|
## Memory File Structure
|
||||||
|
|
||||||
|
### Description Frontmatter
|
||||||
|
Keep domain file descriptions general, focusing on the domain responsibility rather than implementation specifics.
|
||||||
|
|
||||||
|
### ApplyTo Frontmatter
|
||||||
|
Target specific file patterns and locations relevant to the domain using glob patterns. Keep the glob patterns few and broad, targeting directories if the domain is not specific to a language, or file extensions if the domain is language-specific.
|
||||||
|
|
||||||
|
### Main Headline
|
||||||
|
Use level 1 heading format: `# <Domain Name> Memory`
|
||||||
|
|
||||||
|
### Tag Line
|
||||||
|
Follow the main headline with a succinct tagline that captures the core patterns and value of that domain's memory file.
|
||||||
|
|
||||||
|
### Learnings
|
||||||
|
|
||||||
|
Each distinct lesson has its own level 2 headline
|
||||||
|
|
||||||
|
## Process
|
||||||
|
|
||||||
|
1. **Parse domain syntax** - Check if user specified `>domain-name` to target specific domain
|
||||||
|
2. **Glob and Read** existing `vscode-userdata:/User/prompts/memory.instructions.md` and `vscode-userdata:/User/prompts/*-memory.instructions.md` files to understand current domain structure
|
||||||
|
3. **Analyze** the specific lesson learned from user input
|
||||||
|
4. **Categorize** the learning:
|
||||||
|
- New gotcha/common mistake
|
||||||
|
- Enhancement to existing section
|
||||||
|
- New best practice
|
||||||
|
- Process improvement
|
||||||
|
5. **Determine target domain(s)**:
|
||||||
|
- If user specified `>domain-name`, request human input if it seems to be a typo
|
||||||
|
- Otherwise, intelligently match learning to a domain, using existing domain files as a guide while recognizing there may be coverage gaps.
|
||||||
|
- For universal learnings, use `vscode-userdata:/User/prompts/memory.instructions.md`
|
||||||
|
- If no good domain match exists, create new domain-specific file like `vscode-userdata:/User/prompts/{domain}-memory.instructions.md`
|
||||||
|
- When uncertain about domain classification, request human input
|
||||||
|
6. **Update or create files**:
|
||||||
|
- Update existing domain files with new learnings
|
||||||
|
- Create new domain files following [Memory File Structure](#memory-file-structure)
|
||||||
|
- Update `applyTo` frontmatter if needed
|
||||||
|
7. **Write** succinct, clear, and actionable instructions:
|
||||||
|
- **Extract general (within the domain) patterns** from specific instances
|
||||||
|
- Use positive reinforcement focusing on correct patterns
|
||||||
|
- Brief explanations of WHY, when helpful
|
||||||
|
- Capture:
|
||||||
|
- Coding style, preferences, and workflow
|
||||||
|
- Critical implementation paths
|
||||||
|
- Project-specific patterns
|
||||||
|
- Tool usage patterns
|
||||||
|
- Reusable problem-solving approaches
|
||||||
|
|
||||||
|
## Quality Guidelines
|
||||||
|
|
||||||
|
- **Generalize beyond specifics** - Extract reusable patterns rather than task-specific details
|
||||||
|
- Be specific and concrete (avoid vague advice)
|
||||||
|
- Include code examples when relevant
|
||||||
|
- Focus on common, recurring issues
|
||||||
|
- Keep instructions scannable and actionable
|
||||||
|
- Clean up redundancy
|
||||||
|
- Instructions focus on what to do, not what to avoid
|
||||||
|
|
||||||
|
## Update Triggers
|
||||||
|
|
||||||
|
Common scenarios that warrant memory updates:
|
||||||
|
- Repeatedly forgetting the same shortcuts or commands
|
||||||
|
- Discovering effective workflows
|
||||||
|
- Learning domain-specific best practices
|
||||||
|
- Finding reusable problem-solving approaches
|
||||||
|
- Coding style decisions and rationale
|
||||||
|
- Cross-project patterns that work well
|
||||||
158
update-readme.js
158
update-readme.js
@ -2,6 +2,7 @@
|
|||||||
|
|
||||||
const fs = require("fs");
|
const fs = require("fs");
|
||||||
const path = require("path");
|
const path = require("path");
|
||||||
|
const { parseCollectionYaml } = require("./yaml-parser");
|
||||||
|
|
||||||
// Template sections for the README
|
// Template sections for the README
|
||||||
const TEMPLATES = {
|
const TEMPLATES = {
|
||||||
@ -49,9 +50,28 @@ Custom chat modes define specific behaviors and tools for GitHub Copilot Chat, e
|
|||||||
- Import the chat mode configuration into your VS Code settings
|
- Import the chat mode configuration into your VS Code settings
|
||||||
- Access the installed chat modes through the VS Code Chat interface
|
- Access the installed chat modes through the VS Code Chat interface
|
||||||
- Select the desired chat mode from the available options in VS Code Chat`,
|
- Select the desired chat mode from the available options in VS Code Chat`,
|
||||||
|
|
||||||
|
collectionsSection: `## 📦 Collections
|
||||||
|
|
||||||
|
Curated collections of related prompts, instructions, and chat modes organized around specific themes, workflows, or use cases.`,
|
||||||
|
|
||||||
|
collectionsUsage: `### How to Use Collections
|
||||||
|
|
||||||
|
**Browse Collections:**
|
||||||
|
- Explore themed collections that group related customizations
|
||||||
|
- Each collection includes prompts, instructions, and chat modes for specific workflows
|
||||||
|
- Collections make it easy to adopt comprehensive toolkits for particular scenarios
|
||||||
|
|
||||||
|
**Install Items:**
|
||||||
|
- Click install buttons for individual items within collections
|
||||||
|
- Or browse to the individual files to copy content manually
|
||||||
|
- Collections help you discover related customizations you might have missed`,
|
||||||
};
|
};
|
||||||
|
|
||||||
// Add error handling utility
|
// Add error handling utility
|
||||||
|
/**
|
||||||
|
* Safe file operation wrapper
|
||||||
|
*/
|
||||||
function safeFileOperation(operation, filePath, defaultValue = null) {
|
function safeFileOperation(operation, filePath, defaultValue = null) {
|
||||||
try {
|
try {
|
||||||
return operation();
|
return operation();
|
||||||
@ -409,6 +429,110 @@ function generateChatModesSection(chatmodesDir) {
|
|||||||
return `${TEMPLATES.chatmodesSection}\n${TEMPLATES.chatmodesUsage}\n\n${chatmodesContent}`;
|
return `${TEMPLATES.chatmodesSection}\n${TEMPLATES.chatmodesUsage}\n\n${chatmodesContent}`;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
/**
|
||||||
|
* Generate the collections section with a table of all collections
|
||||||
|
*/
|
||||||
|
function generateCollectionsSection(collectionsDir) {
|
||||||
|
// Check if collections directory exists, create it if it doesn't
|
||||||
|
if (!fs.existsSync(collectionsDir)) {
|
||||||
|
console.log("Collections directory does not exist, creating it...");
|
||||||
|
fs.mkdirSync(collectionsDir, { recursive: true });
|
||||||
|
}
|
||||||
|
|
||||||
|
// Get all collection files
|
||||||
|
const collectionFiles = fs
|
||||||
|
.readdirSync(collectionsDir)
|
||||||
|
.filter((file) => file.endsWith(".collection.yml"))
|
||||||
|
.sort();
|
||||||
|
|
||||||
|
console.log(`Found ${collectionFiles.length} collection files`);
|
||||||
|
|
||||||
|
// If no collections, return empty string
|
||||||
|
if (collectionFiles.length === 0) {
|
||||||
|
return "";
|
||||||
|
}
|
||||||
|
|
||||||
|
// Create table header
|
||||||
|
let collectionsContent =
|
||||||
|
"| Name | Description | Items | Tags |\n| ---- | ----------- | ----- | ---- |\n";
|
||||||
|
|
||||||
|
// Generate table rows for each collection file
|
||||||
|
for (const file of collectionFiles) {
|
||||||
|
const filePath = path.join(collectionsDir, file);
|
||||||
|
const collection = parseCollectionYaml(filePath);
|
||||||
|
|
||||||
|
if (!collection) {
|
||||||
|
console.warn(`Failed to parse collection: ${file}`);
|
||||||
|
continue;
|
||||||
|
}
|
||||||
|
|
||||||
|
const collectionId = collection.id || path.basename(file, ".collection.yml");
|
||||||
|
const name = collection.name || collectionId;
|
||||||
|
const description = collection.description || "No description";
|
||||||
|
const itemCount = collection.items ? collection.items.length : 0;
|
||||||
|
const tags = collection.tags ? collection.tags.join(", ") : "";
|
||||||
|
|
||||||
|
const link = `collections/${collectionId}.md`;
|
||||||
|
|
||||||
|
collectionsContent += `| [${name}](${link}) | ${description} | ${itemCount} items | ${tags} |\n`;
|
||||||
|
}
|
||||||
|
|
||||||
|
return `${TEMPLATES.collectionsSection}\n${TEMPLATES.collectionsUsage}\n\n${collectionsContent}`;
|
||||||
|
}
|
||||||
|
|
||||||
|
/**
|
||||||
|
* Generate individual collection README file
|
||||||
|
*/
|
||||||
|
function generateCollectionReadme(collection, collectionId) {
|
||||||
|
if (!collection || !collection.items) {
|
||||||
|
return `# ${collectionId}\n\nCollection not found or invalid.`;
|
||||||
|
}
|
||||||
|
|
||||||
|
const name = collection.name || collectionId;
|
||||||
|
const description = collection.description || "No description provided.";
|
||||||
|
const tags = collection.tags ? collection.tags.join(", ") : "None";
|
||||||
|
|
||||||
|
let content = `# ${name}\n\n${description}\n\n`;
|
||||||
|
|
||||||
|
if (collection.tags && collection.tags.length > 0) {
|
||||||
|
content += `**Tags:** ${tags}\n\n`;
|
||||||
|
}
|
||||||
|
|
||||||
|
content += `## Items in this Collection\n\n`;
|
||||||
|
content += `| Title | Type | Description |\n| ----- | ---- | ----------- |\n`;
|
||||||
|
|
||||||
|
// Sort items based on display.ordering setting
|
||||||
|
const items = [...collection.items];
|
||||||
|
if (collection.display?.ordering === "alpha") {
|
||||||
|
items.sort((a, b) => {
|
||||||
|
const titleA = extractTitle(path.join(__dirname, a.path));
|
||||||
|
const titleB = extractTitle(path.join(__dirname, b.path));
|
||||||
|
return titleA.localeCompare(titleB);
|
||||||
|
});
|
||||||
|
}
|
||||||
|
|
||||||
|
for (const item of items) {
|
||||||
|
const filePath = path.join(__dirname, item.path);
|
||||||
|
const title = extractTitle(filePath);
|
||||||
|
const description = extractDescription(filePath) || "No description";
|
||||||
|
const typeDisplay = item.kind === "chat-mode" ? "Chat Mode" :
|
||||||
|
item.kind === "instruction" ? "Instruction" : "Prompt";
|
||||||
|
const link = `../${item.path}`;
|
||||||
|
|
||||||
|
// Create install badges for each item
|
||||||
|
const badges = makeBadges(item.path, item.kind === "instruction" ? "instructions" :
|
||||||
|
item.kind === "chat-mode" ? "mode" : "prompt");
|
||||||
|
|
||||||
|
content += `| [${title}](${link})<br />${badges} | ${typeDisplay} | ${description} |\n`;
|
||||||
|
}
|
||||||
|
|
||||||
|
if (collection.display?.show_badge) {
|
||||||
|
content += `\n---\n*This collection includes ${items.length} curated items for ${name.toLowerCase()}.*`;
|
||||||
|
}
|
||||||
|
|
||||||
|
return content;
|
||||||
|
}
|
||||||
|
|
||||||
// Utility: write file only if content changed
|
// Utility: write file only if content changed
|
||||||
function writeFileIfChanged(filePath, content) {
|
function writeFileIfChanged(filePath, content) {
|
||||||
const exists = fs.existsSync(filePath);
|
const exists = fs.existsSync(filePath);
|
||||||
@ -441,11 +565,13 @@ try {
|
|||||||
const instructionsDir = path.join(__dirname, "instructions");
|
const instructionsDir = path.join(__dirname, "instructions");
|
||||||
const promptsDir = path.join(__dirname, "prompts");
|
const promptsDir = path.join(__dirname, "prompts");
|
||||||
const chatmodesDir = path.join(__dirname, "chatmodes");
|
const chatmodesDir = path.join(__dirname, "chatmodes");
|
||||||
|
const collectionsDir = path.join(__dirname, "collections");
|
||||||
|
|
||||||
// Compose headers for standalone files by converting section headers to H1
|
// Compose headers for standalone files by converting section headers to H1
|
||||||
const instructionsHeader = TEMPLATES.instructionsSection.replace(/^##\s/m, "# ");
|
const instructionsHeader = TEMPLATES.instructionsSection.replace(/^##\s/m, "# ");
|
||||||
const promptsHeader = TEMPLATES.promptsSection.replace(/^##\s/m, "# ");
|
const promptsHeader = TEMPLATES.promptsSection.replace(/^##\s/m, "# ");
|
||||||
const chatmodesHeader = TEMPLATES.chatmodesSection.replace(/^##\s/m, "# ");
|
const chatmodesHeader = TEMPLATES.chatmodesSection.replace(/^##\s/m, "# ");
|
||||||
|
const collectionsHeader = TEMPLATES.collectionsSection.replace(/^##\s/m, "# ");
|
||||||
|
|
||||||
const instructionsReadme = buildCategoryReadme(
|
const instructionsReadme = buildCategoryReadme(
|
||||||
generateInstructionsSection,
|
generateInstructionsSection,
|
||||||
@ -465,11 +591,41 @@ try {
|
|||||||
chatmodesHeader,
|
chatmodesHeader,
|
||||||
TEMPLATES.chatmodesUsage
|
TEMPLATES.chatmodesUsage
|
||||||
);
|
);
|
||||||
|
|
||||||
|
// Generate collections README
|
||||||
|
const collectionsReadme = buildCategoryReadme(
|
||||||
|
generateCollectionsSection,
|
||||||
|
collectionsDir,
|
||||||
|
collectionsHeader,
|
||||||
|
TEMPLATES.collectionsUsage
|
||||||
|
);
|
||||||
|
|
||||||
// Write outputs
|
// Write category outputs
|
||||||
writeFileIfChanged(path.join(__dirname, "README.instructions.md"), instructionsReadme);
|
writeFileIfChanged(path.join(__dirname, "README.instructions.md"), instructionsReadme);
|
||||||
writeFileIfChanged(path.join(__dirname, "README.prompts.md"), promptsReadme);
|
writeFileIfChanged(path.join(__dirname, "README.prompts.md"), promptsReadme);
|
||||||
writeFileIfChanged(path.join(__dirname, "README.chatmodes.md"), chatmodesReadme);
|
writeFileIfChanged(path.join(__dirname, "README.chatmodes.md"), chatmodesReadme);
|
||||||
|
writeFileIfChanged(path.join(__dirname, "README.collections.md"), collectionsReadme);
|
||||||
|
|
||||||
|
// Generate individual collection README files
|
||||||
|
if (fs.existsSync(collectionsDir)) {
|
||||||
|
console.log("Generating individual collection README files...");
|
||||||
|
|
||||||
|
const collectionFiles = fs
|
||||||
|
.readdirSync(collectionsDir)
|
||||||
|
.filter((file) => file.endsWith(".collection.yml"));
|
||||||
|
|
||||||
|
for (const file of collectionFiles) {
|
||||||
|
const filePath = path.join(collectionsDir, file);
|
||||||
|
const collection = parseCollectionYaml(filePath);
|
||||||
|
|
||||||
|
if (collection) {
|
||||||
|
const collectionId = collection.id || path.basename(file, ".collection.yml");
|
||||||
|
const readmeContent = generateCollectionReadme(collection, collectionId);
|
||||||
|
const readmeFile = path.join(collectionsDir, `${collectionId}.md`);
|
||||||
|
writeFileIfChanged(readmeFile, readmeContent);
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
} catch (error) {
|
} catch (error) {
|
||||||
console.error(`Error generating category README files: ${error.message}`);
|
console.error(`Error generating category README files: ${error.message}`);
|
||||||
process.exit(1);
|
process.exit(1);
|
||||||
|
|||||||
262
validate-collections.js
Executable file
262
validate-collections.js
Executable file
@ -0,0 +1,262 @@
|
|||||||
|
#!/usr/bin/env node
|
||||||
|
|
||||||
|
const fs = require("fs");
|
||||||
|
const path = require("path");
|
||||||
|
const { parseCollectionYaml } = require("./yaml-parser");
|
||||||
|
|
||||||
|
// Maximum number of items allowed in a collection
|
||||||
|
const MAX_COLLECTION_ITEMS = 50;
|
||||||
|
function safeFileOperation(operation, filePath, defaultValue = null) {
|
||||||
|
try {
|
||||||
|
return operation();
|
||||||
|
} catch (error) {
|
||||||
|
console.error(`Error processing file ${filePath}: ${error.message}`);
|
||||||
|
return defaultValue;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
// Validation functions
|
||||||
|
function validateCollectionId(id) {
|
||||||
|
if (!id || typeof id !== "string") {
|
||||||
|
return "ID is required and must be a string";
|
||||||
|
}
|
||||||
|
if (!/^[a-z0-9-]+$/.test(id)) {
|
||||||
|
return "ID must contain only lowercase letters, numbers, and hyphens";
|
||||||
|
}
|
||||||
|
if (id.length < 1 || id.length > 50) {
|
||||||
|
return "ID must be between 1 and 50 characters";
|
||||||
|
}
|
||||||
|
return null;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateCollectionName(name) {
|
||||||
|
if (!name || typeof name !== "string") {
|
||||||
|
return "Name is required and must be a string";
|
||||||
|
}
|
||||||
|
if (name.length < 1 || name.length > 100) {
|
||||||
|
return "Name must be between 1 and 100 characters";
|
||||||
|
}
|
||||||
|
return null;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateCollectionDescription(description) {
|
||||||
|
if (!description || typeof description !== "string") {
|
||||||
|
return "Description is required and must be a string";
|
||||||
|
}
|
||||||
|
if (description.length < 1 || description.length > 500) {
|
||||||
|
return "Description must be between 1 and 500 characters";
|
||||||
|
}
|
||||||
|
return null;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateCollectionTags(tags) {
|
||||||
|
if (tags && !Array.isArray(tags)) {
|
||||||
|
return "Tags must be an array";
|
||||||
|
}
|
||||||
|
if (tags && tags.length > 10) {
|
||||||
|
return "Maximum 10 tags allowed";
|
||||||
|
}
|
||||||
|
if (tags) {
|
||||||
|
for (const tag of tags) {
|
||||||
|
if (typeof tag !== "string") {
|
||||||
|
return "All tags must be strings";
|
||||||
|
}
|
||||||
|
if (!/^[a-z0-9-]+$/.test(tag)) {
|
||||||
|
return `Tag "${tag}" must contain only lowercase letters, numbers, and hyphens`;
|
||||||
|
}
|
||||||
|
if (tag.length < 1 || tag.length > 30) {
|
||||||
|
return `Tag "${tag}" must be between 1 and 30 characters`;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
return null;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateCollectionItems(items) {
|
||||||
|
if (!items || !Array.isArray(items)) {
|
||||||
|
return "Items is required and must be an array";
|
||||||
|
}
|
||||||
|
if (items.length < 1) {
|
||||||
|
return "At least one item is required";
|
||||||
|
}
|
||||||
|
if (items.length > MAX_COLLECTION_ITEMS) {
|
||||||
|
return `Maximum ${MAX_COLLECTION_ITEMS} items allowed`;
|
||||||
|
}
|
||||||
|
|
||||||
|
for (let i = 0; i < items.length; i++) {
|
||||||
|
const item = items[i];
|
||||||
|
if (!item || typeof item !== "object") {
|
||||||
|
return `Item ${i + 1} must be an object`;
|
||||||
|
}
|
||||||
|
if (!item.path || typeof item.path !== "string") {
|
||||||
|
return `Item ${i + 1} must have a path string`;
|
||||||
|
}
|
||||||
|
if (!item.kind || typeof item.kind !== "string") {
|
||||||
|
return `Item ${i + 1} must have a kind string`;
|
||||||
|
}
|
||||||
|
if (!["prompt", "instruction", "chat-mode"].includes(item.kind)) {
|
||||||
|
return `Item ${i + 1} kind must be one of: prompt, instruction, chat-mode`;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Validate file path exists
|
||||||
|
const filePath = path.join(__dirname, item.path);
|
||||||
|
if (!fs.existsSync(filePath)) {
|
||||||
|
return `Item ${i + 1} file does not exist: ${item.path}`;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Validate path pattern matches kind
|
||||||
|
if (item.kind === "prompt" && !item.path.endsWith(".prompt.md")) {
|
||||||
|
return `Item ${i + 1} kind is "prompt" but path doesn't end with .prompt.md`;
|
||||||
|
}
|
||||||
|
if (item.kind === "instruction" && !item.path.endsWith(".instructions.md")) {
|
||||||
|
return `Item ${i + 1} kind is "instruction" but path doesn't end with .instructions.md`;
|
||||||
|
}
|
||||||
|
if (item.kind === "chat-mode" && !item.path.endsWith(".chatmode.md")) {
|
||||||
|
return `Item ${i + 1} kind is "chat-mode" but path doesn't end with .chatmode.md`;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
return null;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateCollectionDisplay(display) {
|
||||||
|
if (display && typeof display !== "object") {
|
||||||
|
return "Display must be an object";
|
||||||
|
}
|
||||||
|
if (display) {
|
||||||
|
// Normalize ordering and show_badge in case the YAML parser left inline comments
|
||||||
|
const normalize = (val) => {
|
||||||
|
if (typeof val !== 'string') return val;
|
||||||
|
// Strip any inline comment starting with '#'
|
||||||
|
const hashIndex = val.indexOf('#');
|
||||||
|
if (hashIndex !== -1) {
|
||||||
|
val = val.substring(0, hashIndex).trim();
|
||||||
|
}
|
||||||
|
// Also strip surrounding quotes if present
|
||||||
|
if ((val.startsWith("\"") && val.endsWith("\"")) || (val.startsWith("'") && val.endsWith("'"))) {
|
||||||
|
val = val.substring(1, val.length - 1);
|
||||||
|
}
|
||||||
|
return val.trim();
|
||||||
|
};
|
||||||
|
|
||||||
|
if (display.ordering) {
|
||||||
|
const normalizedOrdering = normalize(display.ordering);
|
||||||
|
if (!["manual", "alpha"].includes(normalizedOrdering)) {
|
||||||
|
return "Display ordering must be 'manual' or 'alpha'";
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
if (display.show_badge !== undefined) {
|
||||||
|
const raw = display.show_badge;
|
||||||
|
const normalizedBadge = normalize(raw);
|
||||||
|
// Accept boolean or string boolean values
|
||||||
|
if (typeof normalizedBadge === 'string') {
|
||||||
|
if (!['true', 'false'].includes(normalizedBadge.toLowerCase())) {
|
||||||
|
return "Display show_badge must be boolean";
|
||||||
|
}
|
||||||
|
} else if (typeof normalizedBadge !== 'boolean') {
|
||||||
|
return "Display show_badge must be boolean";
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
return null;
|
||||||
|
}
|
||||||
|
|
||||||
|
function validateCollectionManifest(collection, filePath) {
|
||||||
|
const errors = [];
|
||||||
|
|
||||||
|
const idError = validateCollectionId(collection.id);
|
||||||
|
if (idError) errors.push(`ID: ${idError}`);
|
||||||
|
|
||||||
|
const nameError = validateCollectionName(collection.name);
|
||||||
|
if (nameError) errors.push(`Name: ${nameError}`);
|
||||||
|
|
||||||
|
const descError = validateCollectionDescription(collection.description);
|
||||||
|
if (descError) errors.push(`Description: ${descError}`);
|
||||||
|
|
||||||
|
const tagsError = validateCollectionTags(collection.tags);
|
||||||
|
if (tagsError) errors.push(`Tags: ${tagsError}`);
|
||||||
|
|
||||||
|
const itemsError = validateCollectionItems(collection.items);
|
||||||
|
if (itemsError) errors.push(`Items: ${itemsError}`);
|
||||||
|
|
||||||
|
const displayError = validateCollectionDisplay(collection.display);
|
||||||
|
if (displayError) errors.push(`Display: ${displayError}`);
|
||||||
|
|
||||||
|
return errors;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Main validation function
|
||||||
|
function validateCollections() {
|
||||||
|
const collectionsDir = path.join(__dirname, "collections");
|
||||||
|
|
||||||
|
if (!fs.existsSync(collectionsDir)) {
|
||||||
|
console.log("No collections directory found - validation skipped");
|
||||||
|
return true;
|
||||||
|
}
|
||||||
|
|
||||||
|
const collectionFiles = fs
|
||||||
|
.readdirSync(collectionsDir)
|
||||||
|
.filter((file) => file.endsWith(".collection.yml"));
|
||||||
|
|
||||||
|
if (collectionFiles.length === 0) {
|
||||||
|
console.log("No collection files found - validation skipped");
|
||||||
|
return true;
|
||||||
|
}
|
||||||
|
|
||||||
|
console.log(`Validating ${collectionFiles.length} collection files...`);
|
||||||
|
|
||||||
|
let hasErrors = false;
|
||||||
|
const usedIds = new Set();
|
||||||
|
|
||||||
|
for (const file of collectionFiles) {
|
||||||
|
const filePath = path.join(collectionsDir, file);
|
||||||
|
console.log(`\nValidating ${file}...`);
|
||||||
|
|
||||||
|
const collection = parseCollectionYaml(filePath);
|
||||||
|
if (!collection) {
|
||||||
|
console.error(`❌ Failed to parse ${file}`);
|
||||||
|
hasErrors = true;
|
||||||
|
continue;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Validate the collection structure
|
||||||
|
const errors = validateCollectionManifest(collection, filePath);
|
||||||
|
|
||||||
|
if (errors.length > 0) {
|
||||||
|
console.error(`❌ Validation errors in ${file}:`);
|
||||||
|
errors.forEach(error => console.error(` - ${error}`));
|
||||||
|
hasErrors = true;
|
||||||
|
} else {
|
||||||
|
console.log(`✅ ${file} is valid`);
|
||||||
|
}
|
||||||
|
|
||||||
|
// Check for duplicate IDs
|
||||||
|
if (collection.id) {
|
||||||
|
if (usedIds.has(collection.id)) {
|
||||||
|
console.error(`❌ Duplicate collection ID "${collection.id}" found in ${file}`);
|
||||||
|
hasErrors = true;
|
||||||
|
} else {
|
||||||
|
usedIds.add(collection.id);
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
if (!hasErrors) {
|
||||||
|
console.log(`\n✅ All ${collectionFiles.length} collections are valid`);
|
||||||
|
}
|
||||||
|
|
||||||
|
return !hasErrors;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Run validation
|
||||||
|
try {
|
||||||
|
const isValid = validateCollections();
|
||||||
|
if (!isValid) {
|
||||||
|
console.error("\n❌ Collection validation failed");
|
||||||
|
process.exit(1);
|
||||||
|
}
|
||||||
|
console.log("\n🎉 Collection validation passed");
|
||||||
|
} catch (error) {
|
||||||
|
console.error(`Error during validation: ${error.message}`);
|
||||||
|
process.exit(1);
|
||||||
|
}
|
||||||
113
yaml-parser.js
Normal file
113
yaml-parser.js
Normal file
@ -0,0 +1,113 @@
|
|||||||
|
// Simple YAML parser for collection files
|
||||||
|
const fs = require("fs");
|
||||||
|
|
||||||
|
function safeFileOperation(operation, filePath, defaultValue = null) {
|
||||||
|
try {
|
||||||
|
return operation();
|
||||||
|
} catch (error) {
|
||||||
|
console.error(`Error processing file ${filePath}: ${error.message}`);
|
||||||
|
return defaultValue;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
function parseCollectionYaml(filePath) {
|
||||||
|
return safeFileOperation(
|
||||||
|
() => {
|
||||||
|
const content = fs.readFileSync(filePath, "utf8");
|
||||||
|
const lines = content.split("\n");
|
||||||
|
const result = {};
|
||||||
|
let currentKey = null;
|
||||||
|
let currentArray = null;
|
||||||
|
let currentObject = null;
|
||||||
|
|
||||||
|
for (let i = 0; i < lines.length; i++) {
|
||||||
|
const line = lines[i];
|
||||||
|
const trimmed = line.trim();
|
||||||
|
|
||||||
|
if (!trimmed || trimmed.startsWith("#")) continue;
|
||||||
|
|
||||||
|
const leadingSpaces = line.length - line.trimLeft().length;
|
||||||
|
|
||||||
|
// Handle array items starting with -
|
||||||
|
if (trimmed.startsWith("- ")) {
|
||||||
|
if (currentKey === "items") {
|
||||||
|
if (!currentArray) {
|
||||||
|
currentArray = [];
|
||||||
|
result[currentKey] = currentArray;
|
||||||
|
}
|
||||||
|
|
||||||
|
// Parse item object
|
||||||
|
const item = {};
|
||||||
|
currentArray.push(item);
|
||||||
|
currentObject = item;
|
||||||
|
|
||||||
|
// Handle inline properties on same line as -
|
||||||
|
const restOfLine = trimmed.substring(2).trim();
|
||||||
|
if (restOfLine) {
|
||||||
|
const colonIndex = restOfLine.indexOf(":");
|
||||||
|
if (colonIndex > -1) {
|
||||||
|
const key = restOfLine.substring(0, colonIndex).trim();
|
||||||
|
const value = restOfLine.substring(colonIndex + 1).trim();
|
||||||
|
item[key] = value;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
} else if (currentKey === "tags") {
|
||||||
|
if (!currentArray) {
|
||||||
|
currentArray = [];
|
||||||
|
result[currentKey] = currentArray;
|
||||||
|
}
|
||||||
|
const value = trimmed.substring(2).trim();
|
||||||
|
currentArray.push(value);
|
||||||
|
}
|
||||||
|
}
|
||||||
|
// Handle key-value pairs
|
||||||
|
else if (trimmed.includes(":")) {
|
||||||
|
const colonIndex = trimmed.indexOf(":");
|
||||||
|
const key = trimmed.substring(0, colonIndex).trim();
|
||||||
|
let value = trimmed.substring(colonIndex + 1).trim();
|
||||||
|
|
||||||
|
if (leadingSpaces === 0) {
|
||||||
|
// Top-level property
|
||||||
|
currentKey = key;
|
||||||
|
currentArray = null;
|
||||||
|
currentObject = null;
|
||||||
|
|
||||||
|
if (value) {
|
||||||
|
// Handle array format [item1, item2, item3]
|
||||||
|
if (value.startsWith("[") && value.endsWith("]")) {
|
||||||
|
const arrayContent = value.slice(1, -1);
|
||||||
|
if (arrayContent.trim()) {
|
||||||
|
result[key] = arrayContent.split(",").map(item => item.trim());
|
||||||
|
} else {
|
||||||
|
result[key] = [];
|
||||||
|
}
|
||||||
|
currentKey = null; // Reset since we handled the array
|
||||||
|
} else {
|
||||||
|
result[key] = value;
|
||||||
|
}
|
||||||
|
} else if (key === "items" || key === "tags") {
|
||||||
|
// Will be populated by array items
|
||||||
|
result[key] = [];
|
||||||
|
currentArray = result[key];
|
||||||
|
} else if (key === "display") {
|
||||||
|
result[key] = {};
|
||||||
|
currentObject = result[key];
|
||||||
|
}
|
||||||
|
} else if (currentObject && leadingSpaces > 0) {
|
||||||
|
// Property of current object (e.g., display properties)
|
||||||
|
currentObject[key] = value === "true" ? true : value === "false" ? false : value;
|
||||||
|
} else if (currentArray && currentObject && leadingSpaces > 2) {
|
||||||
|
// Property of array item object
|
||||||
|
currentObject[key] = value;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
return result;
|
||||||
|
},
|
||||||
|
filePath,
|
||||||
|
null
|
||||||
|
);
|
||||||
|
}
|
||||||
|
|
||||||
|
module.exports = { parseCollectionYaml, safeFileOperation };
|
||||||
Loading…
x
Reference in New Issue
Block a user