@cubis/foundry 0.3.82 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-database.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /database
-
-Design or review schema, queries, and migrations with performance and integrity controls.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/database.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `database-design`, `drizzle-orm`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.github/skills/database-design/SKILL.md`, `.github/skills/drizzle-orm/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-debug.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /debug
-
-Isolate root cause quickly, apply the smallest safe remediation, and leave behind regression evidence.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/debug.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `systematic-debugging`, `observability`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `integration-testing`, `playwright-interactive`, `skill-creator`.
-- Local skill file hints if installed: `.github/skills/systematic-debugging/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/java-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-devops.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /devops
-
-Plan and execute deployment, CI/CD, incident response, and operational safety changes with rollback controls.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/devops.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `ci-cd-pipeline`, `kubernetes-deploy`, `observability`, `git-workflow`, `systematic-debugging`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/ci-cd-pipeline/SKILL.md`, `.github/skills/kubernetes-deploy/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/git-workflow/SKILL.md`, `.github/skills/systematic-debugging/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-implement-track.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /implement-track
-
-Execute large work in milestones with explicit quality gates and status updates.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/implement-track.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `system-design`, `api-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `react`, `nextjs`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/react/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-migrate.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /migrate
-
-Plan and execute technology migrations, framework upgrades, and dependency updates with rollback safety, incremental verification, and zero-downtime transition.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/migrate.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `system-design`, `code-review`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-mobile.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /mobile
-
-Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/mobile.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `expo-app`, `react-native`, `stitch`, `frontend-design`, `swift-best-practices`, `kotlin-best-practices`.
-- Local skill file hints if installed: `.github/skills/expo-app/SKILL.md`, `.github/skills/react-native/SKILL.md`, `.github/skills/stitch/SKILL.md`, `.github/skills/frontend-design/SKILL.md`, `.github/skills/swift-best-practices/SKILL.md`, `.github/skills/kotlin-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-onboard.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /onboard
-
-Survey an unfamiliar codebase, map its architecture, identify patterns and conventions, and produce a structured orientation report for new contributors.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/onboard.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `deep-research`, `system-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.github/skills/deep-research/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-orchestrate.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /orchestrate
-
-Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership, validation gates, and repeat-until-good iteration.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/orchestrate.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/mcp-server-builder/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/prompt-engineering/SKILL.md`, `.github/skills/skill-creator/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-plan.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /plan
-
-Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/plan.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/mcp-server-builder/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/prompt-engineering/SKILL.md`, `.github/skills/skill-creator/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-refactor.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /refactor
-
-Improve maintainability while preserving behavior through incremental safe refactoring.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/refactor.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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`, `system-design`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-release.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /release
-
-Prepare and execute release with rollout guardrails, verification, and rollback plan.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/release.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `ci-cd-pipeline`, `git-workflow`, `tech-doc`, `observability`, `kubernetes-deploy`, `typescript-best-practices`, `javascript-best-practices`.
-- Local skill file hints if installed: `.github/skills/ci-cd-pipeline/SKILL.md`, `.github/skills/git-workflow/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/kubernetes-deploy/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-review.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /review
-
-Run a strict review for bugs, regressions, accessibility issues, security risk, and code quality with prioritized findings.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/review.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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`, `unit-testing`, `owasp-security-review`, `performance-testing`, `react`, `nextjs`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/owasp-security-review/SKILL.md`, `.github/skills/performance-testing/SKILL.md`, `.github/skills/react/SKILL.md`, `.github/skills/nextjs/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-security.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /security
-
-Run security-focused analysis and remediation planning with exploitability-first triage.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/security.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `owasp-security-review`, `code-review`, `api-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `rust-best-practices`.
-- Local skill file hints if installed: `.github/skills/owasp-security-review/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/rust-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-spec.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /spec
-
-Create or refresh a Git-tracked spec pack for non-trivial work, including acceptance criteria, traceability, architecture impact, and next-route handoff.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/spec.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `spec-driven-delivery`, `sadd`, `system-design`, `architecture-doc`, `deep-research`, `api-design`, `database-design`, `tech-doc`.
-- Local skill file hints if installed: `.github/skills/spec-driven-delivery/SKILL.md`, `.github/skills/sadd/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/architecture-doc/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/tech-doc/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-test.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /test
-
-Design and execute verification strategy aligned to user risk, release confidence, and regression evidence.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/test.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `unit-testing`, `integration-testing`, `playwright-interactive`, `observability`, `systematic-debugging`, `code-review`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`.
-- Local skill file hints if installed: `.github/skills/unit-testing/SKILL.md`, `.github/skills/integration-testing/SKILL.md`, `.github/skills/playwright-interactive/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/systematic-debugging/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-vercel.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /vercel
-
-Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/vercel.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; 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: `nextjs`, `ci-cd-pipeline`, `performance-testing`, `react`, `frontend-design`, `javascript-best-practices`, `typescript-best-practices`.
-- Local skill file hints if installed: `.github/skills/nextjs/SKILL.md`, `.github/skills/ci-cd-pipeline/SKILL.md`, `.github/skills/performance-testing/SKILL.md`, `.github/skills/react/SKILL.md`, `.github/skills/frontend-design/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/gemini/workflows/accessibility.md

@@ -1,77 +0,0 @@
----
-command: "/accessibility"
-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."
-triggers:
-  [
-    "accessibility",
-    "a11y",
-    "wcag",
-    "aria",
-    "screen reader",
-    "keyboard navigation",
-  ]
----
-
-# Accessibility Workflow
-
-## When to use
-
-Use this for accessibility audits, WCAG compliance review, or improving accessible user experience.
-
-## Routing
-
-- Primary specialist: `the frontend-specialist posture`
-- Verification support: `the test-engineer posture`
-- Review support: `the validator posture`
-
-## 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: `code-review`, `frontend-design`
-- Supporting skills (optional): `frontend-design`, `performance-testing`, `react`, `nextjs`, `frontend-design`, `playwright-interactive`, `typescript-best-practices`, `javascript-best-practices`
-- Start with `code-review` for WCAG compliance checks. Add `frontend-design` for accessible design patterns. Add `frontend-design` 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: [code-review, frontend-design]
-  supporting_skills: [frontend-design?, performance-testing?, playwright-interactive?]
-  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>] | []
-```
-
-> **Gemini note:** Commands route into workflow files under `.gemini/workflows/`. Specialists are inline postures coordinated through GEMINI.md guidance, not separate agent artifacts.

