From 0e15e611bff628f96976ae2640d312e4960e92ab Mon Sep 17 00:00:00 2001 From: Krushi Date: Wed, 7 Jan 2026 21:11:47 +0530 Subject: [PATCH 1/8] Add System Verilog style guide link in coding standards prompt --- prompts/write-coding-standards-from-file.prompt.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/prompts/write-coding-standards-from-file.prompt.md b/prompts/write-coding-standards-from-file.prompt.md index 041f5e5e..f5d115de 100644 --- a/prompts/write-coding-standards-from-file.prompt.md +++ b/prompts/write-coding-standards-from-file.prompt.md @@ -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/) +- [system Verilog 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. ``` -``` \ No newline at end of file +``` From 9e0ce96658d5ac81411d32f85dc2140c2701c185 Mon Sep 17 00:00:00 2001 From: krushideep Date: Sat, 10 Jan 2026 08:11:05 +0530 Subject: [PATCH 2/8] Update write-coding-standards-from-file.prompt.md Updates (system Verilog) to SystemVerilog to address comment on the PR --- prompts/write-coding-standards-from-file.prompt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/prompts/write-coding-standards-from-file.prompt.md b/prompts/write-coding-standards-from-file.prompt.md index f5d115de..c26d8e59 100644 --- a/prompts/write-coding-standards-from-file.prompt.md +++ b/prompts/write-coding-standards-from-file.prompt.md @@ -169,7 +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/) -- [system Verilog Style Guide](https://github.com/lowRISC/style-guides/blob/master/VerilogCodingStyle.md) +- [SystemVerilog Style Guide](https://github.com/lowRISC/style-guides/blob/master/VerilogCodingStyle.md) ## Coding Standards Templates From 75601f4f0b8a439574910097bd5a156d2e55f6aa Mon Sep 17 00:00:00 2001 From: Hunter Hogan Date: Sat, 10 Jan 2026 15:27:38 -0500 Subject: [PATCH 3/8] Fix formatting in task-planner.agent.md Without the space before the comma, VS Code interpreted the comma as part of the file name, which caused the following error even though the target file was in the target location: ``` File './task-researcher.agent.md,' not found at 'C:\Users\hunte\AppData\Roaming\Code - Insiders\User\prompts\task-researcher.agent.md,'. ``` After adding the space, the yellow squiggles and error went away. --- agents/task-planner.agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agents/task-planner.agent.md b/agents/task-planner.agent.md index 0e9fc7f2..e9a0cb66 100644 --- a/agents/task-planner.agent.md +++ b/agents/task-planner.agent.md @@ -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 From 078af396a7f0ad07c56cd3576edee03624eb64df Mon Sep 17 00:00:00 2001 From: Tsubasa Ogawa Date: Sun, 11 Jan 2026 23:10:39 +0900 Subject: [PATCH 4/8] docs(readme): update directory structure to include skills folder Reflect the addition of the skills directory in the project layout description to keep documentation in sync with the codebase. --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 58881bc9..630ab021 100644 --- a/README.md +++ b/README.md @@ -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 From 090efd486c95ee8d0f494f3d2e37dd9e4630a11a Mon Sep 17 00:00:00 2001 From: Alessandro Fragnani Date: Sun, 11 Jan 2026 12:20:47 -0300 Subject: [PATCH 5/8] Add skills for contributing commands and localization in VS Code extensions --- docs/README.skills.md | 2 ++ skills/vscode-ext-commands/SKILL.md | 21 +++++++++++++++++++++ skills/vscode-ext-localization/SKILL.md | 25 +++++++++++++++++++++++++ 3 files changed, 48 insertions(+) create mode 100644 skills/vscode-ext-commands/SKILL.md create mode 100644 skills/vscode-ext-localization/SKILL.md diff --git a/docs/README.skills.md b/docs/README.skills.md index 7c371a6e..99478369 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -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 develoment 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`
`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` | diff --git a/skills/vscode-ext-commands/SKILL.md b/skills/vscode-ext-commands/SKILL.md new file mode 100644 index 00000000..1cf0d586 --- /dev/null +++ b/skills/vscode-ext-commands/SKILL.md @@ -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 develoment 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: It's name follow 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 define the condition (`when`) for the new command is visible. diff --git a/skills/vscode-ext-localization/SKILL.md b/skills/vscode-ext-localization/SKILL.md new file mode 100644 index 00000000..e9a956d8 --- /dev/null +++ b/skills/vscode-ext-localization/SKILL.md @@ -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 used displayed to 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. Walkthough 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 From da7f2032de02cc3e1d8469cb834db69f2d529437 Mon Sep 17 00:00:00 2001 From: Alessandro Fragnani Date: Sun, 11 Jan 2026 12:56:22 -0300 Subject: [PATCH 6/8] Fix typo --- docs/README.skills.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/README.skills.md b/docs/README.skills.md index 99478369..79352bbb 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -27,7 +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 develoment 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 | +| [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 develoment 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`
`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` | From 5424543abfa302eee39c9842ca4de63b4e9d5210 Mon Sep 17 00:00:00 2001 From: Alessandro Fragnani Date: Sun, 11 Jan 2026 13:15:56 -0300 Subject: [PATCH 7/8] Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/README.skills.md | 2 +- skills/vscode-ext-commands/SKILL.md | 4 ++-- skills/vscode-ext-localization/SKILL.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/README.skills.md b/docs/README.skills.md index 79352bbb..6d91c7a4 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -27,7 +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 develoment guidelines, libraries and good practices | 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`
`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` | diff --git a/skills/vscode-ext-commands/SKILL.md b/skills/vscode-ext-commands/SKILL.md index 1cf0d586..30ab8637 100644 --- a/skills/vscode-ext-commands/SKILL.md +++ b/skills/vscode-ext-commands/SKILL.md @@ -1,6 +1,6 @@ --- 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 develoment guidelines, libraries and good practices' +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 @@ -18,4 +18,4 @@ VS Code commands must always define a `title`, independent of its category, visi * 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: It's name follow 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 define the condition (`when`) for the new command is visible. +* Side Bar commands: It's name follow 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. diff --git a/skills/vscode-ext-localization/SKILL.md b/skills/vscode-ext-localization/SKILL.md index e9a956d8..b92def23 100644 --- a/skills/vscode-ext-localization/SKILL.md +++ b/skills/vscode-ext-localization/SKILL.md @@ -11,7 +11,7 @@ This skill helps you localize every aspect of VS Code extensions 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 used displayed to end user +- Localize new or existing messages or other string resources contained in extension source code that are displayed to the end user # Instructions @@ -19,7 +19,7 @@ VS Code localization is composed by three different approaches, depending on the 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. Walkthough content (defined in its own `Markdown` files) +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 From 0eb1a4f1f70a0fad203d021e7daf9f88d7d9b5be Mon Sep 17 00:00:00 2001 From: Alessandro Fragnani Date: Sun, 11 Jan 2026 13:18:36 -0300 Subject: [PATCH 8/8] Apply suggestions from code review --- skills/vscode-ext-commands/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/vscode-ext-commands/SKILL.md b/skills/vscode-ext-commands/SKILL.md index 30ab8637..0d44dc1c 100644 --- a/skills/vscode-ext-commands/SKILL.md +++ b/skills/vscode-ext-commands/SKILL.md @@ -18,4 +18,4 @@ VS Code commands must always define a `title`, independent of its category, visi * 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: It's name follow 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. +* 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.