@cubis/foundry 0.3.82 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/remix/SKILL.md

@@ -76,8 +76,12 @@ Load only what the current task requires.
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/requesting-code-review/SKILL.md

@@ -73,8 +73,12 @@ When preparing a review request, provide:
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/rust-best-practices/SKILL.md

@@ -81,8 +81,12 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/sadd/SKILL.md

@@ -64,8 +64,12 @@ When performing SADD, provide:
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/sanitize-pii/SKILL.md

@@ -100,8 +100,12 @@ Guide the detection, classification, and sanitization of personally identifiable
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/secret-management/SKILL.md

@@ -97,8 +97,12 @@ Guide the design and implementation of robust secret and credential management s
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/skill-creator/SKILL.md

@@ -160,8 +160,12 @@ skill-creator
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/spec-driven-delivery/SKILL.md

@@ -63,8 +63,12 @@ Deliver:
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/spring-boot/SKILL.md

@@ -72,8 +72,12 @@ Provide implementation code, configuration properties, bean definitions, and arc
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/sqlalchemy/SKILL.md

@@ -81,8 +81,12 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/stitch/SKILL.md

@@ -85,8 +85,12 @@ Use these when the task closely matches the example shape.
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/stripe-integration/SKILL.md

@@ -88,8 +88,12 @@ Guide the design and implementation of production-grade Stripe payment integrati
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/svelte-sveltekit/SKILL.md

@@ -84,8 +84,12 @@ Load detailed guidance based on context:
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/swift-best-practices/SKILL.md

@@ -85,8 +85,12 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/system-design/SKILL.md

@@ -80,8 +80,12 @@ Load only what the current task requires.
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/systematic-debugging/SKILL.md

@@ -115,8 +115,12 @@ Provide a disciplined, evidence-based framework for diagnosing and resolving sof
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/t3-stack/SKILL.md

@@ -76,8 +76,12 @@ Provide implementation code, schema definitions, configuration snippets, and arc
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/tech-doc/SKILL.md

@@ -79,8 +79,12 @@ Load on demand. Do not preload all reference files.
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/typescript-best-practices/SKILL.md

@@ -81,8 +81,12 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/unit-testing/SKILL.md

@@ -98,8 +98,12 @@ Provide a rigorous, repeatable methodology for designing, writing, and maintaini
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vibesec/SKILL.md

@@ -94,8 +94,12 @@ Deliver a fast, opinionated security assessment that catches the most common and
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/vuejs/SKILL.md

@@ -85,8 +85,12 @@ Load detailed guidance based on context:
 
 ## Copilot Platform Notes
 
-- Skill files are stored under `.github/prompts/` (prompt files) and `.github/instructions/` (instruction files).
-- Copilot does not support subagent spawning — all skill guidance executes within the current conversation context.
+- Custom agents are defined in `.github/agents/*.md` with YAML frontmatter: `name`, `description`, `tools`, `model`, `handoffs`.
+- Agent `handoffs` field enables guided workflow transitions (e.g., `@project-planner` → `@orchestrator`).
+- Skill files are stored under `.github/skills/` (skill markdown) and `.github/prompts/` (prompt files).
+- Path-scoped instructions in `.github/instructions/*.instructions.md` provide file-pattern-targeted guidance via `applyTo` frontmatter.
 - User arguments are provided as natural language input in the prompt, not through a `$ARGUMENTS` variable.
-- Frontmatter keys `context`, `agent`, and `allowed-tools` are not supported; guidance is advisory only.
+- Frontmatter keys `context: fork` and `allowed-tools` are not natively supported; guidance is advisory.
 - Reference files can be included via `#file:references/<name>.md` syntax in Copilot Chat.
+- MCP configuration lives in `.vscode/mcp.json`. MCP skill tools are available when configured.
+- Rules file: `.github/copilot-instructions.md` — broad and stable, not task-specific.

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/accessibility.toml