package/workflows/workflows/agent-environment-setup/platforms/gemini/workflows/architecture.md

@@ -1,107 +0,0 @@
----
-command: "/architecture"
-description: "Refresh the core project foundation docs in docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md, and ADR scaffolds with explicit structure, product context, testing, and flow guidance."
-triggers:
-  [
-    "architecture",
-    "design system",
-    "adr",
-    "clean architecture",
-    "system map",
-    "app structure",
-    "technical governance",
-    "flow diagram",
-  ]
----
-
-# Architecture Workflow
-
-## When to use
-
-Use this when the task is to declare, refresh, or validate the project backbone docs, especially after structure changes, scale changes, design-system changes, migrations, product-direction shifts, or major feature additions.
-
-## Routing
-
-- Primary coordinator: `the project-planner posture`
-- Documentation support: `the documentation-writer posture`
-- Research support: `the researcher posture`
-- Domain validation: `the backend-specialist posture`, `the frontend-specialist posture`, `the database-architect posture`
-
-## Skill Routing
-
-- Primary skills: `architecture-doc`, `system-design`, `tech-doc`, `frontend-design`
-- Supporting skills (optional): `api-design`, `database-design`, `sadd`, `deep-research`
-- Load the four primary skills directly for this workflow. Add `api-design` or `database-design` when service or data boundaries are central, `sadd` when tying the architecture update to an active spec pack, and `deep-research` only when outside evidence is required.
-
-## Workflow steps
-
-1. Inspect the repo first and derive the current product surfaces, architecture style, module boundaries, technical constraints, and testing strategy from the codebase itself.
-2. Read concrete repo anchors before drafting: root README/manifests, main entrypoints, the primary app roots, existing `docs/specs/`, and representative source folders for each major surface.
-3. Read `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order if they exist.
-4. Update the managed foundation sections in `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md`.
-5. Make `docs/foundation/ARCHITECTURE.md` explicitly state the architecture type in use and include a folder-structure guide for the important apps/packages/directories.
-6. Add or refresh Mermaid diagrams (using fenced ```mermaid blocks with valid syntax) and flow narratives inside `docs/foundation/ARCHITECTURE.md`or`docs/foundation/TECH.md`when they clarify system behavior. Use`sequenceDiagram`for runtime flows and`graph TD`or`C4Context` for structural views.
-7. Ensure `docs/foundation/PRODUCT.md` includes a `## Domain Glossary` defining project-specific terms so future agents use consistent vocabulary.
-8. Ensure `docs/foundation/ARCHITECTURE.md` includes `## Crosscutting Concerns` (logging, auth, error handling patterns), `## Quality Requirements`, and `## Risks And Tech Debt` sections.
-9. Ensure `docs/foundation/TECH.md` includes `## Build And Validation` (exact commands from clean clone to passing CI), `## CI CD Pipeline` (workflow files and triggers), and `## Error Patterns And Debugging` (common errors and resolutions).
-10. Seed or refresh `docs/foundation/adr/README.md` and `docs/foundation/adr/0000-template.md`, and keep ADR linkage explicit when decisions should be durable.
-11. Record whether the update was driven by a broader spec and whether future implementation must follow newly declared structure or product constraints.
-
-## Context notes
-
-- This workflow is route-fixed and skill-fixed: do not start with `route_resolve` or `skill_search`.
-- `docs/foundation/PRODUCT.md` captures intent and domain glossary, `docs/foundation/ARCHITECTURE.md` captures accepted structure and crosscutting concerns, and `docs/foundation/TECH.md` is the developer-facing technical map with build/validation commands. Keep them aligned but not redundant.
-- Favor a lean arc42/C4 style: clear scope, boundaries, building blocks, runtime flows, crosscutting concerns, quality requirements, risks, deployment/testing notes, and only diagrams that add real value.
-- `docs/foundation/ARCHITECTURE.md` should guide future contributors, not just describe the system. Be explicit about architecture style and folder ownership.
-- `docs/foundation/TECH.md` should enable an AI agent to start working immediately: exact build commands, environment setup, error patterns, and validation steps.
-- Prefer stable section headings over ad hoc prose so future refreshes stay clean and easy to diff.
-- All generated markdown must use correct formatting: single H1, proper heading hierarchy, fenced code blocks with language identifiers, valid Mermaid syntax, and tables with header/separator rows.
-- Preserve manual content outside the managed foundation sections.
-- Mark non-applicable sections explicitly instead of silently omitting them.
-- Use relative markdown links between foundation docs: `[ARCHITECTURE.md](docs/foundation/ARCHITECTURE.md)`.
-
-## Verification
-
-- Managed foundation sections exist in the target docs under `docs/foundation/`.
-- Product intent, architecture style, dependency rules, and technical guidance are explicit.
-- `docs/foundation/PRODUCT.md` includes a `## Domain Glossary` with project-specific terms.
-- `docs/foundation/ARCHITECTURE.md` includes `## Crosscutting Concerns`, `## Quality Requirements`, and `## Risks And Tech Debt`.
-- `docs/foundation/ARCHITECTURE.md` or `docs/foundation/TECH.md` includes flow text and at least one Mermaid diagram when the repo has meaningful flow complexity.
-- `docs/foundation/TECH.md` includes `## Build And Validation` with exact commands and `## Error Patterns And Debugging`.
-- All Mermaid diagrams use fenced ```mermaid blocks with valid syntax (no rendering errors).
-- All markdown files use correct heading hierarchy (single H1, no skipped levels).
-- The update records `doc_impact` and whether future feature work must refresh the docs again.
-
-## Output Contract
-
-```yaml
-ARCHITECTURE_WORKFLOW_RESULT:
-  primary_agent: project-planner
-  supporting_agents: [documentation-writer?, researcher?, backend-specialist?, frontend-specialist?, database-architect?]
-  primary_skills: [architecture-doc, system-design, tech-doc, frontend-design]
-  supporting_skills: [api-design?, database-design?, sadd?, deep-research?]
-  managed_targets:
-    product_doc: docs/foundation/PRODUCT.md
-    architecture_doc: docs/foundation/ARCHITECTURE.md
-    tech_doc: docs/foundation/TECH.md
-    adr_dir: docs/foundation/adr
-  files_updated: [docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md]
-  architecture_contract:
-    style: <string>
-    dependency_rules: [<string>]
-    design_system_source: <string>
-    crosscutting_concerns: [<string>]
-    quality_requirements: [<string>]
-    risks_and_tech_debt: [<string>]
-  technical_snapshot:
-    topology: [<string>]
-    flows: [<string>]
-    diagrams: [<string>] | []
-    build_commands: [<string>]
-    error_patterns: [<string>] | []
-  product_glossary: [<string>] | []
-  doc_impact: rules | tech | both
-  next_actions: [<string>] | []
-```
-
-> **Gemini note:** Commands route into workflow files under `.gemini/workflows/`. Specialists are inline postures coordinated through GEMINI.md guidance, not separate agent artifacts.

package/workflows/workflows/agent-environment-setup/platforms/gemini/workflows/backend.md

@@ -1,86 +0,0 @@
----
-command: "/backend"
-description: "Drive backend architecture, API operations, and Postman-oriented execution with API, data, and reliability focus."
-triggers:
-  [
-    "backend",
-    "api",
-    "service",
-    "database",
-    "performance",
-    "postman",
-    "collection",
-    "workspace",
-    "environment",
-    "runcollection",
-    "monitor",
-    "mock",
-    "api test",
-  ]
----
-
-# Backend Workflow
-
-## When to use
-
-Use this for backend architecture, API design, service implementation, or Postman-oriented API operations.
-
-## Routing
-
-- Primary specialist: `the backend-specialist posture`
-- Database support: `the database-architect posture`
-- Security review: `the security-auditor posture`
-- Verification support: `the test-engineer posture`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach API specifications, schema diagrams, Postman collections, and relevant service code.
-- Read `ENGINEERING_RULES.md` and `TECH.md` before changing service boundaries or shared backend structure.
-
-## Skill Routing
-
-- Primary skills: `api-design`, `api-design`, `javascript-best-practices`
-- Supporting skills (optional): `owasp-security-review`, `database-design`, `database-design`, `nestjs`, `fastapi`, `api-design`, `microservices-design`, `drizzle-orm`, `database-design`, `stripe-integration`, `ci-cd-pipeline`, `frontend-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`
-- Start with `api-design` for API contract work and `javascript-best-practices` for Node.js services. Add framework-specific skill when applicable.
-
-## Workflow steps
-
-1. Clarify API contracts and data model requirements.
-2. Design or review schema and service boundaries.
-3. Implement backend logic with proper error handling and validation.
-4. Write integration tests covering happy path and error cases.
-5. Review for security, performance, and reliability.
-6. Set `doc_impact` if the change alters service boundaries, shared contracts, or operational shape.
-
-## Verification
-
-- API contracts match specification.
-- All endpoints have input validation and error handling.
-- Integration tests cover happy path and key error cases.
-- No N+1 queries or unindexed access patterns.
-- Auth applied correctly to protected endpoints.
-
-## Output Contract
-
-```yaml
-BACKEND_WORKFLOW_RESULT:
-  primary_agent: backend-specialist
-  supporting_agents: [database-architect?, security-auditor?, test-engineer?]
-  primary_skills: [api-design, api-design, javascript-best-practices]
-  supporting_skills: [owasp-security-review?, database-design?, <framework-skill>?]
-  api_changes:
-    endpoints_created: [<string>] | []
-    endpoints_modified: [<string>] | []
-    schema_changes: [<string>] | []
-  implementation:
-    files_changed: [<path>]
-    tests_added: [<path>]
-  doc_impact: none | tech | rules | both
-  verification:
-    checks_run: [<command-or-test>]
-    evidence: [<string>]
-  follow_up_items: [<string>] | []
-```
-
-> **Gemini note:** Commands route into workflow files under `.gemini/workflows/`. Specialists are inline postures coordinated through GEMINI.md guidance, not separate agent artifacts.