@cubis/foundry 0.3.76 → 0.3.78

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

@@ -4,9 +4,16 @@ Follow the /backend workflow from .agent/workflows/backend.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/api-design/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/owasp-security-review/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/nestjs/SKILL.md`, `.agent/skills/fastapi/SKILL.md`, `.agent/skills/microservices-design/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/create.toml

@@ -4,9 +4,16 @@ Follow the /create workflow from .agent/workflows/create.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/skills/golang-best-practices/SKILL.md`, `.agent/skills/java-best-practices/SKILL.md`, `.agent/skills/csharp-best-practices/SKILL.md`, `.agent/skills/kotlin-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/database.toml

@@ -4,9 +4,16 @@ Follow the /database workflow from .agent/workflows/database.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/database-design/SKILL.md`, `.agent/skills/drizzle-orm/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/debug.toml

@@ -4,9 +4,16 @@ Follow the /debug workflow from .agent/workflows/debug.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/systematic-debugging/SKILL.md`, `.agent/skills/observability/SKILL.md`, `.agent/skills/unit-testing/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/skills/golang-best-practices/SKILL.md`, `.agent/skills/java-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 hand off to `@researcher` 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/antigravity/commands/devops.toml

@@ -4,9 +4,16 @@ Follow the /devops workflow from .agent/workflows/devops.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/ci-cd-pipeline/SKILL.md`, `.agent/skills/kubernetes-deploy/SKILL.md`, `.agent/skills/observability/SKILL.md`, `.agent/skills/git-workflow/SKILL.md`, `.agent/skills/systematic-debugging/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/implement-track.toml

@@ -4,9 +4,16 @@ Follow the /implement-track workflow from .agent/workflows/implement-track.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/system-design/SKILL.md`, `.agent/skills/api-design/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/skills/golang-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/migrate.toml

@@ -4,9 +4,16 @@ Follow the /migrate workflow from .agent/workflows/migrate.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/system-design/SKILL.md`, `.agent/skills/code-review/SKILL.md`, `.agent/skills/unit-testing/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/mobile.toml

@@ -4,9 +4,16 @@ Follow the /mobile workflow from .agent/workflows/mobile.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/expo-app/SKILL.md`, `.agent/skills/react-native/SKILL.md`, `.agent/skills/stitch/SKILL.md`, `.agent/skills/frontend-design/SKILL.md`, `.agent/skills/swift-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/onboard.toml

@@ -4,9 +4,16 @@ Follow the /onboard workflow from .agent/workflows/onboard.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/deep-research/SKILL.md`, `.agent/skills/system-design/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/orchestrate.toml

@@ -4,9 +4,16 @@ Follow the /orchestrate workflow from .agent/workflows/orchestrate.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/system-design/SKILL.md`, `.agent/skills/api-design/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/deep-research/SKILL.md`, `.agent/skills/mcp-server-builder/SKILL.md`, `.agent/skills/tech-doc/SKILL.md`, `.agent/skills/prompt-engineering/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/plan.toml

@@ -4,9 +4,16 @@ Follow the /plan workflow from .agent/workflows/plan.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/system-design/SKILL.md`, `.agent/skills/api-design/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/skills/deep-research/SKILL.md`, `.agent/skills/mcp-server-builder/SKILL.md`, `.agent/skills/tech-doc/SKILL.md`, `.agent/skills/prompt-engineering/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/refactor.toml

@@ -4,9 +4,16 @@ Follow the /refactor workflow from .agent/workflows/refactor.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/code-review/SKILL.md`, `.agent/skills/system-design/SKILL.md`, `.agent/skills/unit-testing/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/release.toml

@@ -4,9 +4,16 @@ Follow the /release workflow from .agent/workflows/release.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/ci-cd-pipeline/SKILL.md`, `.agent/skills/git-workflow/SKILL.md`, `.agent/skills/tech-doc/SKILL.md`, `.agent/skills/observability/SKILL.md`, `.agent/skills/kubernetes-deploy/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/review.toml

