@cubis/foundry 0.3.81 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/test.toml

@@ -1,19 +1,81 @@
 description = "Design and execute verification strategy aligned to user risk, release confidence, and regression evidence."
 prompt = '''
-Follow the /test workflow from .agent/workflows/test.md.
+Execute the native projection of the /test workflow.
+
+Design and execute verification strategy aligned to user risk, release confidence, and regression evidence.
 
 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: `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: `.agent/skills/unit-testing/SKILL.md`, `.agent/skills/integration-testing/SKILL.md`, `.agent/skills/playwright-interactive/SKILL.md`, `.agent/skills/observability/SKILL.md`, `.agent/skills/systematic-debugging/SKILL.md`, `.agent/skills/code-review/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/unit-testing/SKILL.md`, `.agents/skills/integration-testing/SKILL.md`, `.agents/skills/playwright-interactive/SKILL.md`, `.agents/skills/observability/SKILL.md`, `.agents/skills/systematic-debugging/SKILL.md`, `.agents/skills/code-review/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 hand off to `@researcher` 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:
+# 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: `testing-patterns`, `webapp-testing`
+- Supporting skills (optional): `playwright-e2e`, `error-ux-observability`, `debugging-strategies`, `frontend-code-review`, `static-analysis`, `typescript-pro`, `javascript-pro`, `python-pro`, `golang-pro`, `java-pro`
+- Start with `testing-patterns` for test strategy and architecture. Add `webapp-testing` for implementation. Add `playwright-e2e` for E2E automation. Add `error-ux-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: [testing-patterns, webapp-testing]
+  supporting_skills: [playwright-e2e?, error-ux-observability?, debugging-strategies?]
+  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>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -1,19 +1,82 @@
 description = "Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails."
 prompt = '''
-Follow the /vercel workflow from .agent/workflows/vercel.md.
+Execute the native projection of the /vercel workflow.
+
+Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails.
 
 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: `.agent/skills/nextjs/SKILL.md`, `.agent/skills/ci-cd-pipeline/SKILL.md`, `.agent/skills/performance-testing/SKILL.md`, `.agent/skills/react/SKILL.md`, `.agent/skills/frontend-design/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`.
