mirror of
https://github.com/github/awesome-copilot.git
synced 2026-02-20 18:35:14 +00:00
Merge branch 'main' into update-research-technical-spike
This commit is contained in:
Daniel Scott-Raynsford
GitHub
@@ -104,7 +104,8 @@ For AI coding agents working with this project, refer to [AGENTS.md](AGENTS.md)
|
||||
├── instructions/ # Coding standards and best practices (.instructions.md)
|
||||
├── agents/ # AI personas and specialized modes (.agent.md)
|
||||
├── collections/ # Curated collections of related items (.collection.yml)
|
||||
└── scripts/ # Utility scripts for maintenance
|
||||
├── scripts/ # Utility scripts for maintenance
|
||||
└── skills/ # AI capabilities for specialized tasks
|
||||
```
|
||||
|
||||
## 📄 License
|
||||
|
||||
@@ -63,7 +63,7 @@ You WILL process user input as follows:
|
||||
- `{{specific_action}}` → "Create eventstream module with custom endpoint support"
|
||||
- **Final Output**: You WILL ensure NO template markers remain in final files
|
||||
|
||||
**CRITICAL**: If you encounter invalid file references or broken line numbers, you WILL update the research file first using #file:./task-researcher.agent.md, then update all dependent planning files.
|
||||
**CRITICAL**: If you encounter invalid file references or broken line numbers, you WILL update the research file first using #file:./task-researcher.agent.md , then update all dependent planning files.
|
||||
|
||||
## File Naming Standards
|
||||
|
||||
|
||||
@@ -27,5 +27,7 @@ Skills differ from other primitives by supporting bundled assets (scripts, code
|
||||
| [github-issues](../skills/github-issues/SKILL.md) | Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task. | `references/templates.md` |
|
||||
| [nuget-manager](../skills/nuget-manager/SKILL.md) | Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions. | None |
|
||||
| [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md) | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None |
|
||||
| [vscode-ext-commands](../skills/vscode-ext-commands/SKILL.md) | Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices | None |
|
||||
| [vscode-ext-localization](../skills/vscode-ext-localization/SKILL.md) | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices | None |
|
||||
| [web-design-reviewer](../skills/web-design-reviewer/SKILL.md) | This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level. | `references/framework-fixes.md`<br />`references/visual-checklist.md` |
|
||||
| [webapp-testing](../skills/webapp-testing/SKILL.md) | Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. | `test-helper.js` |
|
||||
|
||||
@@ -10,7 +10,7 @@ Use the existing syntax of the file(s) to establish the standards and style guid
|
||||
|
||||
## Rules and Configuration
|
||||
|
||||
Below is a set of quasi-configuration `boolean` and `string[]` variables. Conditions for handling `true`, or other values for each variable are under the level two heading `## Variable and Parameter Configuration Conditions`.
|
||||
Below is a set of quasi-configuration `boolean` and `string[]` variables. Conditions for handling `true`, or other values for each variable are under the level two heading `## Variable and Parameter Configuration Conditions`.
|
||||
|
||||
Parameters for the prompt have a text definition. There is one required parameter **`${fileName}`**, and several optional parameters **`${folderName}`**, **`${instructions}`**, and any **`[configVariableAsParameter]`**.
|
||||
|
||||
@@ -169,6 +169,7 @@ Depending on the programming language, for each link in list below, run `#fetch
|
||||
- [Angular Style Guide](https://angular.dev/style-guide)
|
||||
- [Vue Style Guide](https://vuejs.org/style-guide/rules-strongly-recommended.html)
|
||||
- [Django Style Guide](https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/)
|
||||
- [SystemVerilog Style Guide](https://github.com/lowRISC/style-guides/blob/master/VerilogCodingStyle.md)
|
||||
|
||||
## Coding Standards Templates
|
||||
|
||||
@@ -222,7 +223,7 @@ Depending on the programming language, for each link in list below, run `#fetch
|
||||
|
||||
# Style Guide
|
||||
|
||||
This document defines the style and conventions used in this project.
|
||||
This document defines the style and conventions used in this project.
|
||||
All contributions should follow these rules unless otherwise noted.
|
||||
|
||||
## 1. General Code Style
|
||||
@@ -310,7 +311,7 @@ Depending on the programming language, for each link in list below, run `#fetch
|
||||
|
||||
## 8. Changes to This Guide
|
||||
|
||||
Style evolves.
|
||||
Style evolves.
|
||||
Propose improvements by opening an issue or sending a patch updating this document.
|
||||
```
|
||||
```
|
||||
```
|
||||
|
||||
21
skills/vscode-ext-commands/SKILL.md
Normal file
21
skills/vscode-ext-commands/SKILL.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
name: vscode-ext-commands
|
||||
description: 'Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices'
|
||||
---
|
||||
|
||||
# VS Code extension command contribution
|
||||
|
||||
This skill helps you to contribute commands in VS Code extensions
|
||||
|
||||
## When to use this skill
|
||||
|
||||
Use this skill when you need to:
|
||||
- Add or update commands to your VS Code extension
|
||||
|
||||
# Instructions
|
||||
|
||||
VS Code commands must always define a `title`, independent of its category, visibility or location. We use a few patterns for each "kind" of command, with some characteristics, described below:
|
||||
|
||||
* Regular commands: By default, all commands should be accessible in the Command Palette, must define a `category`, and don't need an `icon`, unless the command will be used in the Side Bar.
|
||||
|
||||
* Side Bar commands: Its name follows a special pattern, starting with underscore (`_`) and suffixed with `#sideBar`, like `_extensionId.someCommand#sideBar` for instance. Must define an `icon`, and may or may not have some rule for `enablement`. Side Bar exclusive commands should not be visible in the Command Palette. Contributing it to the `view/title` or `view/item/context`, we must inform _order/position_ that it will be displayed, and we can use terms "relative to other command/button" in order to you identify the correct `group` to be used. Also, it's a good practice to define the condition (`when`) for the new command is visible.
|
||||
25
skills/vscode-ext-localization/SKILL.md
Normal file
25
skills/vscode-ext-localization/SKILL.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
name: vscode-ext-localization
|
||||
description: 'Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices'
|
||||
---
|
||||
|
||||
# VS Code extension localization
|
||||
|
||||
This skill helps you localize every aspect of VS Code extensions
|
||||
|
||||
## When to use this skill
|
||||
|
||||
Use this skill when you need to:
|
||||
- Localize new or existing contributed configurations (settings), commands, menus, views or walkthroughs
|
||||
- Localize new or existing messages or other string resources contained in extension source code that are displayed to the end user
|
||||
|
||||
# Instructions
|
||||
|
||||
VS Code localization is composed by three different approaches, depending on the resource that is being localized. When a new localizable resource is created or updated, the corresponding localization for all currently available languages must be created/updated.
|
||||
|
||||
1. Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in `package.json`
|
||||
-> An exclusive `package.nls.LANGID.json` file, like `package.nls.pt-br.json` of Brazilian Portuguese (`pt-br`) localization
|
||||
2. Walkthrough content (defined in its own `Markdown` files)
|
||||
-> An exclusive `Markdown` file like `walkthrough/someStep.pt-br.md` for Brazilian Portuguese localization
|
||||
3. Messages and string located in extension source code (JavaScript or TypeScript files)
|
||||
-> An exclusive `bundle.l10n.pt-br.json` for Brazilian Portuguese localization
|
||||
Reference in New Issue
Block a user