@cubis/foundry 0.3.10

package/Ai Agent Workflow/skills/vercel-agent-workflows/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-agent-workflows
+description: "Run Vercel Agent workflows for iterative code review and troubleshooting."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, agent, workflows
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Agent Workflows
+
+## Purpose
+Run Vercel Agent workflows for iterative code review and troubleshooting.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-gateway-auth-byok/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-gateway-auth-byok
+description: "Configure AI Gateway authentication and bring-your-own-key controls."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, auth, byok
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai Gateway Auth Byok
+
+## Purpose
+Configure AI Gateway authentication and bring-your-own-key controls.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-gateway-core/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-gateway-core
+description: "Route LLM traffic through Vercel AI Gateway with unified controls."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, core
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai Gateway Core
+
+## Purpose
+Route LLM traffic through Vercel AI Gateway with unified controls.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-gateway-fallbacks/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-gateway-fallbacks
+description: "Implement retries and fallback chains for resilient AI responses."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, fallbacks
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai Gateway Fallbacks
+
+## Purpose
+Implement retries and fallback chains for resilient AI responses.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-gateway-model-routing/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-gateway-model-routing
+description: "Design model and provider routing policies for latency, quality, and cost."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, model, routing
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai Gateway Model Routing
+
+## Purpose
+Design model and provider routing policies for latency, quality, and cost.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-gateway-observability/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-gateway-observability
+description: "Monitor AI Gateway usage, latency, and spend with actionable thresholds."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, observability
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai Gateway Observability
+
+## Purpose
+Monitor AI Gateway usage, latency, and spend with actionable thresholds.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-gateway-openai-compatible/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-gateway-openai-compatible
+description: "Use OpenAI-compatible AI Gateway endpoints without lock-in risk."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, openai, compatible
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai Gateway Openai Compatible
+
+## Purpose
+Use OpenAI-compatible AI Gateway endpoints without lock-in risk.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-sdk-core/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-sdk-core
+description: "Implement Vercel AI SDK core abstractions for model calls and tool usage."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, sdk, core
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai SDK Core
+
+## Purpose
+Implement Vercel AI SDK core abstractions for model calls and tool usage.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-sdk-ui/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ai-sdk-ui
+description: "Implement AI SDK UI streaming and client interaction patterns."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, sdk, ui
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
+---
+
+# Vercel Ai SDK Ui
+
+## Purpose
+Implement AI SDK UI streaming and client interaction patterns.
+
+## When To Use
+- Vercel platform changes in the `ai` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Implement routing, fallback, and authentication policy explicitly.
+3. Instrument token usage, latency, and error classes for all calls.
+4. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-alerts-monitoring/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-alerts-monitoring
+description: "Define alerts and monitoring thresholds tied to user-impact symptoms."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, alerts, monitoring
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Alerts Monitoring
+
+## Purpose
+Define alerts and monitoring thresholds tied to user-impact symptoms.
+
+## When To Use
+- Vercel platform changes in the `obs` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define critical user journeys and map required telemetry coverage.
+2. Ensure logs, traces, and metrics share correlation identifiers.
+3. Set alert thresholds tied to user impact, not only resource counters.
+4. Verify incident drill-down flow from alert to root-cause evidence.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-audit-logs/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-audit-logs
+description: "Use audit logs for compliance evidence and change forensics."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, audit, logs
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Audit Logs
+
+## Purpose
+Use audit logs for compliance evidence and change forensics.
+
+## When To Use
+- Vercel platform changes in the `security` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Model threat paths and required controls before enabling policy changes.
+2. Roll out security controls gradually with monitoring and safe bypass process.
+3. Validate policy behavior with legitimate and malicious traffic patterns.
+4. Document ownership, escalation, and audit expectations.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-automation/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-automation
+description: "Umbrella Vercel automation playbook covering project setup, deployment lifecycle, security, observability, and CLI operations."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, automation
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Automation
+
+## Purpose
+Umbrella Vercel automation playbook covering project setup, deployment lifecycle, security, observability, and CLI operations.
+
+## When To Use
+- Vercel platform changes in the `platform` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm project, environment, and branch deployment expectations.
+2. Apply the smallest configuration change that satisfies behavior goals.
+3. Validate preview and production behavior with explicit rollback plan.
+4. Document resulting deployment and operational constraints.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-blob/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-blob
+description: "Use Vercel Blob for object storage, uploads, and secure access patterns."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, storage, blob
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: database-design, postgres-pro, server-management
+---
+
+# Vercel Blob
+
+## Purpose
+Use Vercel Blob for object storage, uploads, and secure access patterns.
+
+## When To Use
+- Vercel platform changes in the `storage` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Map data access patterns and retention requirements first.
+2. Choose storage primitive that matches latency, consistency, and cost goals.
+3. Implement access control and environment isolation for each data path.
+4. Validate migration and recovery procedures before production rollout.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-bot-management/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-bot-management
+description: "Use bot-management policy controls for traffic quality and abuse defense."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, bot, management
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Bot Management
+
+## Purpose
+Use bot-management policy controls for traffic quality and abuse defense.
+
+## When To Use
+- Vercel platform changes in the `security` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Model threat paths and required controls before enabling policy changes.
+2. Roll out security controls gradually with monitoring and safe bypass process.
+3. Validate policy behavior with legitimate and malicious traffic patterns.
+4. Document ownership, escalation, and audit expectations.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-botid/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-botid
+description: "Implement BotID challenge behavior with minimal legitimate-user friction."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, botid
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Botid
+
+## Purpose
+Implement BotID challenge behavior with minimal legitimate-user friction.
+
+## When To Use
+- Vercel platform changes in the `security` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Model threat paths and required controls before enabling policy changes.
+2. Roll out security controls gradually with monitoring and safe bypass process.
+3. Validate policy behavior with legitimate and malicious traffic patterns.
+4. Document ownership, escalation, and audit expectations.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-build-image-upgrades/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-build-image-upgrades
+description: "Plan and validate build image and runtime toolchain upgrades on Vercel."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, build, image, upgrades
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Build Image Upgrades
+
+## Purpose
+Plan and validate build image and runtime toolchain upgrades on Vercel.
+
+## When To Use
+- Vercel platform changes in the `platform` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm project, environment, and branch deployment expectations.
+2. Apply the smallest configuration change that satisfies behavior goals.
+3. Validate preview and production behavior with explicit rollback plan.
+4. Document resulting deployment and operational constraints.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-build-output-api/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-build-output-api
+description: "Use Build Output API patterns for framework output integration."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, build, output, api
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Build Output API
+
+## Purpose
+Use Build Output API patterns for framework output integration.
+
+## When To Use
+- Vercel platform changes in the `platform` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm project, environment, and branch deployment expectations.
+2. Apply the smallest configuration change that satisfies behavior goals.
+3. Validate preview and production behavior with explicit rollback plan.
+4. Document resulting deployment and operational constraints.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-build-pipeline/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-build-pipeline
+description: "Operate build settings, build logs, and build-failure triage workflows."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, build, pipeline
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Build Pipeline
+
+## Purpose
+Operate build settings, build logs, and build-failure triage workflows.
+
+## When To Use
+- Vercel platform changes in the `platform` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm project, environment, and branch deployment expectations.
+2. Apply the smallest configuration change that satisfies behavior goals.
+3. Validate preview and production behavior with explicit rollback plan.
+4. Document resulting deployment and operational constraints.
+
+## Output Contract
+- Proposed implementation choices and tradeoffs
+- Required config, code, and environment changes
+- Validation evidence and rollback notes
+- Residual risks and follow-up actions