+- Local skill file hints if installed: `.agents/skills/nextjs/SKILL.md`, `.agents/skills/ci-cd-pipeline/SKILL.md`, `.agents/skills/performance-testing/SKILL.md`, `.agents/skills/react/SKILL.md`, `.agents/skills/frontend-design/SKILL.md`, `.agents/skills/javascript-best-practices/SKILL.md`, `.agents/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.
+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 hand off to `@researcher` 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:
+# Vercel Workflow
+
+## When to use
+
+Use this for Vercel-specific deployment, configuration, runtime optimization, or platform operations.
+
+## Routing
+
+- Primary specialist: `@vercel-expert`
+- Infrastructure support: `@devops-engineer`
+- 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-developer`, `serverless-patterns`
+- Supporting skills (optional): `web-perf`, `react-expert`, `tailwind-patterns`, `nodejs-best-practices`, `typescript-pro`, `javascript-pro`
+- Start with `nextjs-developer` for Next.js on Vercel and `serverless-patterns` for runtime behavior. Add `web-perf` 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: [devops-engineer?, test-engineer?]
+  primary_skills: [nextjs-developer, serverless-patterns]
+  supporting_skills: [web-perf?, react-expert?]
+  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>] | []
+```
+
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/rules/GEMINI.md

@@ -28,11 +28,9 @@ If any check fails, restart your reasoning.
 
 | Asset           | Location                 |
 | --------------- | ------------------------ |
-| Workflows       | `.agent/workflows`       |
-| Agents          | `.agent/agents`          |
-| Skills          | `.agent/skills`          |
+| Skills          | `.agents/skills`         |
 | Gemini commands | `.gemini/commands`       |
-| Rules file      | `.agent/rules/GEMINI.md` |
+| Rules file      | `.agents/rules/GEMINI.md` |
 
 ---
 
@@ -75,16 +73,16 @@ Execute this tree top-to-bottom. Stop at the **first match**. Never skip levels.
 
 ## 3) Layer Reference
 
-| Layer              | What it is                   | When to invoke                        | How                                |
-| ------------------ | ---------------------------- | ------------------------------------- | ---------------------------------- |
-| **Direct**         | Zero routing                 | Trivial, single-step, obvious tasks   | Just do it                         |
-| **Gemini command** | Platform-native command      | Task matches installed command        | `.gemini/commands/*.toml`          |
-| **Workflow**       | Structured multi-step recipe | Known pattern, repeatable process     | `/plan`, `/create`, `/debug`, etc. |
-| **Agent**          | Specialist persona + context | Domain depth or parallel workstream   | `@specialist` reference            |
-| **Skill (MCP)**    | Focused knowledge module     | Domain context after route is set     | `skill_validate` → `skill_get`     |
-| **skill_search**   | Fuzzy skill discovery        | Domain unclear after route_resolve    | One narrow call only               |
-| **route_resolve**  | Intent → route mapping       | Free-text intent doesn't match        | MCP tool call                      |
-| **Orchestrator**   | Multi-specialist coordinator | Work crosses 2+ domains with handoffs | `@orchestrator` or Agent Manager   |
+| Layer              | What it is                      | When to invoke                        | How                                |
+| ------------------ | ------------------------------- | ------------------------------------- | ---------------------------------- |
+| **Direct**         | Zero routing                    | Trivial, single-step, obvious tasks   | Just do it                         |
+| **Gemini command** | Platform-native command         | Task matches installed command        | `.gemini/commands/*.toml`          |
+| **Workflow route** | Structured recipe projected to command | Known pattern, repeatable process | `/plan`, `/create`, `/debug`, etc. |
+| **Agent route**    | Specialist route projected to command | Domain depth or parallel workstream | `@specialist` via command/rule flow |
+| **Skill (MCP)**    | Focused knowledge module        | Domain context after route is set     | `skill_validate` → `skill_get`     |
+| **skill_search**   | Fuzzy skill discovery           | Domain unclear after route_resolve    | One narrow call only               |
+| **route_resolve**  | Intent → route mapping          | Free-text intent doesn't match        | MCP tool call                      |
+| **Orchestrator**   | Multi-specialist coordinator    | Work crosses 2+ domains with handoffs | `@orchestrator` or Agent Manager   |
 
 ---
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/api-design/SKILL.md

@@ -77,8 +77,11 @@ Load only what the current task requires.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/architecture-doc/SKILL.md

@@ -72,8 +72,11 @@ Load on demand. Do not preload all reference files.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/ci-cd-pipeline/SKILL.md

@@ -67,8 +67,11 @@ Provide complete pipeline configuration files with inline comments explaining no
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

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

@@ -61,8 +61,11 @@ When conducting a code review, provide:
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/csharp-best-practices/SKILL.md

@@ -76,8 +76,11 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/database-design/SKILL.md

@@ -70,8 +70,11 @@ Load on demand. Do not preload all reference files.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/deep-research/SKILL.md

@@ -82,8 +82,11 @@ Use these when the task shape already matches.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/django-drf/SKILL.md

@@ -61,8 +61,11 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/docker-compose-dev/SKILL.md

@@ -67,8 +67,11 @@ Provide complete `docker-compose.yml` and `Dockerfile` content with inline comme
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/drizzle-orm/SKILL.md

@@ -74,8 +74,11 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/electron-qa/SKILL.md

@@ -80,8 +80,11 @@ Deliver:
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/expo-app/SKILL.md

@@ -86,8 +86,11 @@ Guide the design and implementation of production-grade Expo applications using
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/express-nodejs/SKILL.md

@@ -73,8 +73,11 @@ Load only what the current step needs.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/fastapi/SKILL.md

@@ -67,8 +67,11 @@ Provide implementation code, Pydantic model definitions, dependency functions, c
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/frontend-design/SKILL.md

@@ -84,8 +84,11 @@ Load only what the current task requires.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/gin-golang/SKILL.md

@@ -69,8 +69,11 @@ Load only what the current step needs.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/git-workflow/SKILL.md

@@ -61,8 +61,11 @@ When advising on git workflows, provide:
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/go-fiber/SKILL.md

@@ -69,8 +69,11 @@ Load only what the current step needs.
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/golang-best-practices/SKILL.md

@@ -72,8 +72,11 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 ## Antigravity Platform Notes
 
-- Use Agent Manager for parallel agent coordination and task delegation.
-- Skill and agent files are stored under `.agent/skills/` and `.agent/agents/` respectively.
-- TOML command files in `.agent/commands/` provide slash-command entry points for workflows.
-- Replace direct `@agent-name` delegation with Agent Manager dispatch calls.
-- Reference files are loaded relative to the skill directory under `.agent/skills/<skill-id>/`.
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file: `.agents/rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.