@cubis/foundry 0.3.75 → 0.3.77

package/workflows/workflows/agent-environment-setup/manifest.json

@@ -1,6 +1,6 @@
 {
   "id": "agent-environment-setup",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Workflow-first AI agent environment setup for Antigravity, Codex, Copilot, Claude Code, and Gemini CLI.",
   "platforms": {
     "antigravity": {
@@ -55,6 +55,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -105,6 +106,7 @@
         "skill-creator",
         "spring-boot",
         "sqlalchemy",
+        "stitch",
         "stripe-integration",
         "svelte-sveltekit",
         "swift-best-practices",
@@ -198,6 +200,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -248,6 +251,7 @@
         "skill-creator",
         "spring-boot",
         "sqlalchemy",
+        "stitch",
         "stripe-integration",
         "svelte-sveltekit",
         "swift-best-practices",
@@ -321,6 +325,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -371,6 +376,7 @@
         "skill-creator",
         "spring-boot",
         "sqlalchemy",
+        "stitch",
         "stripe-integration",
         "svelte-sveltekit",
         "swift-best-practices",
@@ -464,6 +470,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -514,6 +521,7 @@
         "skill-creator",
         "spring-boot",
         "sqlalchemy",
+        "stitch",
         "stripe-integration",
         "svelte-sveltekit",
         "swift-best-practices",
@@ -532,6 +540,27 @@
           "type": "conductor-reference",
           "optional": true,
           "description": "If Conductor artifacts exist, workflows can reference them as supporting context."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "README.md",
+          "optional": true,
+          "description": "Usage guide for the Claude route/research hook templates."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "settings.snippet.json",
+          "optional": true,
+          "description": "Settings snippet that wires the route/research reminder hook into Claude Code."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "route-research-guard.mjs",
+          "optional": true,
+          "description": "Hook script template that reinforces explicit-route honoring and research escalation."
         }
       ]
     },
@@ -564,6 +593,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -614,6 +644,7 @@
         "skill-creator",
         "spring-boot",
         "sqlalchemy",
+        "stitch",
         "stripe-integration",
         "svelte-sveltekit",
         "swift-best-practices",

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/frontend-specialist.md

@@ -1,11 +1,15 @@
 ---
 name: frontend-specialist
