@cubis/foundry 0.3.82 → 0.3.84

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

@@ -1,79 +0,0 @@
----
-command: "/spec"
-description: "Create or refresh a Git-tracked spec pack for non-trivial work, including acceptance criteria, traceability, architecture impact, and next-route handoff."
-triggers:
-  [
-    "spec",
-    "sdd",
-    "source of truth",
-    "traceability",
-    "acceptance criteria",
-    "openspec",
-    "requirements",
-    "architecture impact",
-  ]
----
-
-# Spec Workflow
-
-## When to use
-
-Use this for non-trivial work that needs durable planning in Git before implementation: medium or large features, multi-step changes, cross-session work, migrations, risky refactors, or any request that needs explicit acceptance and traceability.
-
-## Routing
-
-- Primary coordinator: `@project-planner`
-- Traceability and requirements support: `@researcher`
-- Cross-domain coordination: `@orchestrator`
-- Documentation and structure support: `@documentation-writer`
-
-## Skill Routing
-
-- Primary skills: `spec-driven-delivery`, `sadd`
-- Supporting skills (optional): `system-design`, `architecture-doc`, `deep-research`, `api-design`, `database-design`, `tech-doc`
-- Start with `spec-driven-delivery` for the pack structure and handoff contract. Add `sadd` when mining requirements into testable assertions, `system-design` or `architecture-doc` when the spec changes structure, and `deep-research` only when repo-local evidence is insufficient.
-
-## Workflow steps
-
-1. Determine whether the task is non-trivial enough to justify a spec pack.
-2. Find an existing `docs/specs/<spec-id>/` pack or create a new stable `spec_id`.
-3. Write or refresh the spec pack with brief, acceptance, tasks, traceability, and handoff files.
-4. Record `architecture_impact`, `doc_impact`, and any required updates to `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, `ENGINEERING_RULES.md`, or `docs/foundation/TECH.md`. If the change adds new terms, update the `## Domain Glossary` in `docs/foundation/PRODUCT.md`. If the change introduces new crosscutting patterns or tech debt, flag updates needed in `docs/foundation/ARCHITECTURE.md`.
-5. Identify the next execution route and hand off without replanning the same work.
-
-## Context notes
-
-- Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist because they define the accepted product direction, architecture contract, and current state.
-- Prefer repo evidence first; escalate to `deep-research` only when freshness, public comparison, or explicit research requests require it.
-- Keep spec packs lean. Trivial one-step tasks should stay on the lightweight path with no new spec directory.
-
-## Verification
-
-- `spec_id` and `spec_root` are stable and explicit.
-- Acceptance criteria are testable and traceable.
-- Task dependencies form a valid execution order.
-- `architecture_impact`, `doc_impact`, and `traceability_status` are present.
-
-## Output Contract
-
-```yaml
-SPEC_WORKFLOW_RESULT:
-  primary_agent: project-planner
-  supporting_agents: [researcher?, orchestrator?, documentation-writer?]
-  primary_skills: [spec-driven-delivery, sadd]
-  supporting_skills: [system-design?, architecture-doc?, deep-research?, api-design?, database-design?, tech-doc?]
-  spec_id: <string>
-  spec_root: docs/specs/<spec-id>
-  architecture_impact:
-    summary: <string>
-    affects_structure: true | false
-    affects_design_system: true | false
-    affects_testing_strategy: true | false
-  doc_impact: none | tech | rules | both
-  traceability_status: complete | partial | blocked
-  documents:
-    created: [<path>] | []
-    updated: [<path>] | []
-  next_route: </create | /implement-track | /orchestrate | /architecture | direct>
-  gaps: [<string>] | []
-```

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