@@ -4,9 +4,16 @@ Follow the /review workflow from .agent/workflows/review.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/code-review/SKILL.md`, `.agent/skills/unit-testing/SKILL.md`, `.agent/skills/owasp-security-review/SKILL.md`, `.agent/skills/performance-testing/SKILL.md`, `.agent/skills/react/SKILL.md`, `.agent/skills/nextjs/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/security.toml

@@ -4,9 +4,16 @@ Follow the /security workflow from .agent/workflows/security.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/owasp-security-review/SKILL.md`, `.agent/skills/code-review/SKILL.md`, `.agent/skills/api-design/SKILL.md`, `.agent/skills/typescript-best-practices/SKILL.md`, `.agent/skills/javascript-best-practices/SKILL.md`, `.agent/skills/python-best-practices/SKILL.md`, `.agent/skills/golang-best-practices/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/spec.toml

@@ -0,0 +1,19 @@
+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 .agent/workflows/spec.md.
+
+Execution contract:
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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: `.agent/skills/spec-driven-delivery/SKILL.md`, `.agent/skills/sadd/SKILL.md`, `.agent/skills/system-design/SKILL.md`, `.agent/skills/architecture-doc/SKILL.md`, `.agent/skills/deep-research/SKILL.md`, `.agent/skills/api-design/SKILL.md`, `.agent/skills/database-design/SKILL.md`, `.agent/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 hand off to `@researcher` 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/antigravity/commands/test.toml

@@ -4,9 +4,16 @@ Follow the /test workflow from .agent/workflows/test.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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`.
+- 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 hand off to `@researcher` 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/antigravity/commands/vercel.toml

@@ -4,9 +4,16 @@ Follow the /vercel workflow from .agent/workflows/vercel.md.
 
 Execution contract:
 1. Treat route selection as already resolved by this command; do not begin with skill discovery.
