code-ai-installer 1.5.2 → 1.5.3

package/locales/en/.agents/skills/styling_css_stack/agents/copilot.json

@@ -1,13 +1,13 @@
 {
   "name": "styling_css_stack",
   "display_name": "Styling & CSS Stack",
-  "description": "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility.",
+  "description": "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate when writing or reviewing CSS/Less/Sass, when refactoring styles, or for questions \"how to properly style X\".",
   "default_prompt": "Use $styling_css_stack when the task matches the \"Styling & CSS Stack\" skill.",
   "triggers": [
     "styling_css_stack",
     "styling css stack",
     "Styling & CSS Stack",
-    "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility"
+    "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
   ],
   "capabilities": [
     "styling",

package/locales/en/.agents/skills/styling_css_stack/agents/gemini.json

@@ -1,13 +1,13 @@
 {
   "name": "styling_css_stack",
   "display_name": "Styling & CSS Stack",
-  "description": "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility.",
+  "description": "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate when writing or reviewing CSS/Less/Sass, when refactoring styles, or for questions \"how to properly style X\".",
   "default_prompt": "Use $styling_css_stack when the task matches the \"Styling & CSS Stack\" skill.",
   "triggers": [
     "styling_css_stack",
     "styling css stack",
     "Styling & CSS Stack",
-    "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility"
+    "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
   ],
   "capabilities": [
     "styling",

package/locales/en/.agents/skills/styling_css_stack/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Styling & CSS Stack"
-  short_description: "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-i…"
+  short_description: "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, tran…"
   default_prompt: "Use $styling_css_stack when the task matches the \"Styling & CSS Stack\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/skills/styling_css_stack/agents/qwen.json

@@ -1,13 +1,13 @@
 {
   "name": "styling_css_stack",
   "display_name": "Styling & CSS Stack",
-  "description": "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility.",
+  "description": "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate when writing or reviewing CSS/Less/Sass, when refactoring styles, or for questions \"how to properly style X\".",
   "default_prompt": "Use $styling_css_stack when the task matches the \"Styling & CSS Stack\" skill.",
   "triggers": [
     "styling_css_stack",
     "styling css stack",
     "Styling & CSS Stack",
-    "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility"
+    "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
   ],
   "capabilities": [
     "styling",

package/locales/en/.agents/skills/styling_css_stack/agents/skill.yaml

@@ -1,13 +1,13 @@
 version: 1
 name: "styling_css_stack"
 display_name: "Styling & CSS Stack"
-description: "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility."
+description: "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate when writing or reviewing CSS/Less/Sass, when refactoring styles, or for questions \"how to properly style X\"."
 default_prompt: "Use $styling_css_stack when the task matches the \"Styling & CSS Stack\" skill."
 triggers:
   - "styling_css_stack"
   - "styling css stack"
   - "Styling & CSS Stack"
-  - "Apply CSS practices - custom properties, naming conventions, responsive rules, transitions, z-index scale, dark mode, and accessibility"
+  - "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
 capabilities:
   - "styling"
   - "css"

package/locales/en/.agents/skills/system_design_checklist/agents/claude.json

@@ -1,12 +1,12 @@
 {
   "name": "system_design_checklist",
   "display_name": "System Design Checklist",
-  "description": "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback.",
+  "description": "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten.",
   "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
   "triggers": [
     "system_design_checklist",
     "system design checklist",
-    "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback"
+    "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten"
   ],
   "capabilities": [
     "system",

package/locales/en/.agents/skills/system_design_checklist/agents/copilot.json

@@ -1,12 +1,12 @@
 {
   "name": "system_design_checklist",
   "display_name": "System Design Checklist",
-  "description": "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback.",
+  "description": "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten.",
   "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
   "triggers": [
     "system_design_checklist",
     "system design checklist",
-    "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback"
+    "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten"
   ],
   "capabilities": [
     "system",

package/locales/en/.agents/skills/system_design_checklist/agents/gemini.json

@@ -1,12 +1,12 @@
 {
   "name": "system_design_checklist",
   "display_name": "System Design Checklist",
-  "description": "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback.",
+  "description": "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten.",
   "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
   "triggers": [
     "system_design_checklist",
     "system design checklist",
-    "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback"
+    "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten"
   ],
   "capabilities": [
     "system",

package/locales/en/.agents/skills/system_design_checklist/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "System Design Checklist"
-  short_description: "Use a system design checklist - functional and non-functional requirements, technical design, a…"
+  short_description: "System design checklist — functional/non-functional requirements, technical design, operations…"
   default_prompt: "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/skills/system_design_checklist/agents/qwen.json

@@ -1,12 +1,12 @@
 {
   "name": "system_design_checklist",
   "display_name": "System Design Checklist",
-  "description": "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback.",
+  "description": "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten.",
   "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
   "triggers": [
     "system_design_checklist",
     "system design checklist",
-    "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback"
+    "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten"
   ],
   "capabilities": [
     "system",

package/locales/en/.agents/skills/system_design_checklist/agents/skill.yaml

@@ -1,12 +1,12 @@
 version: 1
 name: "system_design_checklist"
 display_name: "System Design Checklist"
-description: "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback."
+description: "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten."
 default_prompt: "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill."
 triggers:
   - "system_design_checklist"
   - "system design checklist"
-  - "Use a system design checklist - functional and non-functional requirements, technical design, and operational concerns such as deploy, monitoring, backup, and rollback"
+  - "System design checklist — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), to ensure nothing is forgotten"
 capabilities:
   - "system"
   - "design"

package/locales/en/.agents/skills/tailwind_beast_practices/agents/claude.json

@@ -1,12 +1,12 @@
 {
   "name": "tailwind_beast_practices",
   "display_name": "Tailwind Beast Practices",
-  "description": "Tailwind CSS best practices for senior-level work: class organization, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever a task concerns styling via Tailwind ? writing classes, structuring config, working with design, avoiding className chaos, or integrating with React/Next.js.",
+  "description": "Tailwind CSS best practices for Senior level: organization of classes, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever the task concerns styling via Tailwind — writing classes, config structure, working with the design system, avoiding className chaos, or integration with React/Next.js.",
   "default_prompt": "Use $tailwind_beast_practices when the task matches the \"Tailwind Beast Practices\" skill.",
   "triggers": [
     "tailwind_beast_practices",
     "tailwind beast practices",
-    "Tailwind CSS best practices for senior-level work"
+    "Tailwind CSS best practices for Senior level"
   ],
   "capabilities": [
     "tailwind",

package/locales/en/.agents/skills/tailwind_beast_practices/agents/copilot.json

@@ -1,12 +1,12 @@
 {
   "name": "tailwind_beast_practices",
   "display_name": "Tailwind Beast Practices",
-  "description": "Tailwind CSS best practices for senior-level work: class organization, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever a task concerns styling via Tailwind ? writing classes, structuring config, working with design, avoiding className chaos, or integrating with React/Next.js.",
+  "description": "Tailwind CSS best practices for Senior level: organization of classes, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever the task concerns styling via Tailwind — writing classes, config structure, working with the design system, avoiding className chaos, or integration with React/Next.js.",
   "default_prompt": "Use $tailwind_beast_practices when the task matches the \"Tailwind Beast Practices\" skill.",
   "triggers": [
     "tailwind_beast_practices",
     "tailwind beast practices",
-    "Tailwind CSS best practices for senior-level work"
+    "Tailwind CSS best practices for Senior level"
   ],
   "capabilities": [
     "tailwind",

package/locales/en/.agents/skills/tailwind_beast_practices/agents/gemini.json

@@ -1,12 +1,12 @@
 {
   "name": "tailwind_beast_practices",
   "display_name": "Tailwind Beast Practices",
-  "description": "Tailwind CSS best practices for senior-level work: class organization, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever a task concerns styling via Tailwind ? writing classes, structuring config, working with design, avoiding className chaos, or integrating with React/Next.js.",
+  "description": "Tailwind CSS best practices for Senior level: organization of classes, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever the task concerns styling via Tailwind — writing classes, config structure, working with the design system, avoiding className chaos, or integration with React/Next.js.",
   "default_prompt": "Use $tailwind_beast_practices when the task matches the \"Tailwind Beast Practices\" skill.",
   "triggers": [
     "tailwind_beast_practices",
     "tailwind beast practices",
-    "Tailwind CSS best practices for senior-level work"
+    "Tailwind CSS best practices for Senior level"
   ],
   "capabilities": [
     "tailwind",

package/locales/en/.agents/skills/tailwind_beast_practices/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Tailwind Beast Practices"
-  short_description: "Tailwind CSS best practices for senior-level work: class organization, component approach, them…"
+  short_description: "Tailwind CSS best practices for Senior level: organization of classes, component approach, them…"
   default_prompt: "Use $tailwind_beast_practices when the task matches the \"Tailwind Beast Practices\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/skills/tailwind_beast_practices/agents/qwen.json

@@ -1,12 +1,12 @@
 {
   "name": "tailwind_beast_practices",
   "display_name": "Tailwind Beast Practices",
-  "description": "Tailwind CSS best practices for senior-level work: class organization, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever a task concerns styling via Tailwind ? writing classes, structuring config, working with design, avoiding className chaos, or integrating with React/Next.js.",
+  "description": "Tailwind CSS best practices for Senior level: organization of classes, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever the task concerns styling via Tailwind — writing classes, config structure, working with the design system, avoiding className chaos, or integration with React/Next.js.",
   "default_prompt": "Use $tailwind_beast_practices when the task matches the \"Tailwind Beast Practices\" skill.",
   "triggers": [
     "tailwind_beast_practices",
     "tailwind beast practices",
-    "Tailwind CSS best practices for senior-level work"
+    "Tailwind CSS best practices for Senior level"
   ],
   "capabilities": [
     "tailwind",

package/locales/en/.agents/skills/tailwind_beast_practices/agents/skill.yaml

@@ -1,12 +1,12 @@
 version: 1
 name: "tailwind_beast_practices"
 display_name: "Tailwind Beast Practices"
-description: "Tailwind CSS best practices for senior-level work: class organization, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever a task concerns styling via Tailwind ? writing classes, structuring config, working with design, avoiding className chaos, or integrating with React/Next.js."
+description: "Tailwind CSS best practices for Senior level: organization of classes, component approach, theme customization, responsive/dark mode, performance (purge/JIT), typical patterns and DO/DON'T. Use this skill whenever the task concerns styling via Tailwind — writing classes, config structure, working with the design system, avoiding className chaos, or integration with React/Next.js."
 default_prompt: "Use $tailwind_beast_practices when the task matches the \"Tailwind Beast Practices\" skill."
 triggers:
   - "tailwind_beast_practices"
   - "tailwind beast practices"
-  - "Tailwind CSS best practices for senior-level work"
+  - "Tailwind CSS best practices for Senior level"
 capabilities:
   - "tailwind"
   - "beast"

package/locales/en/.agents/skills/tanstack_beast_practices/agents/claude.json

@@ -1,7 +1,7 @@
 {
   "name": "tanstack_beast_practices",
   "display_name": "TanStack Beast Practices",
-  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server filters/sorting, virtualization for large lists. Use this skill with any work involving TanStack Query, TanStack Table, or TanStack Virtual ? writing the fetcher layer, setting up cache, building a table with server pagination, virtual lists, and questions like \"how to do X correctly with TanStack\".",
+  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server-side filters/sorting, virtualization of large lists. Use this skill for any work with TanStack Query, TanStack Table or TanStack Virtual — when writing the fetcher layer, configuring the cache, building tables with server-side pagination, virtual lists, and when asked \"how to do X correctly with TanStack\".",
   "default_prompt": "Use $tanstack_beast_practices when the task matches the \"TanStack Beast Practices\" skill.",
   "triggers": [
     "tanstack_beast_practices",

package/locales/en/.agents/skills/tanstack_beast_practices/agents/copilot.json

@@ -1,7 +1,7 @@
 {
   "name": "tanstack_beast_practices",
   "display_name": "TanStack Beast Practices",
-  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server filters/sorting, virtualization for large lists. Use this skill with any work involving TanStack Query, TanStack Table, or TanStack Virtual ? writing the fetcher layer, setting up cache, building a table with server pagination, virtual lists, and questions like \"how to do X correctly with TanStack\".",
+  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server-side filters/sorting, virtualization of large lists. Use this skill for any work with TanStack Query, TanStack Table or TanStack Virtual — when writing the fetcher layer, configuring the cache, building tables with server-side pagination, virtual lists, and when asked \"how to do X correctly with TanStack\".",
   "default_prompt": "Use $tanstack_beast_practices when the task matches the \"TanStack Beast Practices\" skill.",
   "triggers": [
     "tanstack_beast_practices",

package/locales/en/.agents/skills/tanstack_beast_practices/agents/gemini.json

@@ -1,7 +1,7 @@
 {
   "name": "tanstack_beast_practices",
   "display_name": "TanStack Beast Practices",
-  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server filters/sorting, virtualization for large lists. Use this skill with any work involving TanStack Query, TanStack Table, or TanStack Virtual ? writing the fetcher layer, setting up cache, building a table with server pagination, virtual lists, and questions like \"how to do X correctly with TanStack\".",
+  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server-side filters/sorting, virtualization of large lists. Use this skill for any work with TanStack Query, TanStack Table or TanStack Virtual — when writing the fetcher layer, configuring the cache, building tables with server-side pagination, virtual lists, and when asked \"how to do X correctly with TanStack\".",
   "default_prompt": "Use $tanstack_beast_practices when the task matches the \"TanStack Beast Practices\" skill.",
   "triggers": [
     "tanstack_beast_practices",

package/locales/en/.agents/skills/tanstack_beast_practices/agents/qwen.json

@@ -1,7 +1,7 @@
 {
   "name": "tanstack_beast_practices",
   "display_name": "TanStack Beast Practices",
-  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server filters/sorting, virtualization for large lists. Use this skill with any work involving TanStack Query, TanStack Table, or TanStack Virtual ? writing the fetcher layer, setting up cache, building a table with server pagination, virtual lists, and questions like \"how to do X correctly with TanStack\".",
+  "description": "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server-side filters/sorting, virtualization of large lists. Use this skill for any work with TanStack Query, TanStack Table or TanStack Virtual — when writing the fetcher layer, configuring the cache, building tables with server-side pagination, virtual lists, and when asked \"how to do X correctly with TanStack\".",
   "default_prompt": "Use $tanstack_beast_practices when the task matches the \"TanStack Beast Practices\" skill.",
   "triggers": [
     "tanstack_beast_practices",

package/locales/en/.agents/skills/tanstack_beast_practices/agents/skill.yaml

@@ -1,7 +1,7 @@
 version: 1
 name: "tanstack_beast_practices"
 display_name: "TanStack Beast Practices"
-description: "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server filters/sorting, virtualization for large lists. Use this skill with any work involving TanStack Query, TanStack Table, or TanStack Virtual ? writing the fetcher layer, setting up cache, building a table with server pagination, virtual lists, and questions like \"how to do X correctly with TanStack\"."
+description: "TanStack (Query v5, Table v8, Virtual v3): caching, invalidation, pagination, infinite scroll, server-side filters/sorting, virtualization of large lists. Use this skill for any work with TanStack Query, TanStack Table or TanStack Virtual — when writing the fetcher layer, configuring the cache, building tables with server-side pagination, virtual lists, and when asked \"how to do X correctly with TanStack\"."
 default_prompt: "Use $tanstack_beast_practices when the task matches the \"TanStack Beast Practices\" skill."
 triggers:
   - "tanstack_beast_practices"

package/locales/en/.agents/skills/tdd_workflow/agents/claude.json

@@ -1,12 +1,12 @@
 {
   "name": "tdd_workflow",
   "display_name": "TDD Workflow",
-  "description": "Development strictly by TDD (RED→GREEN→REFACTOR): wording test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill Always when needed write tests, develop a feature via TDD, review tests or explain why a test is fragile. Activate with questions «how test X», «why test breaks with refactoring», «what a good test is».",
+  "description": "Development strictly according to TDD (RED→GREEN→REFACTOR): formulating test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill ALWAYS when you need to write tests, develop a feature via TDD, conduct a review of tests, or explain why a test is fragile. Activate upon questions \"how to test X\", \"why the test breaks during refactoring\", \"what is a good test\".",
   "default_prompt": "Use $tdd_workflow when the task matches the \"TDD Workflow\" skill.",
   "triggers": [
     "tdd_workflow",
     "tdd workflow",
-    "Development strictly by TDD (RED→GREEN→REFACTOR)"
+    "Development strictly according to TDD (RED→GREEN→REFACTOR)"
   ],
   "capabilities": [
     "tdd",

package/locales/en/.agents/skills/tdd_workflow/agents/copilot.json

@@ -1,12 +1,12 @@
 {
   "name": "tdd_workflow",
   "display_name": "TDD Workflow",
-  "description": "Development strictly by TDD (RED→GREEN→REFACTOR): wording test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill Always when needed write tests, develop a feature via TDD, review tests or explain why a test is fragile. Activate with questions «how test X», «why test breaks with refactoring», «what a good test is».",
+  "description": "Development strictly according to TDD (RED→GREEN→REFACTOR): formulating test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill ALWAYS when you need to write tests, develop a feature via TDD, conduct a review of tests, or explain why a test is fragile. Activate upon questions \"how to test X\", \"why the test breaks during refactoring\", \"what is a good test\".",
   "default_prompt": "Use $tdd_workflow when the task matches the \"TDD Workflow\" skill.",
   "triggers": [
     "tdd_workflow",
     "tdd workflow",
-    "Development strictly by TDD (RED→GREEN→REFACTOR)"
+    "Development strictly according to TDD (RED→GREEN→REFACTOR)"
   ],
   "capabilities": [
     "tdd",

package/locales/en/.agents/skills/tdd_workflow/agents/gemini.json

@@ -1,12 +1,12 @@
 {
   "name": "tdd_workflow",
   "display_name": "TDD Workflow",
-  "description": "Development strictly by TDD (RED→GREEN→REFACTOR): wording test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill Always when needed write tests, develop a feature via TDD, review tests or explain why a test is fragile. Activate with questions «how test X», «why test breaks with refactoring», «what a good test is».",
+  "description": "Development strictly according to TDD (RED→GREEN→REFACTOR): formulating test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill ALWAYS when you need to write tests, develop a feature via TDD, conduct a review of tests, or explain why a test is fragile. Activate upon questions \"how to test X\", \"why the test breaks during refactoring\", \"what is a good test\".",
   "default_prompt": "Use $tdd_workflow when the task matches the \"TDD Workflow\" skill.",
   "triggers": [
     "tdd_workflow",
     "tdd workflow",
-    "Development strictly by TDD (RED→GREEN→REFACTOR)"
+    "Development strictly according to TDD (RED→GREEN→REFACTOR)"
   ],
   "capabilities": [
     "tdd",

package/locales/en/.agents/skills/tdd_workflow/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "TDD Workflow"
-  short_description: "Development strictly by TDD (RED→GREEN→REFACTOR): wording test cases via user journey, unit + i…"
+  short_description: "Development strictly according to TDD (RED→GREEN→REFACTOR): formulating test cases via user jou…"
   default_prompt: "Use $tdd_workflow when the task matches the \"TDD Workflow\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/skills/tdd_workflow/agents/qwen.json

@@ -1,12 +1,12 @@
 {
   "name": "tdd_workflow",
   "display_name": "TDD Workflow",
-  "description": "Development strictly by TDD (RED→GREEN→REFACTOR): wording test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill Always when needed write tests, develop a feature via TDD, review tests or explain why a test is fragile. Activate with questions «how test X», «why test breaks with refactoring», «what a good test is».",
+  "description": "Development strictly according to TDD (RED→GREEN→REFACTOR): formulating test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill ALWAYS when you need to write tests, develop a feature via TDD, conduct a review of tests, or explain why a test is fragile. Activate upon questions \"how to test X\", \"why the test breaks during refactoring\", \"what is a good test\".",
   "default_prompt": "Use $tdd_workflow when the task matches the \"TDD Workflow\" skill.",
   "triggers": [
     "tdd_workflow",
     "tdd workflow",
-    "Development strictly by TDD (RED→GREEN→REFACTOR)"
+    "Development strictly according to TDD (RED→GREEN→REFACTOR)"
   ],
   "capabilities": [
     "tdd",

package/locales/en/.agents/skills/tdd_workflow/agents/skill.yaml

@@ -1,12 +1,12 @@
 version: 1
 name: "tdd_workflow"
 display_name: "TDD Workflow"
-description: "Development strictly by TDD (RED→GREEN→REFACTOR): wording test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill Always when needed write tests, develop a feature via TDD, review tests or explain why a test is fragile. Activate with questions «how test X», «why test breaks with refactoring», «what a good test is»."
+description: "Development strictly according to TDD (RED→GREEN→REFACTOR): formulating test cases via user journey, unit + integration tests with Vitest and Testing Library, e2e with Playwright for critical flows. Use this skill ALWAYS when you need to write tests, develop a feature via TDD, conduct a review of tests, or explain why a test is fragile. Activate upon questions \"how to test X\", \"why the test breaks during refactoring\", \"what is a good test\"."
 default_prompt: "Use $tdd_workflow when the task matches the \"TDD Workflow\" skill."
 triggers:
   - "tdd_workflow"
   - "tdd workflow"
-  - "Development strictly by TDD (RED→GREEN→REFACTOR)"
+  - "Development strictly according to TDD (RED→GREEN→REFACTOR)"
 capabilities:
   - "tdd"
   - "workflow"

package/locales/en/.agents/skills/testing_strategy_js/agents/claude.json

@@ -1,13 +1,13 @@
 {
   "name": "testing_strategy_js",
   "display_name": "JS/TS Testing Strategy",
-  "description": "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration.",
+  "description": "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright). AAA pattern, Vitest config, React Testing Library, mocks of external services, coverage thresholds, naming conventions, CI pipeline. Activate when writing new tests, refactoring existing ones, or for questions \"how to properly test X\".",
   "default_prompt": "Use $testing_strategy_js when the task matches the \"JS/TS Testing Strategy\" skill.",
   "triggers": [
     "testing_strategy_js",
     "testing strategy js",
     "JS/TS Testing Strategy",
-    "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration"
+    "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright)"
   ],
   "capabilities": [
     "testing",

package/locales/en/.agents/skills/testing_strategy_js/agents/copilot.json

@@ -1,13 +1,13 @@
 {
   "name": "testing_strategy_js",
   "display_name": "JS/TS Testing Strategy",
-  "description": "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration.",
+  "description": "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright). AAA pattern, Vitest config, React Testing Library, mocks of external services, coverage thresholds, naming conventions, CI pipeline. Activate when writing new tests, refactoring existing ones, or for questions \"how to properly test X\".",
   "default_prompt": "Use $testing_strategy_js when the task matches the \"JS/TS Testing Strategy\" skill.",
   "triggers": [
     "testing_strategy_js",
     "testing strategy js",
     "JS/TS Testing Strategy",
-    "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration"
+    "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright)"
   ],
   "capabilities": [
     "testing",

package/locales/en/.agents/skills/testing_strategy_js/agents/gemini.json

@@ -1,13 +1,13 @@
 {
   "name": "testing_strategy_js",
   "display_name": "JS/TS Testing Strategy",
-  "description": "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration.",
+  "description": "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright). AAA pattern, Vitest config, React Testing Library, mocks of external services, coverage thresholds, naming conventions, CI pipeline. Activate when writing new tests, refactoring existing ones, or for questions \"how to properly test X\".",
   "default_prompt": "Use $testing_strategy_js when the task matches the \"JS/TS Testing Strategy\" skill.",
   "triggers": [
     "testing_strategy_js",
     "testing strategy js",
     "JS/TS Testing Strategy",
-    "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration"
+    "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright)"
   ],
   "capabilities": [
     "testing",

package/locales/en/.agents/skills/testing_strategy_js/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "JS/TS Testing Strategy"
-  short_description: "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AA…"
+  short_description: "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright). AA…"
   default_prompt: "Use $testing_strategy_js when the task matches the \"JS/TS Testing Strategy\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/skills/testing_strategy_js/agents/qwen.json

@@ -1,13 +1,13 @@
 {
   "name": "testing_strategy_js",
   "display_name": "JS/TS Testing Strategy",
-  "description": "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration.",
+  "description": "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright). AAA pattern, Vitest config, React Testing Library, mocks of external services, coverage thresholds, naming conventions, CI pipeline. Activate when writing new tests, refactoring existing ones, or for questions \"how to properly test X\".",
   "default_prompt": "Use $testing_strategy_js when the task matches the \"JS/TS Testing Strategy\" skill.",
   "triggers": [
     "testing_strategy_js",
     "testing strategy js",
     "JS/TS Testing Strategy",
-    "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration"
+    "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright)"
   ],
   "capabilities": [
     "testing",

package/locales/en/.agents/skills/testing_strategy_js/agents/skill.yaml

@@ -1,13 +1,13 @@
 version: 1
 name: "testing_strategy_js"
 display_name: "JS/TS Testing Strategy"
-description: "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration."
+description: "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright). AAA pattern, Vitest config, React Testing Library, mocks of external services, coverage thresholds, naming conventions, CI pipeline. Activate when writing new tests, refactoring existing ones, or for questions \"how to properly test X\"."
 default_prompt: "Use $testing_strategy_js when the task matches the \"JS/TS Testing Strategy\" skill."
 triggers:
   - "testing_strategy_js"
   - "testing strategy js"
   - "JS/TS Testing Strategy"
-  - "Define a testing strategy for JS and TS projects - unit tests, integration tests, E2E tests, AAA structure, tooling, mocks, coverage thresholds, and CI integration"
+  - "Testing strategy for JS/TS projects — unit (Vitest), integration (API/DB), e2e (Playwright)"
 capabilities:
   - "testing"
   - "strategy"

package/locales/en/.agents/skills/tests_quality_review/agents/claude.json

@@ -1,12 +1,12 @@
 {
   "name": "tests_quality_review",
   "display_name": "Tests Quality Review",
-  "description": "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risks, and checklist-based findings.",
+  "description": "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence of flakes and test \"magic\". Prioritized checklist, good/bad test examples, output report template. Activate when reviewing existing tests, stabilizing flaky tests, or auditing test suite quality.",
   "default_prompt": "Use $tests_quality_review when the task matches the \"Tests Quality Review\" skill.",
   "triggers": [
     "tests_quality_review",
     "tests quality review",
-    "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risks, and checklist-based findings"
+    "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence of flakes and test \"magic\""
   ],
   "capabilities": [
     "tests",

package/locales/en/.agents/skills/tests_quality_review/agents/copilot.json

@@ -1,12 +1,12 @@
 {
   "name": "tests_quality_review",
   "display_name": "Tests Quality Review",
-  "description": "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risks, and checklist-based findings.",
+  "description": "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence of flakes and test \"magic\". Prioritized checklist, good/bad test examples, output report template. Activate when reviewing existing tests, stabilizing flaky tests, or auditing test suite quality.",
   "default_prompt": "Use $tests_quality_review when the task matches the \"Tests Quality Review\" skill.",
   "triggers": [
     "tests_quality_review",
     "tests quality review",
-    "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risks, and checklist-based findings"
+    "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence of flakes and test \"magic\""
   ],
   "capabilities": [
     "tests",

package/locales/en/.agents/skills/tests_quality_review/agents/gemini.json

@@ -1,12 +1,12 @@
 {
   "name": "tests_quality_review",
   "display_name": "Tests Quality Review",
-  "description": "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risks, and checklist-based findings.",
+  "description": "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence of flakes and test \"magic\". Prioritized checklist, good/bad test examples, output report template. Activate when reviewing existing tests, stabilizing flaky tests, or auditing test suite quality.",
   "default_prompt": "Use $tests_quality_review when the task matches the \"Tests Quality Review\" skill.",
   "triggers": [
     "tests_quality_review",
     "tests quality review",
-    "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risks, and checklist-based findings"
+    "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence of flakes and test \"magic\""
   ],
   "capabilities": [
     "tests",

package/locales/en/.agents/skills/tests_quality_review/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Tests Quality Review"
-  short_description: "Review the quality of unit and integration tests - coverage, boundaries, resilience, flake risk…"
+  short_description: "Quality review of unit/integration tests — scenario coverage, boundaries, resilience, absence o…"
   default_prompt: "Use $tests_quality_review when the task matches the \"Tests Quality Review\" skill."
 dependencies:
   tools: []