@@ -1,64 +0,0 @@
----
-command: "/test"
-description: "Design and execute verification strategy aligned to user risk, release confidence, and regression evidence."
-triggers: ["test", "verify", "coverage", "qa", "regression"]
----
-
-# Test Workflow
-
-## When to use
-
-Use this when writing new tests, improving coverage, debugging test failures, or designing a testing strategy.
-
-## Routing
-
-- Primary specialist: `@test-engineer`
-- Automation support: `@qa-automation-engineer`
-- Domain support: `@backend-specialist`, `@frontend-specialist`
-- Verification support: `@validator`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the code under test, existing test files, coverage reports, and any failing test output.
-
-## Skill Routing
-
-- Primary skills: `unit-testing`, `integration-testing`
-- Supporting skills (optional): `playwright-interactive`, `observability`, `systematic-debugging`, `code-review`, `code-review`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`
-- Start with `unit-testing` for test strategy and architecture. Add `integration-testing` for implementation. Add `playwright-interactive` for E2E automation. Add `observability` for testing error states.
-
-## Workflow steps
-
-1. Assess current test coverage and identify gaps.
-2. Design test strategy (which layers, what to test, what to skip).
-3. Implement tests with clear arrange/act/assert structure.
-4. Run tests and verify they pass.
-5. Review coverage improvement and remaining gaps.
-
-## Verification
-
-- All new tests pass reliably (no flakiness).
-- Tests cover the identified risk areas.
-- Coverage metrics improved or maintained.
-- Test naming clearly describes the scenario being verified.
-
-## Output Contract
-
-```yaml
-TEST_WORKFLOW_RESULT:
-  primary_agent: test-engineer
-  supporting_agents: [qa-automation-engineer?, backend-specialist?, frontend-specialist?, validator?]
-  primary_skills: [unit-testing, integration-testing]
-  supporting_skills: [playwright-interactive?, observability?, systematic-debugging?]
-  test_strategy:
-    unit: <number of tests>
-    integration: <number of tests>
-    e2e: <number of tests>
-  tests_written: [<test-file-path>]
-  coverage:
-    before: <percentage or description>
-    after: <percentage or description>
-  gaps_remaining: [<string>] | []
-  follow_up_items: [<string>] | []
-```

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

@@ -1,74 +0,0 @@
----
-command: "/vercel"
-description: "Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails."
-triggers:
-  [
-    "vercel",
-    "deployment",
-    "preview",
-    "edge",
-    "functions",
-    "domains",
-    "vercel cli",
-  ]
----
-
-# Vercel Workflow
-
-## When to use
-
-Use this for Vercel-specific deployment, configuration, runtime optimization, or platform operations.
-
-## Routing
-
-- Primary specialist: `@vercel-expert`
-- Infrastructure support: `@ci-cd-pipeline`
-- Verification support: `@test-engineer`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the Vercel project config, deployment target, and any specific Vercel feature requirements.
-
-## Skill Routing
-
-- Primary skills: `nextjs`, `ci-cd-pipeline`
-- Supporting skills (optional): `performance-testing`, `react`, `frontend-design`, `javascript-best-practices`, `typescript-best-practices`, `javascript-best-practices`
-- Start with `nextjs` for Next.js on Vercel and `ci-cd-pipeline` for runtime behavior. Add `performance-testing` for performance optimization.
-
-## Workflow steps
-
-1. Assess deployment requirements and runtime selection (Edge vs Serverless vs Static).
-2. Configure project settings and environment variables.
-3. Set up deployment pipeline with preview deployments.
-4. Verify deployment health and performance.
-5. Configure monitoring and alerting.
-
-## Verification
-
-- Deployment successful with no build errors.
-- Runtime selection appropriate for each route.
-- Environment variables correctly configured per environment.
-- Preview deployments working for PRs.
-- Performance metrics within acceptable ranges.
-
-## Output Contract
-
-```yaml
-VERCEL_WORKFLOW_RESULT:
-  primary_agent: vercel-expert
-  supporting_agents: [ci-cd-pipeline?, test-engineer?]
-  primary_skills: [nextjs, ci-cd-pipeline]
-  supporting_skills: [performance-testing?, react?]
-  deployment:
-    project: <string>
-    runtime: <edge | serverless | static>
-    environment: <development | preview | production>
-    status: success | failure
-  configuration:
-    env_vars: [<string>]
-    domains: [<string>]
-    caching: <string>
-  monitoring: <string>
-  follow_up_items: [<string>] | []
-```

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

@@ -1,19 +0,0 @@
-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.
-
-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`.
-- 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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-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."
-prompt = '''
-Follow the /architecture workflow from .gemini/workflows/architecture.md.
-
-Execution contract:
-1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.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: `architecture-doc`, `system-design`, `tech-doc`, `frontend-design`, `api-design`, `database-design`, `sadd`, `deep-research`.
-- Local skill file hints if installed: `.gemini/skills/architecture-doc/SKILL.md`, `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/tech-doc/SKILL.md`, `.gemini/skills/frontend-design/SKILL.md`, `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/sadd/SKILL.md`, `.gemini/skills/deep-research/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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Drive backend architecture, API operations, and Postman-oriented execution with API, data, and reliability focus."
-prompt = '''
-Follow the /backend workflow from .gemini/workflows/backend.md.
-
-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: `api-design`, `javascript-best-practices`, `owasp-security-review`, `database-design`, `nestjs`, `fastapi`, `microservices-design`, `drizzle-orm`, `stripe-integration`, `ci-cd-pipeline`, `frontend-design`, `typescript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/owasp-security-review/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/nestjs/SKILL.md`, `.gemini/skills/fastapi/SKILL.md`, `.gemini/skills/microservices-design/SKILL.md`, `.gemini/skills/drizzle-orm/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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Implement feature work with minimal blast radius and clear verification checkpoints."
-prompt = '''
-Follow the /create workflow from .gemini/workflows/create.md.
-
-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: `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `php-best-practices`, `expo-app`, `swift-best-practices`, `api-design`, `nestjs`, `fastapi`, `drizzle-orm`, `database-design`, `mcp-server-builder`, `stitch`, `react`, `nextjs`, `frontend-design`, `performance-testing`, `skill-creator`, `stripe-integration`, `ci-cd-pipeline`.
-- Local skill file hints if installed: `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`, `.gemini/skills/java-best-practices/SKILL.md`, `.gemini/skills/csharp-best-practices/SKILL.md`, `.gemini/skills/kotlin-best-practices/SKILL.md`, `.gemini/skills/rust-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Design or review schema, queries, and migrations with performance and integrity controls."
-prompt = '''
-Follow the /database workflow from .gemini/workflows/database.md.
-
-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: `database-design`, `drizzle-orm`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/drizzle-orm/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Plan and execute deployment, CI/CD, incident response, and operational safety changes with rollback controls."
-prompt = '''
-Follow the /devops workflow from .gemini/workflows/devops.md.
-
-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: `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: `.gemini/skills/ci-cd-pipeline/SKILL.md`, `.gemini/skills/kubernetes-deploy/SKILL.md`, `.gemini/skills/observability/SKILL.md`, `.gemini/skills/git-workflow/SKILL.md`, `.gemini/skills/systematic-debugging/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Execute large work in milestones with explicit quality gates and status updates."
-prompt = '''
-Follow the /implement-track workflow from .gemini/workflows/implement-track.md.
-
-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: `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: `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`, `.gemini/skills/react/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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Plan and execute technology migrations, framework upgrades, and dependency updates with rollback safety, incremental verification, and zero-downtime transition."
-prompt = '''
-Follow the /migrate workflow from .gemini/workflows/migrate.md.
-
-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: `system-design`, `code-review`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/code-review/SKILL.md`, `.gemini/skills/unit-testing/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability."
-prompt = '''
-Follow the /mobile workflow from .gemini/workflows/mobile.md.
-
-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: `expo-app`, `react-native`, `stitch`, `frontend-design`, `swift-best-practices`, `kotlin-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/expo-app/SKILL.md`, `.gemini/skills/react-native/SKILL.md`, `.gemini/skills/stitch/SKILL.md`, `.gemini/skills/frontend-design/SKILL.md`, `.gemini/skills/swift-best-practices/SKILL.md`, `.gemini/skills/kotlin-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Survey an unfamiliar codebase, map its architecture, identify patterns and conventions, and produce a structured orientation report for new contributors."
-prompt = '''
-Follow the /onboard workflow from .gemini/workflows/onboard.md.
-
-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: `deep-research`, `system-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/deep-research/SKILL.md`, `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership, validation gates, and repeat-until-good iteration."
-prompt = '''
-Follow the /orchestrate workflow from .gemini/workflows/orchestrate.md.
-
-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: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
-- Local skill file hints if installed: `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/deep-research/SKILL.md`, `.gemini/skills/mcp-server-builder/SKILL.md`, `.gemini/skills/tech-doc/SKILL.md`, `.gemini/skills/prompt-engineering/SKILL.md`, `.gemini/skills/skill-creator/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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Improve maintainability while preserving behavior through incremental safe refactoring."
-prompt = '''
-Follow the /refactor workflow from .gemini/workflows/refactor.md.
-
-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`, `system-design`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/code-review/SKILL.md`, `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/unit-testing/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Prepare and execute release with rollout guardrails, verification, and rollback plan."
-prompt = '''
-Follow the /release workflow from .gemini/workflows/release.md.
-
-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: `ci-cd-pipeline`, `git-workflow`, `tech-doc`, `observability`, `kubernetes-deploy`, `typescript-best-practices`, `javascript-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/ci-cd-pipeline/SKILL.md`, `.gemini/skills/git-workflow/SKILL.md`, `.gemini/skills/tech-doc/SKILL.md`, `.gemini/skills/observability/SKILL.md`, `.gemini/skills/kubernetes-deploy/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Run security-focused analysis and remediation planning with exploitability-first triage."
-prompt = '''
-Follow the /security workflow from .gemini/workflows/security.md.
-
-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: `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: `.gemini/skills/owasp-security-review/SKILL.md`, `.gemini/skills/code-review/SKILL.md`, `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/typescript-best-practices/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/python-best-practices/SKILL.md`, `.gemini/skills/golang-best-practices/SKILL.md`, `.gemini/skills/rust-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Create or refresh a Git-tracked spec pack for non-trivial work, including acceptance criteria, traceability, architecture impact, and next-route handoff."
-prompt = '''
-Follow the /spec workflow from .gemini/workflows/spec.md.
-
-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: `spec-driven-delivery`, `sadd`, `system-design`, `architecture-doc`, `deep-research`, `api-design`, `database-design`, `tech-doc`.
-- Local skill file hints if installed: `.gemini/skills/spec-driven-delivery/SKILL.md`, `.gemini/skills/sadd/SKILL.md`, `.gemini/skills/system-design/SKILL.md`, `.gemini/skills/architecture-doc/SKILL.md`, `.gemini/skills/deep-research/SKILL.md`, `.gemini/skills/api-design/SKILL.md`, `.gemini/skills/database-design/SKILL.md`, `.gemini/skills/tech-doc/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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

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

@@ -1,19 +0,0 @@
-description = "Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails."
-prompt = '''
-Follow the /vercel workflow from .gemini/workflows/vercel.md.
-
-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: `nextjs`, `ci-cd-pipeline`, `performance-testing`, `react`, `frontend-design`, `javascript-best-practices`, `typescript-best-practices`.
-- Local skill file hints if installed: `.gemini/skills/nextjs/SKILL.md`, `.gemini/skills/ci-cd-pipeline/SKILL.md`, `.gemini/skills/performance-testing/SKILL.md`, `.gemini/skills/react/SKILL.md`, `.gemini/skills/frontend-design/SKILL.md`, `.gemini/skills/javascript-best-practices/SKILL.md`, `.gemini/skills/typescript-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.
-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.
-7. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
-
-If command arguments are provided, treat them as additional user context.
-'''

package/workflows/workflows/agent-environment-setup/platforms/gemini/skills/api-design/evals/assertions.md

@@ -1,53 +0,0 @@
-# API Design Eval Assertions
-
-## Eval 1: REST API Contract Design
-
-This eval tests the ability to design a RESTful API with proper resource modeling, HTTP semantics, pagination, error handling, and OpenAPI documentation for a task management system.
-
-### Assertions
-
-| # | Type | What it checks | Why it matters |
-|---|------|----------------|----------------|
-| 1 | contains | `GET` — Proper HTTP method usage | REST APIs must use HTTP methods with their standardized semantics. GET for safe retrieval enables caching and is idempotent. Using POST for reads breaks HTTP semantics and cache layers. |
-| 2 | contains | `cursor` — Cursor-based pagination | Offset pagination breaks when data changes between requests (duplicates, skipped items). Cursor-based pagination provides stable pages regardless of concurrent writes. |
-| 3 | contains | `application/problem+json` — RFC 9457 error format | Ad-hoc error formats require custom parsing per API. Problem Details provides a standardized structure that clients can handle generically while still including API-specific detail fields. |
-| 4 | contains | `openapi` — OpenAPI specification | A spec-first approach ensures documentation is always synchronized with implementation. OpenAPI enables code generation, testing, and SDK creation from a single source of truth. |
-| 5 | contains | `filter` — Collection filtering support | Clients must be able to retrieve subsets of collections without downloading everything. Query parameter filters reduce payload size, database load, and client-side processing. |
-
-### What a passing response looks like
-
-- Resource hierarchy: `/v1/workspaces/{id}/projects/{id}/tasks/{id}/comments/{id}`.
-- GET (list with filters), GET (by ID), POST (create), PATCH (partial update), DELETE for each resource.
-- Cursor-based pagination: `?cursor=eyJpZCI6MTIzfQ&limit=25` with `next_cursor` in response.
-- Filtering: `?status=in_progress&priority=high&assignee=user_123&due_before=2025-12-31`.
-- Error responses with `application/problem+json` content type, including `type` URI, `title`, `status`, `detail`, and `errors` array for validation failures.
-- OpenAPI 3.1 spec with `info`, `paths`, `components/schemas`, and `examples`.
-- Standard response envelope or direct resource representation with consistent field naming (camelCase).
-- Rate limit headers: `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset`.
-
----
-
-## Eval 2: GraphQL Schema Design
-
-This eval tests the ability to design a GraphQL schema with Relay-style pagination, input types, union-based error handling, and DataLoader for N+1 prevention in a social content platform.
-
-### Assertions
-
-| # | Type | What it checks | Why it matters |
-|---|------|----------------|----------------|
-| 1 | contains | `Connection` — Relay-style pagination types | Relay connections provide a standardized cursor-based pagination contract that works with any GraphQL client. Custom pagination reinvents a solved problem and breaks client library expectations. |
-| 2 | contains | `input` — Dedicated mutation input types | Input types encapsulate mutation arguments into a single typed object, enabling validation, documentation, and future field additions without breaking existing mutations. |
-| 3 | contains | `DataLoader` — N+1 query prevention | Without DataLoader, resolving a list of posts with their authors generates N+1 database queries. DataLoader batches and deduplicates loader calls within a single request. |
-| 4 | contains | `union` — Union types for error modeling | Returning errors in the data layer (union of success and error types) gives clients type-safe error handling. Throwing exceptions forces clients to parse untyped error extensions. |
-| 5 | contains | `visibility` — Authorization in resolvers | Post visibility (public, followers, private) must be enforced in resolvers, not just in the client. Missing server-side authorization means private content is accessible via direct GraphQL queries. |
-
-### What a passing response looks like
-
-- Types: `User`, `Post`, `Comment`, `Reaction`, `MediaAttachment`, `Tag`.
-- Connection types: `PostConnection { edges: [PostEdge], pageInfo: PageInfo }` with `PostEdge { cursor, node }`.
-- Input types: `CreatePostInput { content, mediaIds, tagIds, visibility }`, `UpdatePostInput { content?, visibility? }`.
-- Union result types: `CreatePostResult = Post | ValidationError | AuthorizationError`.
-- Visibility enum: `enum PostVisibility { PUBLIC, FOLLOWERS, PRIVATE }`.
-- Feed query with DataLoader for batch-loading authors, reaction counts, and comment counts.
-- Resolver architecture: per-type DataLoaders instantiated per-request to avoid cross-request caching.
-- Subscription type for real-time updates: `onNewComment(postId: ID!): Comment`.