-2. Confirm the request fits the workflow's "When to use" section.
-3. Execute according to "Workflow steps" and apply "Context notes".
-4. Complete "Verification" checks and report concrete evidence.
+2. Read `ENGINEERING_RULES.md` first and `TECH.md` next 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`.
+- 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 hand off to `@researcher` 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/antigravity/rules/GEMINI.md

@@ -46,7 +46,7 @@ Execute this tree top-to-bottom. Stop at the **first match**. Never skip levels.
 ├─ [TRIVIAL] Single-step, obvious, reversible?
 │   → Execute directly. No routing. Stop.
 │
-├─ [EXPLICIT] User named a Gemini command, workflow, or @agent?
+├─ [EXPLICIT] User named a Gemini command, workflow, @agent, or exact skill?
 │   → Honor that route exactly. Stop.
 │
 ├─ [SINGLE-DOMAIN] Multi-step but contained in one specialty?
@@ -66,6 +66,7 @@ Execute this tree top-to-bottom. Stop at the **first match**. Never skip levels.
 **Hard rules:**
 
 - Never pre-load skills before route resolution.
+- If the user names an exact skill ID, run `skill_validate` on that ID before `route_resolve`.
 - Never invoke an agent when direct execution suffices.
 - Never chain more than one `skill_search` per request.
 - Treat this file as **durable project memory** — not a per-task playbook.
@@ -360,6 +361,7 @@ Use this matrix to match incoming tasks to the correct skill and primary agent.
 | docker-compose-dev | DevOps | Docker Compose local dev environments | @devops-engineer |
 | kubernetes-deploy | DevOps | K8s manifests, Helm charts, deployment | @devops-engineer |
 | observability | DevOps | Logging, metrics, tracing, alerting | @devops-engineer |
+| deep-research | Research | Latest docs, public comparisons, external verification | @researcher |
 | llm-eval | AI/ML | LLM evaluation, benchmarking, evals | @researcher |
 | rag-patterns | AI/ML | RAG architecture, embeddings, retrieval | @researcher |
 | prompt-engineering | AI/ML | Prompt design, few-shot, chain-of-thought | @researcher |
@@ -407,12 +409,17 @@ Selection policy:
 Keep MCP context lazy and exact. Skills are supporting context, not the route layer.
 
 1. Never begin with `skill_search`. Inspect the repo/task locally first.
-2. Resolve workflows, agents, or free-text route intent with `route_resolve` before loading any skills.
-3. If the route is still unresolved and local grounding leaves the domain unclear, use one narrow `skill_search`.
-4. Always run `skill_validate` on the exact selected ID before `skill_get`.
-5. Call `skill_get` with `includeReferences:false` by default.
-6. Load at most one sidecar markdown file at a time with `skill_get_reference`.
-7. Do not auto-prime every specialist with a skill. Load only what the task clearly needs.
-8. Use upstream MCP servers such as `postman`, `stitch`, or `playwright` for real cloud/browser actions when available.
+2. If the user already named `/workflow`, `@agent`, or an exact skill ID, honor it directly. For exact skills, run `skill_validate` first and skip `route_resolve` when valid.
+3. Resolve only free-text workflow/agent intent with `route_resolve` before loading non-explicit skills.
+4. If the route is still unresolved and local grounding leaves the domain unclear, use one narrow `skill_search`.
+5. Always run `skill_validate` on the exact selected ID before `skill_get`.
+6. Call `skill_get` with `includeReferences:false` by default.
+7. Load at most one sidecar markdown file at a time with `skill_get_reference`.
+8. Do not auto-prime every specialist with a skill. Load only what the task clearly needs.
+9. For research: repo/local evidence first, official docs next, Reddit/community only as labeled secondary evidence.
+10. Escalate to research only when freshness matters, public comparison matters, or the user explicitly asks to research/verify.
+11. For non-trivial work, read `ENGINEERING_RULES.md` first and `TECH.md` next when they exist.
+12. If those docs declare architecture or design-system rules, follow them unless the current spec or task explicitly changes them.
+13. Use upstream MCP servers such as `postman`, `stitch`, or `playwright` for real cloud/browser actions when available.
 
 <!-- cbx:mcp:auto:end -->

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

@@ -0,0 +1,89 @@
+---
+name: deep-research
+description: Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.
+---
+# Deep Research
+
+## Purpose
+
+Run a disciplined research pass before implementation when the repo alone is not enough. This skill keeps research evidence-driven: inspect the local codebase first, escalate to official docs when freshness or public comparison matters, then use labeled community evidence only when it adds practical context.
+
+## When to Use
+
+- Verifying latest SDK, CLI, API, or platform behavior
+- Comparing tools, frameworks, hosted services, or implementation approaches
+- Checking whether public docs and the local repo disagree
+- Gathering external evidence before planning a migration or new capability
+- Producing a structured research brief that hands off cleanly into implementation
+
+## Instructions
+
+1. **Define the research question before collecting sources** because vague research sprawls quickly. Restate the target topic, freshness requirement, comparison axis, and what decision the findings need to support.
+
+2. **Inspect the repo first** because many questions are already answerable from local code, configs, tests, docs, or generated assets. Do not browse externally until the local evidence is exhausted or clearly insufficient.
+
+3. **Decide whether external research is actually required** because not every task needs web evidence. Escalate only when freshness matters, public comparison matters, or the user explicitly asks to research or verify.
+
+4. **Follow the source ladder strictly** because evidence quality matters. Use official docs, upstream repositories, standards, and maintainer material as primary sources before looking at blogs, issue threads, or Reddit.
+
+5. **Capture concrete source details** because research without provenance is hard to trust. Record exact links, relevant dates, versions, and any repo files that support or contradict the external evidence.
+
+6. **Cross-check important claims across more than one source when possible** because public docs, repos, and community advice can drift. If sources disagree, say so explicitly instead of smoothing over the conflict.
+
+7. **Use Reddit and other community sources only as labeled secondary evidence** because they can surface practical gotchas but are not authoritative. Treat them as implementation color, not final truth.
+
+8. **Separate verified facts from inference** because downstream planning depends on confidence. Mark what is directly supported by repo evidence or official sources versus what you infer from patterns or secondary signals.
+
+9. **Keep the output decision-oriented** because the goal is not to dump links. Tie each finding back to the implementation, workflow, agent, or skill decision it affects.
+
+10. **Recommend the next route explicitly** because research is usually a handoff, not the end of the task. Name the next workflow, agent, or exact skill that should continue the work.
+
+11. **State the remaining gaps and risks** because incomplete research is still useful when the uncertainty is visible. Call out what you could not verify, what may have changed recently, and what assumptions remain.
+
+12. **Avoid over-quoting and over-collecting** because research quality comes from synthesis, not volume. Prefer concise summaries with high-signal citations over long pasted excerpts.
+
+13. **When the task turns into implementation, stop researching and hand off** because mixing discovery and execution usually creates drift. Deliver the research brief first, then route into the correct workflow or specialist.
+
+## Output Format
+
+Deliver:
+
+1. **Research question** — topic, freshness requirement, and decision to support
+2. **Verified facts** — repo evidence and primary-source findings
+3. **Secondary/community evidence** — labeled lower-trust supporting signals
+4. **Gaps / unknowns** — unresolved questions or contradictory evidence
+5. **Recommended next route** — direct execution, workflow, agent, or exact skill to use next
+
+## References
+
+Load only the file needed for the current question.
+
+| File | Load when |
+| --- | --- |
+| `references/source-ladder.md` | Need the repo-first and source-priority policy for official docs versus community evidence. |
+| `references/research-output.md` | Need the structured output format, evidence labeling rules, or handoff pattern. |
+| `references/comparison-checklist.md` | Comparing vendors, frameworks, or tools and need a concrete evaluation frame. |
+
+## Examples
+
+Use these when the task shape already matches.
+
+| File | Use when |
+| --- | --- |
+| `examples/01-latest-docs-check.md` | Verifying a latest capability or doc claim before implementation. |
+| `examples/02-ecosystem-comparison.md` | Comparing multiple tools or platforms with official-first sourcing. |
+| `examples/03-research-to-implementation-handoff.md` | Turning research findings into a concrete next workflow or specialist handoff. |
+
+## Antigravity Research Flow
+
+- Keep research repo-first even when Agent Manager is available. Do not fan out web browsing before you understand the local system.
+- Official docs and upstream sources stay primary. Reddit and other community posts can inform practical tradeoffs, but label them as secondary evidence.
+- Use Agent Manager only when the research can be cleanly split into independent tracks, then synthesize one final evidence-backed recommendation.
+
+## 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>/`.

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

@@ -0,0 +1,17 @@
+# Deep Research Eval Assertions
+
+## Eval 1: Latest Capability Verification
+
+1. **repo-first** — Starts by checking repo or local evidence before jumping to web claims.
+2. **official-first** — Uses official docs or upstream sources as the primary evidence for the capability.
+3. **secondary-labeled** — If community sources are mentioned, labels them as secondary evidence instead of presenting them as authoritative.
+4. **gaps-called-out** — Identifies unresolved uncertainty or missing confirmation.
+5. **next-route** — Ends with a concrete recommended workflow, agent, or skill to use next.
+
+## Eval 2: Tool Comparison
+
+1. **comparison-frame** — Defines the comparison axes instead of producing vague preferences.
+2. **repo-impact** — Connects the comparison back to the current repo or implementation constraints.
+3. **fact-vs-inference** — Separates verified facts from inference or interpretation.
+4. **decision-oriented** — Produces a recommendation or explicit defer condition.
+5. **no-research-sprawl** — Keeps the output concise and structured rather than dumping raw links.