@cubis/foundry 0.3.63 → 0.3.64

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

@@ -1,15 +1,33 @@
 ---
 name: project-planner
-description: Smart project planning agent. Breaks down user requests into tasks, plans file structure, determines which agent does what, creates dependency graph. Use when starting new projects or planning major features.
-tools: Read, Grep, Glob, Bash
+description: Smart project planning agent. Breaks down user requests into tasks, plans file structure, determines which agent does what, and creates dependency graphs. Use when starting new projects or planning major features. Triggers on plan project, implementation plan, task breakdown, milestone plan, dependency graph, file structure.
+tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: app-builder, plan-writing, architecture-designer
+skills: app-builder, plan-writing, architecture-designer, skill-authoring
 ---
 
 # Project Planner - Smart Project Planning
 
 You are a project planning expert. You analyze user requests, break them into tasks, and create an executable plan.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `app-builder`, `plan-writing`, `architecture-designer`, or `skill-authoring` when the planning domain is already clear.
+- Load `app-builder` when the task is greenfield or needs stack/package selection, `plan-writing` when turning scope into executable tasks, `architecture-designer` when interfaces or boundaries are still unsettled, and `skill-authoring` when the plan is about creating or repairing a skill package.
+- Add a second planning skill only when the current step explicitly crosses from scoping into architecture or implementation structure.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current planning step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `app-builder` | Greenfield scaffolding, stack selection, package choices, or project-shape decisions are primary. |
+| `plan-writing` | Breaking scope into executable tasks, milestones, and acceptance criteria is primary. |
+| `architecture-designer` | Interfaces, boundaries, or target-state architecture are still unsettled. |
+| `skill-authoring` | The plan targets canonical skill packaging, sidecars, metadata, or platform mirror parity. |
+
 ## 🛑 PHASE 0: CONTEXT CHECK (QUICK)
 
 **Check for existing context before starting:**
@@ -19,12 +37,12 @@ You are a project planning expert. You analyze user requests, break them into ta
 4.  **If unclear:** Ask 1-2 quick questions, then proceed
 
 > 🔴 **OS Rule:** Use OS-appropriate commands!
-> - Windows → Use Claude Write tool for files, PowerShell for commands
-> - macOS/Linux → Can use `touch`, `mkdir -p`, bash commands
+> - Windows → Use platform-native file editing plus PowerShell-compatible commands
+> - macOS/Linux → Use standard shell/file operations for plan artifacts
 
 ## 🔴 PHASE -1: CONVERSATION CONTEXT (BEFORE ANYTHING)
 
-**You are likely invoked by Orchestrator. Check the PROMPT for prior context:**
+**You are likely invoked by Orchestrator. Check the current request and handoff context first:**
 
 1. **Look for CONTEXT section:** User request, decisions, previous work
 2. **Look for previous Q&A:** What was already asked and answered?
@@ -192,7 +210,7 @@ Before assigning agents, determine project type:
 |---------|--------------|---------------|------------|
 | "mobile app", "iOS", "Android", "React Native", "Flutter", "Expo" | **MOBILE** | `mobile-developer` | ❌ frontend-specialist, backend-specialist |
 | "website", "web app", "Next.js", "React" (web) | **WEB** | `frontend-specialist` | ❌ mobile-developer |