@@ -1,19 +1,84 @@
 description = "Run a structured accessibility audit on web UI code with WCAG 2.2 AA compliance checks, ARIA validation, keyboard navigation testing, and screen reader verification."
 prompt = '''
-Follow the /accessibility workflow from .gemini/workflows/accessibility.md.
+Execute the native projection of the /accessibility workflow.
+
+Run a structured accessibility audit on web UI code with WCAG 2.2 AA compliance checks, ARIA validation, keyboard navigation testing, and screen reader verification.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
 2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
 Attached skills:
 - Load these exact skill IDs first: `code-review`, `frontend-design`, `performance-testing`, `react`, `nextjs`, `playwright-interactive`, `typescript-best-practices`, `javascript-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/code-review/SKILL.md`, `.gemini/skills/frontend-design/SKILL.md`, `.gemini/skills/performance-testing/SKILL.md`, `.gemini/skills/react/SKILL.md`, `.gemini/skills/nextjs/SKILL.md`, `.gemini/skills/playwright-interactive/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/code-review/SKILL.md`, `.agents/skills/frontend-design/SKILL.md`, `.agents/skills/performance-testing/SKILL.md`, `.agents/skills/react/SKILL.md`, `.agents/skills/nextjs/SKILL.md`, `.agents/skills/playwright-interactive/SKILL.md`, `.agents/skills/typescript-best-practices/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`.
 - Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Confirm the request fits the workflow's "When to use" section.
+3. Confirm the request fits the workflow's "When to use" section before acting.
 4. Execute according to "Workflow steps" and apply "Context notes".
 5. Complete "Verification" checks and report concrete evidence.
-6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to the researcher posture first.
+6. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or route to research first.
 7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
+Workflow source:
+# Accessibility Workflow
+
+## When to use
+
+Use this for accessibility audits, WCAG compliance review, or improving accessible user experience.
+
+## Routing
+
+- Primary specialist: `@frontend-specialist`
+- Verification support: `@test-engineer`
+- Review support: `@validator`
+
+## Context notes
+
+- This workflow file, active platform rules, and selected agents or skills guide execution.
+- Attach the target components, pages, or routes to audit. Include any existing axe or Lighthouse results.
+
+## Skill Routing
+
+- Primary skills: `frontend-code-review`, `frontend-design`
+- Supporting skills (optional): `i18n-localization`, `web-perf`, `react-expert`, `nextjs-developer`, `tailwind-patterns`, `playwright-e2e`, `typescript-pro`, `javascript-pro`
+- Start with `frontend-code-review` for WCAG compliance checks. Add `frontend-design` for accessible design patterns. Add `i18n-localization` for RTL and locale-specific accessibility.
+
+## Workflow steps
+
+1. Inventory components and user flows to audit.
+2. Run automated accessibility checks (axe, Lighthouse).
+3. Manual keyboard navigation and focus management review.
+4. ARIA validation — correct roles, states, and properties.
+5. Screen reader compatibility assessment.
+6. Prioritize findings and provide remediation guidance.
+
+## Verification
+
+- All critical WCAG 2.2 AA violations identified.
+- Keyboard navigation works for all interactive elements.
+- ARIA attributes are semantically correct.
+- Color contrast meets minimum ratios.
+- Focus management is logical and visible.
+
+## Output Contract
+
+```yaml
+ACCESSIBILITY_WORKFLOW_RESULT:
+  primary_agent: frontend-specialist
+  supporting_agents: [test-engineer?, validator?]
+  primary_skills: [frontend-code-review, frontend-design]
+  supporting_skills: [i18n-localization?, web-perf?, playwright-e2e?]
+  audit_scope: [<component-or-route>]
+  findings:
+    - severity: critical | high | medium | low
+      wcag_criterion: <string>
+      element: <string>
+      description: <string>
+      remediation: <string>
+  automated_results:
+    tool: <axe | lighthouse | other>
+    violations: <number>
+    passes: <number>
+  follow_up_items: [<string>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/gemini/commands/agent-backend-specialist.toml

@@ -0,0 +1,86 @@
+description = "Backend specialist for API contracts, service logic, schema-aware backend changes, auth-sensitive implementation, payment integrations, and serverless architecture. Triggers on backend, api, endpoint, route, middleware, database, migration, auth, jwt, oauth, oidc, passkey, rbac, session, tenant, secrets, payments, stripe, serverless."
+prompt = '''
+Execute the native projection of the @backend-specialist specialist route.
+
+Backend specialist for API contracts, service logic, schema-aware backend changes, auth-sensitive implementation, payment integrations, and serverless architecture. Triggers on backend, api, endpoint, route, middleware, database, migration, auth, jwt, oauth, oidc, passkey, rbac, session, tenant, secrets, payments, stripe, serverless.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `docs/foundation/MEMORY.md` first when it exists, then load deeper foundation docs only when needed.
+Attached skills:
+- Load these exact skill IDs first: `api-design`, `system-design`, `owasp-security-review`, `database-design`, `drizzle-orm`, `microservices-design`, `javascript-best-practices`, `nestjs`, `fastapi`, `stripe-integration`, `ci-cd-pipeline`, `frontend-design`, `typescript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `php-best-practices`.
+- Local skill file hints if installed: `.agents/skills/api-design/SKILL.md`, `.agents/skills/system-design/SKILL.md`, `.agents/skills/owasp-security-review/SKILL.md`, `.agents/skills/database-design/SKILL.md`, `.agents/skills/drizzle-orm/SKILL.md`, `.agents/skills/microservices-design/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/skills/nestjs/SKILL.md`.
+- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
+3. Stay within the specialist scope and escalate to a broader workflow when the task crosses domains.
+4. Run focused verification for the changes or analysis you perform.
+5. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
+
+Specialist source:
+# Backend Specialist
+
+Build backend systems that stay correct under production pressure.
+
+## Skill Loading Contract
+
+- Do not call `skill_search` for any skill in the pre-declared list when the task clearly falls into that domain.
+- Load one primary skill first based on the dominant concern:
+  - `api-design` for API contract shape, versioning, or endpoint design
+  - `api-patterns` for REST/RPC conventions and HTTP semantics
+  - `auth-architect` for authentication, authorization, session, RBAC, or SSO flows
+  - `database-design` for schema design, query optimization, or migration planning
+  - `nestjs-expert` for NestJS-specific module, provider, or decorator patterns
+  - `fastapi-expert` for FastAPI route, dependency injection, or Pydantic model patterns
+  - `graphql-architect` for GraphQL schema, resolver, or subscription design
+  - `microservices-architect` for service boundaries, event-driven patterns, or distributed systems
+  - `stripe-best-practices` for payment processing, subscription management, or webhook handling
+  - `serverless-patterns` for Lambda, Edge Functions, cold starts, or serverless architecture
+  - `i18n-localization` for internationalization of backend responses, locale-aware data
+- Add one supporting skill only when the task genuinely crosses concerns.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File                      | Load when                                                                    |
+| ------------------------- | ---------------------------------------------------------------------------- |
+| `api-design`            | Designing new API contracts, versioning, or endpoint shape.                  |
+| `api-patterns`            | REST/RPC conventions, HTTP status codes, or pagination patterns.             |
+| `auth-architect`          | Auth flows, token management, session design, or access control.             |
+| `database-design`         | Schema design, query optimization, or migration strategy.                    |
+| `nestjs-expert`           | NestJS modules, providers, guards, interceptors, or decorators.              |
+| `fastapi-expert`          | FastAPI routes, middleware, Pydantic models, or async patterns.              |
+| `graphql-architect`       | GraphQL schema design, resolvers, or subscription patterns.                  |
+| `microservices-architect` | Service boundaries, event-driven architecture, or distributed transactions.  |
+| `stripe-best-practices`   | Payment processing, subscriptions, webhooks, or Stripe SDK usage.            |
+| `serverless-patterns`     | Lambda architecture, cold starts, Edge Functions, or serverless constraints. |
+| `i18n-localization`       | Locale-aware responses, pluralization, or internationalization patterns.     |
+
+## Operating Stance
+
+- Prefer explicit contracts over implicit coupling.
+- Treat auth as a first-class concern, not an afterthought.
+- Design for observability: structured logging, correlation IDs, and clear error responses.
+- Keep database access behind a data-access layer; never scatter raw queries across handlers.
+- Validate at boundaries, trust within boundaries.
+- Prefer idempotent operations for anything that touches external state.
+
+## Decision Frameworks
+
+| When choosing... | Prefer                        | Because                                    |
+| ---------------- | ----------------------------- | ------------------------------------------ |
+| API style        | REST for CRUD, GraphQL for UI | Match consumption pattern to client needs  |
+| Auth approach    | JWT + refresh for SPAs        | Stateless scaling with secure rotation     |
+| Database access  | ORM with raw escape hatch     | Safety by default, performance when needed |
+| Error responses  | Structured error envelope     | Machine-parseable, debuggable, consistent  |
+| Background work  | Queue-based with dead-letter  | Fault tolerance and retry isolation        |
+
+## Output Expectations
+
+- Explain the main architecture decision in concrete terms.
+- Call out any security, performance, or data-integrity risk left behind.
+- Run focused checks when code changes land.
+- Note any API contract or schema changes that affect consumers.
+
+If command arguments are provided, treat them as additional user context.
+'''