@cubis/foundry 0.3.31 → 0.3.33

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

@@ -0,0 +1,11 @@
+description = "Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership and handoff."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Create and execute quality strategy with automation and regression-focused coverage."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Improve maintainability while preserving behavior through incremental safe refactoring."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Prepare and execute release with rollout guardrails, verification, and rollback plan."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Run a strict review for bugs, regressions, and security issues with prioritized findings."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Run security-focused analysis and remediation planning with exploitability-first triage."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Design and execute verification strategy aligned to risk and acceptance criteria."
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -0,0 +1,11 @@
+description = "Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails."
+prompt = '''
+Follow the /vercel workflow from .agent/workflows/vercel.md.
+
+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.
+
+If command arguments are provided, treat them as additional user context.
+'''

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

@@ -11,6 +11,7 @@ This file defines mandatory behavior for Antigravity projects installed via `cbx
 - Workflows: `.agent/workflows`
 - Agents: `.agent/agents`
 - Skills: `.agent/skills`
+- Gemini commands: `.gemini/commands`
 - Rules file: `.agent/rules/GEMINI.md`
 
 ## Startup Transparency (Required)
@@ -27,8 +28,8 @@ Keep this user-visible summary concise and factual; do not expose private chain-
 
 ## 2) Workflow-First Contract
 
-1. If the user explicitly requests a slash command, run that workflow first.
-2. Otherwise choose the best workflow by intent from `.agent/workflows`.
+1. If the user explicitly requests a slash command, run that command/workflow first.
+2. Otherwise choose the best workflow by intent from `.agent/workflows` and use matching `.gemini/commands/*.toml` when available.
 3. For cross-domain tasks, use orchestrated delegation with `@orchestrator`.
 4. Keep one primary workflow; use others only as supporting references.
 
@@ -39,6 +40,19 @@ Keep this user-visible summary concise and factual; do not expose private chain-
 3. Simple code changes: minimal edits with focused verification.
 4. Complex code/design changes: plan first, then implement and verify.
 
+## 3A) Workflow Pattern Map (Antigravity)
+
+Map intent to one primary workflow first:
+
+- Explain codebase -> `/plan`
+- Fix bug -> `/debug`
+- Write test -> `/test` or `/qa`
+- Prototype from screenshot -> `/create` + `@frontend-specialist`
+- Iterate UI updates -> `/create` with verification loop
+- Refactor safely -> `/refactor` (or `@code-archaeologist` if scope is narrow)
+- Local code review -> `/review`
+- Documentation update -> `/create` + `@documentation-writer`
+
 ## 4) Agent Routing Policy
 
 Use the best specialist first:
@@ -54,14 +68,14 @@ Use the best specialist first:
 
 ## 5) Skill Loading Policy
 
-### Smart Skill Selection (TIER 0)
+### Smart Skill Selection (Adaptive)
 
-Before starting ANY task, the agent MUST:
+Use an adaptive load policy to control context size:
 
-1.  **Analyze** the user's request against the keywords in `.agent/skills/skills_index.json`.
-2.  **Select** the most relevant skill(s) if a strong match is found.
-3.  **Load** the selected skill's `SKILL.md` using `view_file` **BEFORE** proceeding.
-4.  **Announce** the selection: "I am loading the `[Skill Name]` skill to handle your request."
+1. Q&A/explanations: do not load skills unless the user explicitly asks for one.
+2. Implementation/debug/review: load at most 1 primary skill and 1 supporting skill.
+3. Cross-domain orchestration: use additional skills only when domains clearly differ.
+4. Explicit skill mention by user always takes precedence.
 
 ### General Loading Rules
 
@@ -69,6 +83,7 @@ Before starting ANY task, the agent MUST:
 2.  Prefer progressive disclosure: start from `SKILL.md`, then specific sections.
 3.  Keep context lean; avoid loading unrelated skill documents.
 4.  If a mapped skill is missing, continue with best fallback and state it.
+5.  Keep user-visible decision logs concise: selected skill(s) and one-line rationale.
 
 ## 6) Socratic Gate (Before Complex Work)
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/backend.md

@@ -1,21 +1,37 @@
 ---
 command: "/backend"
-description: "Route backend-focused tasks to the backend specialist with API, data, and reliability focus."
+description: "Drive backend architecture and implementation via backend specialist with API, data, and reliability focus."
 triggers: ["backend", "api", "service", "database", "performance"]
 ---
 # Backend Workflow
 
-Use this workflow when backend architecture or implementation is primary.
+## When to use
+Use this when backend architecture or service logic is primary.
 
 ## Routing
 - Primary specialist: `@backend-specialist`
+- Add `@database-architect` for schema/query changes.
+- Add `@security-auditor` when auth, secrets, or sensitive data are involved.
 
-## Steps
-1. Ask `@backend-specialist` for solution outline.
-2. Validate API contracts, data model, and failure handling.
-3. Implement backend changes with tests and observability.
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `nodejs-best-practices`, `api-designer`
+- Supporting skills (optional): `api-patterns`, `database-skills`, `secure-code-guardian`
+
+## Workflow steps
+1. Ask specialist(s) for design and risk assessment.
+2. Validate contracts, data model, and failure handling.
+3. Implement backend changes with observability.
 4. Always update API docs: OpenAPI spec, Swagger UI route, and Stoplight Elements route/component.
-5. Return summary including migration and rollout notes.
+5. Run targeted tests and summarize rollout notes.
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
 
 ## Output Contract
 - API/contract changes

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/brainstorm.md

@@ -1,14 +1,34 @@
 ---
 command: "/brainstorm"
-description: "Generate options, tradeoffs, and architecture ideas before implementation."
-triggers: ["idea", "explore", "tradeoff", "approach", "brainstorm"]
+description: "Generate concrete solution options and tradeoffs before committing to implementation."
+triggers: ["idea", "brainstorm", "options", "tradeoff", "approach"]
 ---
 # Brainstorm Workflow
 
-Use this workflow when requirements are open-ended and multiple solution paths are possible.
+## When to use
+Use this when requirements are still fluid and architecture choices are open.
 
-## Steps
-1. Clarify goals, constraints, and non-goals.
-2. Produce 2-4 implementation options.
-3. Compare complexity, risk, and maintainability.
-4. Recommend one option and explain why.
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `brainstorming`, `feature-forge`
+- Supporting skills (optional): `plan-writing`
+
+## Workflow steps
+1. Restate problem, constraints, and success metrics.
+2. Produce 2-4 options with architecture shape.
+3. Compare complexity, risk, and implementation speed.
+4. Recommend one option and justify rejection of others.
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+- Option table (pros/cons)
+- Recommended option
+- Known unknowns
+- First implementation milestone

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/create.md

@@ -1,14 +1,34 @@
 ---
 command: "/create"
-description: "Implement new feature code with clear boundaries and minimal regression risk."
-triggers: ["implement", "build", "create", "feature", "code"]
+description: "Implement feature work with minimal blast radius and clear verification checkpoints."
+triggers: ["create", "build", "implement", "feature", "develop"]
 ---
 # Create Workflow
 
-Use this workflow for net-new implementation work.
+## When to use
+Use this for net-new implementation after design is stable.
 
-## Steps
-1. Identify target files and expected behavior.
-2. Implement minimal viable change.
-3. Validate with tests/checks.
-4. Summarize behavior and follow-up actions.
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `feature-forge`, `architecture-designer`
+- Supporting skills (optional): `lint-and-validate`, `test-master`
+
+## Workflow steps
+1. Confirm target files and contracts.
+2. Implement smallest coherent increment.
+3. Validate behavior with focused tests.
+4. Capture remaining gaps and follow-ups.
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+- Changed components/files
+- Behavioral impact
+- Test evidence
+- Follow-up items

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

@@ -5,6 +5,7 @@ triggers: ["database", "sql", "schema", "migration", "index"]
 ---
 # Database Workflow
 
+## When to use
 Use this when data modeling, query quality, migration safety, or database performance is core to the task.
 
 ## Routing
@@ -17,7 +18,15 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Power bridge: `workflows/powers/database-skills`
 - Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
-## Steps
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `database-skills`, `database-design`
+- Supporting skills (optional): `database-optimizer`
+
+## Workflow steps
 1. Confirm data shape, access patterns, and workload size.
 2. Choose track: `database-design` (schema/migrations), `database-optimizer` (tuning), or `database-skills` (engine wrappers).
 3. Choose engine wrapper and define index strategy.
@@ -25,6 +34,11 @@ Use this when data modeling, query quality, migration safety, or database perfor
 5. Plan migration and rollback.
 6. Validate with query-plan evidence and production-risk notes.
 
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
 ## Output Contract
 - Schema/query changes
 - Indexing plan

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/debug.md

@@ -1,14 +1,34 @@
 ---
 command: "/debug"
-description: "Investigate failures, isolate root cause, and propose the smallest safe fix."
-triggers: ["bug", "error", "stack trace", "investigate", "debug"]
+description: "Isolate root cause quickly and apply the smallest safe remediation with verification."
+triggers: ["debug", "bug", "error", "incident", "stack trace"]
 ---
 # Debug Workflow
 
-Use this workflow when behavior is broken or uncertain.
+## When to use
+Use this when behavior is failing or inconsistent.
 
-## Steps
-1. Reproduce the issue reliably.
-2. Narrow fault domain and inspect evidence.
-3. Identify root cause and impact radius.
-4. Implement and validate focused remediation.
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `systematic-debugging`, `find-bugs`
+- Supporting skills (optional): `monitoring-expert`, `error-ux-observability`
+
+## Workflow steps
+1. Reproduce issue and collect evidence.
+2. Narrow fault domain and identify root cause.
+3. Apply focused fix with low regression risk.
+4. Verify resolution and monitor for recurrence.
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+- Reproduction notes
+- Root cause summary
+- Fix summary
+- Regression checks performed

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/devops.md

@@ -5,6 +5,7 @@ triggers: ["devops", "deploy", "ci", "cd", "rollback", "infra"]
 ---
 # DevOps Workflow
 
+## When to use
 Use this when deployment pipeline, infrastructure, or release execution is the main scope.
 
 ## Routing
@@ -12,12 +13,25 @@ Use this when deployment pipeline, infrastructure, or release execution is the m
 - Security checks: `@security-auditor`
 - Verification support: `@test-engineer`
 
-## Steps
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `devops-engineer`, `sre-engineer`
+- Supporting skills (optional): `monitoring-expert`, `terraform-engineer`, `wrangler`
+
+## Workflow steps
 1. Confirm target environment and risk level.
 2. Define rollout and rollback strategy.
 3. Apply CI/CD or infra changes.
 4. Validate monitors/alerts and recovery path.
 
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
 ## Output Contract
 - Deployment plan
 - Rollback conditions

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

@@ -1,14 +1,35 @@
 ---
 command: "/implement-track"
-description: "Execute implementation in tracked milestones with visible progress and quality gates."
-triggers: ["track", "milestone", "implementation", "progress", "deliver"]
+description: "Execute large work in milestones with explicit quality gates and status updates."
+triggers: ["track", "milestone", "delivery", "progress", "execution"]
 ---
 # Implement Track Workflow
 
-Use this workflow for larger work that benefits from milestone tracking.
+## When to use
+Use this for medium/large efforts where progress visibility is required.
 
-## Steps
-1. Split implementation into clear milestones.
-2. Complete one milestone at a time.
-3. Validate each milestone before continuing.
-4. Publish concise progress and remaining risk.
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `plan-writing`, `feature-forge`
+- Supporting skills (optional): `lint-and-validate`, `test-master`
+
+## Workflow steps
+1. Split into milestone-sized deliverables.
+2. Define done criteria per milestone.
+3. Execute one milestone at a time.
+4. Validate before moving forward.
+5. Publish progress and remaining risks.
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+- Milestone board (done/in-progress/next)
+- Gate status
+- Blockers and dependencies
+- ETA confidence

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/incident.md

@@ -0,0 +1,42 @@
+---
+command: "/incident"
+description: "Handle production incidents with triage, mitigation, root cause, and post-incident actions."
+triggers: ["incident", "outage", "sev", "degraded", "hotfix"]
+---
+# Incident Workflow
+
+## When to use
+Use this for active or recent production incidents.
+
+## Routing
+- Runtime/service issues: `@backend-specialist` + `@debugger`
+- Data inconsistencies: `@database-architect`
+- Security events: `@security-auditor`
+- Recovery validation: `@test-engineer`
+- Deployment rollback execution: `@devops-engineer`
+
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `systematic-debugging`, `sre-engineer`
+- Supporting skills (optional): `monitoring-expert`, `security-reviewer`
+
+## Workflow steps
+1. Establish impact, severity, and current status.
+2. Mitigate first, then stabilize.
+3. Identify probable root cause and confirm.
+4. Implement and verify durable fix.
+5. Document post-incident follow-up actions.
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+- Incident timeline
+- Mitigation actions
+- Root cause statement
+- Follow-up prevention tasks

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

@@ -5,6 +5,7 @@ triggers: ["mobile", "flutter", "ios", "android", "navigation"]
 ---
 # Mobile Workflow
 
+## When to use
 Use this when mobile app architecture, UX behavior, or platform constraints are the focus.
 
 ## Routing
@@ -12,12 +13,25 @@ Use this when mobile app architecture, UX behavior, or platform constraints are
 - UI support: `@frontend-specialist`
 - Verification support: `@test-engineer`
 
-## Steps
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `mobile-design`, `flutter-expert`
+- Supporting skills (optional): `riverpod-3`, `drift-flutter`, `flutter-test-master`
+
+## Workflow steps
 1. Confirm platform and UX constraints.
 2. Plan navigation/state/offline behavior.
 3. Implement or refactor mobile flows.
 4. Validate behavior across critical paths.
 
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
 ## Output Contract
 - Mobile flow changes
 - Platform constraints handled

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/orchestrate.md

@@ -0,0 +1,45 @@
+---
+command: "/orchestrate"
+description: "Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership and handoff."
+triggers: ["orchestrate", "coordinate", "multi-area", "cross-team", "handoff"]
+---
+# Orchestrate Workflow
+
+## When to use
+Use this when a task spans backend, frontend, data, testing, and release concerns.
+
+## Routing
+- Primary coordinator: `@orchestrator`
+- Architecture decisions: `@backend-specialist`
+- Data model/query risk: `@database-architect`
+- UX/client behavior: `@frontend-specialist`
+- Security review: `@security-auditor`
+- Verification strategy: `@test-engineer`
+- Rollout plan: `@devops-engineer`
+
+## Workflow steps
+1. Break the request into workstreams with owners.
+2. Request one primary specialist output per workstream.
+3. Merge outputs into a single implementation plan.
+4. Resolve conflicts before implementation.
+5. End with a release-risk summary.
+
+## Context notes
+- This workflow file, active platform rules, and selected agents/skills guide execution.
+- Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
+
+## Skill Routing
+- Primary skills: `parallel-agents`, `architecture-designer`
+- Supporting skills (optional): `plan-writing`, `feature-forge`
+
+## Verification
+- Run focused checks/tests for the changed scope.
+- Confirm no regressions in adjacent behavior.
+- Note any gaps that were not validated.
+
+## Output Contract
+- Scope and assumptions
+- Workstreams with owner + deliverable
+- Consolidated execution order
+- Test and rollout gates
+- Open risks and mitigations