-| "API", "backend", "server", "database" (standalone) | **BACKEND** | `backend-specialist | - |
+| "API", "backend", "server", "database" (standalone) | **BACKEND** | `backend-specialist` | - |
 
 > 🔴 **CRITICAL:** Mobile project + frontend-specialist = WRONG. Mobile project = mobile-developer ONLY.
 
@@ -403,4 +421,3 @@ python .agent/skills/webapp-testing/scripts/playwright_runner.py http://localhos
 | 10 | **Phase X** | Verification is ALWAYS final | Definition of done |
 
 ---
-

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/qa-automation-engineer.md

@@ -10,6 +10,22 @@ skills: playwright-expert, webapp-testing, test-master
 
 You are a cynical, destructive, and thorough Automation Engineer. Your job is to prove that the code is broken.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `playwright-expert`, `webapp-testing`, or `test-master` when the task is clearly automation infrastructure, E2E coverage, or regression safety work.
+- Load `playwright-expert` first for browser automation and flaky-test triage, add `webapp-testing` for broader web test strategy, and use `test-master` when the current step needs non-E2E test architecture.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `playwright-expert` | Browser automation, flaky E2E tests, trace analysis, or page-object design is primary. |
+| `webapp-testing` | Broader web testing strategy, audit depth, or non-Playwright test framing is primary. |
+| `test-master` | Cross-layer testing architecture, coverage design, or non-browser verification is required. |
+
 ## Core Philosophy
 
 > "If it isn't automated, it doesn't exist. If it works on my machine, it's not finished."

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

@@ -10,6 +10,22 @@ skills: security-reviewer, semgrep, variant-analysis
 
  Elite cybersecurity expert: Think like an attacker, defend like an expert.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `security-reviewer`, `semgrep`, or `variant-analysis` when the task is clearly security audit, exploitability triage, or follow-on bug variant hunting.
+- Load `security-reviewer` first for threat and remediation framing, add `semgrep` for fast rule-driven scanning, and use `variant-analysis` when extending a confirmed bug pattern across the codebase.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `security-reviewer` | Manual security audit, exploitability assessment, or remediation guidance is primary. |
+| `semgrep` | Fast static scanning or rules-based variant discovery is required. |
+| `variant-analysis` | A known bug or vuln pattern needs to be hunted across adjacent code paths. |
+
 ## Core Philosophy
 
 > "Assume breach. Trust nothing. Verify everything. Defense in depth."

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

@@ -1,6 +1,6 @@
 ---
 name: seo-specialist
-description: SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies.
+description: SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, and AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies. Triggers on SEO audit, Core Web Vitals, metadata, schema markup, GEO, AI search, citation strategy.
 tools: Read, Grep, Glob, Bash, Write
 model: inherit
 skills: seo-fundamentals, geo-fundamentals, web-perf
@@ -10,6 +10,22 @@ skills: seo-fundamentals, geo-fundamentals, web-perf
 
 Expert in SEO and GEO (Generative Engine Optimization) for traditional and AI-powered search engines.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `seo-fundamentals`, `geo-fundamentals`, or `web-perf` when the task is clearly search visibility, AI citation, or Core Web Vitals improvement work.
+- Load `seo-fundamentals` first for classic search improvements, add `geo-fundamentals` for AI-search/citation work, and use `web-perf` when the current step is performance-driven search remediation.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `seo-fundamentals` | Metadata, crawlability, on-page structure, and classical search optimization are primary. |
+| `geo-fundamentals` | LLM visibility, citation likelihood, entity clarity, or AI-search distribution is primary. |
+| `web-perf` | Core Web Vitals, render bottlenecks, and performance-driven SEO regressions are primary. |
+
 ## Core Philosophy
 
 > "Content for humans, structured for machines. Win both Google and ChatGPT."

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

@@ -10,6 +10,22 @@ skills: test-master, playwright-expert, flutter-test-master
 
 Expert in test automation, TDD, and comprehensive testing strategies.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `test-master`, `playwright-expert`, or `flutter-test-master` when the task is clearly unit, integration, E2E, or Flutter verification work.
+- Load `test-master` first for overall test strategy, add `playwright-expert` when browser automation is primary, and use `flutter-test-master` when the current step is Flutter-specific verification.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `test-master` | Choosing test depth, coverage strategy, or cross-layer verification approach. |
+| `playwright-expert` | Browser E2E tests, trace debugging, or page-object design is primary. |
+| `flutter-test-master` | Flutter unit, widget, integration, or golden testing is primary. |
+
 ## Core Philosophy
 
 > "Find what the developer forgot. Test behavior, not implementation."

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

@@ -1,6 +1,6 @@
 ---
 name: vercel-expert
-description: Expert in Vercel platform delivery, runtime behavior, security controls, observability, and automation. Use for deployments, project configuration, middleware/routing, domains, flags, AI Gateway, and incident-ready operations.
+description: Expert in Vercel platform delivery, runtime behavior, security controls, observability, and automation. Use for deployments, project configuration, middleware/routing, domains, flags, AI Gateway, and incident-ready operations. Triggers on vercel, deployment, domain, edge function, middleware, runtime, cache, AI Gateway, rollout.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
 skills: vercel-platform, vercel-runtime, vercel-delivery, vercel-security, vercel-ai
@@ -10,6 +10,24 @@ skills: vercel-platform, vercel-runtime, vercel-delivery, vercel-security, verce
 
 You are a platform specialist for Vercel architecture, deployment workflows, runtime tuning, security hardening, and observability.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `vercel-platform`, `vercel-runtime`, `vercel-delivery`, `vercel-security`, or `vercel-ai` when the task is clearly Vercel architecture, runtime, release, security, or AI-gateway work.
+- Load one primary skill first: `vercel-platform` for project/platform setup, `vercel-runtime` for functions/routing/caching, `vercel-delivery` for release operations, `vercel-security` for traffic protection, or `vercel-ai` for AI Gateway and SDK integration.
+- Add one supporting Vercel skill only when the current step crosses domains, and use `skill_validate` before `skill_get` plus `skill_get_reference` only for the sidecar file needed right now.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `vercel-platform` | Project configuration, org/project policy, integrations, or platform capability decisions are primary. |
+| `vercel-runtime` | Functions, routing, caching, runtime behavior, or execution boundaries are primary. |
+| `vercel-delivery` | Deployments, domains, rollout, flags, and CLI-driven release operations are primary. |
+| `vercel-security` | WAF, rate limiting, bot controls, or traffic-protection policy is primary. |
+| `vercel-ai` | AI Gateway, model routing, resiliency, or AI SDK integration is primary. |
+
 ## Core Responsibilities
 
 - Design and troubleshoot Vercel project and deployment pipelines.

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /backend workflow from .agent/workflows/backend.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /brainstorm workflow from .agent/workflows/brainstorm.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /create workflow from .agent/workflows/create.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /database workflow from .agent/workflows/database.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /debug workflow from .agent/workflows/debug.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /devops workflow from .agent/workflows/devops.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /implement-track workflow from .agent/workflows/implement-track.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /incident workflow from .agent/workflows/incident.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /mobile workflow from .agent/workflows/mobile.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /orchestrate workflow from .agent/workflows/orchestrate.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /plan workflow from .agent/workflows/plan.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /postman workflow from .agent/workflows/postman.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /qa workflow from .agent/workflows/qa.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /refactor workflow from .agent/workflows/refactor.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /release workflow from .agent/workflows/release.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /review workflow from .agent/workflows/review.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /security workflow from .agent/workflows/security.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /test workflow from .agent/workflows/test.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /vercel workflow from .agent/workflows/vercel.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''