-description: Senior frontend specialist for React, Next.js, UI architecture, interaction quality, accessibility, rendering performance, design-system consistency, and internationalization.
+description: Senior frontend specialist for React, Next.js, Stitch-driven design-to-code delivery, UI architecture, interaction quality, accessibility, rendering performance, design-system consistency, and internationalization.
 triggers:
   [
     "component",
     "react",
     "next",
+    "stitch",
+    "design-to-code",
+    "screen-to-code",
+    "ui diff",
     "ui",
     "ux",
     "css",
@@ -18,7 +22,7 @@ triggers:
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
 maxTurns: 25
-skills: react, nextjs, frontend-design, performance-testing, code-review, observability, typescript-best-practices, javascript-best-practices
+skills: stitch, react, nextjs, frontend-design, performance-testing, code-review, observability, typescript-best-practices, javascript-best-practices
 handoffs:
   - agent: "test-engineer"
     title: "Test UI Components"
@@ -34,6 +38,7 @@ Build and review frontend systems that stay maintainable under real product pres
 
 - Do not call `skill_search` for any skill in the pre-declared list when the task clearly falls into that domain.
 - Load one primary skill first:
+  - `stitch` for Stitch artifacts, design-to-code diffs, screen sync work, and implementation grounded in real Stitch output
   - `react` for component boundaries, state, and runtime behavior
   - `react` for React performance optimization, patterns, and anti-patterns
   - `nextjs` for App Router, server/client boundaries, caching, and route behavior
@@ -45,6 +50,7 @@ Build and review frontend systems that stay maintainable under real product pres
   - `frontend-design` for RTL support, locale switching, pluralization, and date/number formatting
   - `observability` for error boundary design, user-facing error states, and frontend observability
 - Add one supporting skill only when the task genuinely crosses concerns.
+- If the request explicitly references Stitch screens, artifacts, UI diffs, or design sync, load `stitch` first and then add the narrowest implementation skill for the actual stack.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
 
 ## Skill References
@@ -53,6 +59,7 @@ Load on demand. Do not preload all references.
 
 | File                     | Load when                                                                                     |
 | ------------------------ | --------------------------------------------------------------------------------------------- |
+| `stitch`                 | The task starts from Stitch artifacts, design-to-code requests, screen sync, or UI diffs.    |
 | `react`           | React runtime behavior, component boundaries, hooks, or client-state design are primary.      |
 | `react`   | React performance optimization, memoization patterns, or React anti-patterns are the focus.   |
 | `nextjs`       | Next.js route behavior, server/client boundaries, caching, or deployment posture are primary. |
@@ -67,6 +74,7 @@ Load on demand. Do not preload all references.
 ## Operating Stance
 
 - Prefer clear state ownership and small client boundaries.
+- When Stitch is the source of truth, fetch and map the real artifact before editing local UI.
 - Treat accessibility and loading or error states as product correctness, not polish.
 - Measure performance before optimizing.
 - Keep one-off product logic out of shared primitives.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/mobile-developer.md

@@ -1,10 +1,10 @@
 ---
 name: mobile-developer
-description: Expert in Flutter delivery and mobile product design for cross-platform apps. Use for Flutter architecture, native integrations, mobile UX, platform behavior, and release readiness. Triggers on mobile, flutter, ios, android, app store, play store, touch UX.
+description: Expert in Flutter delivery and mobile product design for cross-platform apps. Use for Flutter architecture, Stitch-driven mobile handoff, native integrations, mobile UX, platform behavior, and release readiness. Triggers on mobile, flutter, ios, android, app store, play store, touch UX.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
 maxTurns: 25
-skills: react-native, frontend-design, expo-app, swift-best-practices, kotlin-best-practices, react, systematic-debugging, integration-testing, typescript-best-practices, javascript-best-practices
+skills: stitch, react-native, frontend-design, expo-app, swift-best-practices, kotlin-best-practices, react, systematic-debugging, integration-testing, typescript-best-practices, javascript-best-practices
 handoffs:
   - agent: "test-engineer"
     title: "Test Mobile"
@@ -20,6 +20,7 @@ Build and ship cross-platform mobile apps that feel native and perform reliably.
 
 - Do not call `skill_search` for any skill in the pre-declared list when the task clearly falls into those domains.
 - Load one primary skill first:
+  - `stitch` for Stitch-driven mobile screen handoff, design sync, and artifact-grounded UI updates
   - `react-native` for touch psychology, platform-native patterns, iOS/Android design guidelines
   - `expo-app` for feature implementation in Flutter
   - `expo-app` for state management with Riverpod
@@ -31,12 +32,14 @@ Build and ship cross-platform mobile apps that feel native and perform reliably.
   - `expo-app` for complex state flows
   - `expo-app` for repository pattern and data layer
   - `frontend-design` for internationalization, RTL support, and locale handling
+- If the request starts from Stitch artifacts or a design sync, load `stitch` first and then pair it with the narrowest mobile implementation skill for the target stack.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed.
 
 ## Skill References
 
 | File                    | Load when                                                            |
 | ----------------------- | -------------------------------------------------------------------- |
+| `stitch`                | The task starts from Stitch artifacts, design sync, or screen-to-code handoff. |
 | `react-native`         | Touch UX, platform conventions, iOS/Android design guidelines.       |
 | `expo-app`       | Implementing features, widgets, or screens in Flutter.               |
 | `expo-app`      | State management architecture with Riverpod.                         |
@@ -52,6 +55,7 @@ Build and ship cross-platform mobile apps that feel native and perform reliably.
 ## Operating Stance
 
 - Respect platform conventions — iOS and Android users expect different behaviors.
+- When work starts from Stitch, translate the artifact into native/mobile patterns instead of copying raw layout output.
 - Treat touch targets and gesture feedback as correctness, not polish.
 - Test on real devices for performance-sensitive features.
 - Design for offline-first when the app may lose connectivity.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/orchestrator.md

@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Write, Edit
 model: inherit
 maxTurns: 30
 memory: project
-skills: system-design, api-design, database-design, architecture-doc, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
+skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
 handoffs:
   - agent: "validator"
     title: "Validate Results"
@@ -31,8 +31,8 @@ Your only permitted actions:
 
 ## Skill Loading Contract
 
-- Do not call `skill_search` for `system-design`, `api-design`, `database-design`, `architecture-doc`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, or `skill-creator` when the task is clearly multi-stream coordination, planning, architecture design, contract design, research, or skill package work.
-- Use `system-design` when the coordination problem is really a design tradeoff problem, `api-design` when integration contracts are the coordination bottleneck, `database-design` when the shared dependency is a data-model or migration concern, `architecture-doc` when the coordination risk is stale or conflicting external information, `mcp-server-builder` for MCP-specific streams, `tech-doc` for OpenAI-doc verification streams, `prompt-engineering` for instruction-quality streams, and `skill-creator` when the coordinated changes are in skills, mirrors, routing, or packaging.
+- Do not call `skill_search` for `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, or `skill-creator` when the task is clearly multi-stream coordination, planning, architecture design, contract design, research, or skill package work.
+- Use `system-design` when the coordination problem is really a design tradeoff problem, `api-design` when integration contracts are the coordination bottleneck, `database-design` when the shared dependency is a data-model or migration concern, `deep-research` when the coordination risk is stale or conflicting external information, `mcp-server-builder` for MCP-specific streams, `tech-doc` for OpenAI-doc verification streams, `prompt-engineering` for instruction-quality streams, and `skill-creator` when the coordinated changes are in skills, mirrors, routing, or packaging.
 - Prefer platform-native delegation features when available, but keep the orchestration contract stable even when execution stays in a single track.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current coordination step.
 
@@ -45,7 +45,7 @@ Load on demand. Do not preload all references.
 | `system-design` | Coordination depends on resolving system design or interface tradeoffs first.                             |
 | `api-design`          | The critical shared dependency is an API contract or integration boundary.                                |
 | `database-design`       | The coordination risk centers on schema, migration, data ownership, or engine choice.                     |
-| `architecture-doc`         | External sources, latest information, or public-repo comparisons are blocking confident execution.        |
+| `deep-research`         | External sources, latest information, or public-repo comparisons are blocking confident execution.        |
 | `mcp-server-builder`           | One stream is MCP server design, tool shape, or transport selection.                                      |
 | `tech-doc`           | One stream needs current OpenAI docs or version-specific behavior verification.                           |
 | `prompt-engineering`       | One stream is repairing prompts, agent rules, or instruction quality.                                     |
@@ -158,7 +158,8 @@ ANTI-LAZINESS:
 5. **Iterate, don't accept mediocrity** — if output is incomplete or wrong, re-delegate with feedback.
 6. **Track progress visibly** — maintain a task list showing status of each work item.
 7. **Fail fast on blockers** — if a dependency is missing or a task is stuck after 3 iterations, escalate.
-8. **Synthesize at the end** — combine outputs with concrete actions, risks, and verification evidence.
+8. **Route research explicitly** — when freshness or public comparison matters, delegate to `@researcher` or load `deep-research` before implementation.
+9. **Synthesize at the end** — combine outputs with concrete actions, risks, and verification evidence.
 
 ## Anti-Patterns to Prevent
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/project-planner.md

@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
 maxTurns: 30
 memory: project
-skills: system-design, api-design, database-design, architecture-doc, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
+skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
 handoffs:
   - agent: "orchestrator"
     title: "Start Implementation"
@@ -24,7 +24,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Load `system-design` for system design tradeoffs in the plan.
 - Load `api-design` when the plan involves API contract decisions.
 - Load `database-design` when the plan involves data modeling or migration.
-- Load `architecture-doc` when planning requires external information or comparison.
+- Load `deep-research` when planning requires fresh external information, public comparison, or evidence beyond the repo.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed.
 
 ## Skill References
@@ -34,7 +34,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 | `system-design` | Plan involves system design tradeoffs or component boundaries.     |
 | `api-design`          | Plan involves API contract decisions or integration points.        |
 | `database-design`       | Plan involves data modeling, schema design, or migration strategy. |
-| `architecture-doc`         | Planning requires external research or approach comparison.        |
+| `deep-research`         | Planning requires external research or approach comparison.        |
 | `mcp-server-builder`           | Plan involves MCP server or tool implementation.                   |
 | `skill-creator`         | Plan involves skill package creation or modification.              |
 
@@ -45,6 +45,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Every task needs an owner (agent), acceptance criteria, and verification approach.
 - Plan for rollback — every change should be reversible.
 - Front-load risk — tackle the hardest technical uncertainty first.
+- When outside evidence is needed, send research through `deep-research` first instead of mixing web browsing into every implementation stream.
 
 ## Planning Methodology
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/researcher.md

@@ -18,7 +18,7 @@ tools: Read, Grep, Glob, Bash
 model: inherit
 maxTurns: 30
 memory: project
-skills: architecture-doc, system-design, database-design, tech-doc, prompt-engineering
+skills: deep-research, system-design, database-design, tech-doc, prompt-engineering
 handoffs:
   - agent: "project-planner"
     title: "Plan Implementation"
@@ -30,8 +30,8 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 
 ## Skill Loading Contract
 
-- Do not call `skill_search` for `architecture-doc`, `system-design`, `database-design`, `tech-doc`, or `prompt-engineering` when the task is clearly research work.
-- Load `architecture-doc` first for all research tasks — it defines the research methodology.
+- Do not call `skill_search` for `deep-research`, `system-design`, `database-design`, `tech-doc`, or `prompt-engineering` when the task is clearly research work.
+- Load `deep-research` first for all research tasks — it defines the source ladder, evidence labeling, and research output contract.
 - Add `system-design` when research involves system design patterns or tradeoffs.
 - Add `database-design` when research involves data storage options or migration approaches.
 - Add `tech-doc` when research involves OpenAI API or model behavior verification.
@@ -42,7 +42,7 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 
 | File                    | Load when                                                             |
 | ----------------------- | --------------------------------------------------------------------- |
-| `architecture-doc`         | All research tasks — defines the core research methodology.           |
+| `deep-research`         | All research tasks — defines the core research methodology.           |
 | `system-design` | Research involves system design patterns or architectural tradeoffs.  |
 | `database-design`       | Research involves data storage, database comparison, or migration.    |
 | `tech-doc`           | Research involves OpenAI API, model behavior, or version differences. |
@@ -51,6 +51,9 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 ## Operating Stance
 
 - Breadth first, then depth — survey the landscape before drilling into specifics.
+- Repo first, then web — inspect local code, configs, and docs before using external sources.
+- Official docs first — use vendor or maintainer documentation as primary evidence.
+- Community evidence is secondary — Reddit, blog posts, and forum threads can inform implementation, but label them as lower-trust support.
 - Cite sources — every finding should be traceable to evidence.
 - Distinguish fact from inference — clearly label assumptions.
 - Produce actionable findings — research without recommendations is incomplete.
@@ -72,5 +75,6 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 - Clear distinction between verified facts and educated guesses.
 - Actionable recommendations with tradeoff analysis.
 - Remaining knowledge gaps identified.
+- Output order: verified facts, secondary/community evidence, gaps, recommended next route.
 
 > **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.

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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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/backend.toml

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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

@@ -7,6 +7,8 @@ Execution contract:
 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.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. 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.
@@ -337,6 +338,7 @@ Use this matrix to match incoming tasks to the correct skill and primary agent.
 | sqlalchemy | Framework | SQLAlchemy ORM, sessions, alembic | @database-architect |
 | drizzle-orm | Framework | Drizzle ORM, schema, migrations | @database-architect |
 | frontend-design | Design | UI/UX, component architecture | @frontend-specialist |
+| stitch | Design | Stitch screens, design-to-code, UI diffing | @frontend-specialist |
 | system-design | Design | Distributed systems, scalability | @backend-specialist |
 | microservices-design | Design | Service decomposition, communication | @backend-specialist |
 | api-design | Design | REST/GraphQL API design, versioning | @backend-specialist |
@@ -359,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 |
@@ -406,12 +409,15 @@ 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. Use upstream MCP servers such as `postman`, `stitch`, or `playwright` for real cloud/browser actions when available.
 
 <!-- cbx:mcp:auto:end -->