@cubis/foundry 0.3.10

package/Ai Agent Workflow/skills/vercel-edge-config-integrations/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-edge-config-integrations
+description: "Integrate Edge Config with external flag/config providers safely."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, storage, edge, config, integrations
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: database-design, postgres-pro, server-management
+---
+
+# Vercel Edge Config Integrations
+
+## Purpose
+Integrate Edge Config with external flag/config providers safely.
+
+## 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-edge-to-node-migration/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-edge-to-node-migration
+description: "Migrate Edge Runtime workloads to Node runtime when compatibility requires it."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, edge, to, node, migration
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Edge To Node Migration
+
+## Purpose
+Migrate Edge Runtime workloads to Node runtime when compatibility requires it.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-environments/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-environments
+description: "Design and operate local, preview, production, and custom environment workflows."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, environments
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Environments
+
+## Purpose
+Design and operate local, preview, production, and custom environment 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

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

@@ -0,0 +1,36 @@
+---
+name: vercel-firewall-core
+description: "Operate Vercel Firewall controls and policy lifecycle management."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, firewall, core
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Firewall Core
+
+## Purpose
+Operate Vercel Firewall controls and policy lifecycle management.
+
+## 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-flags-cli-workflows/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-flags-cli-workflows
+description: "Automate flag creation, rollout, and cleanup via CLI workflows."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, flags, cli, workflows
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: feature-forge, qa-automation-engineer, monitoring-expert
+---
+
+# Vercel Flags Cli Workflows
+
+## Purpose
+Automate flag creation, rollout, and cleanup via CLI workflows.
+
+## When To Use
+- Vercel platform changes in the `flags` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define rollout cohorts and success/failure metrics before toggling flags.
+2. Implement flag evaluation boundaries close to request decision points.
+3. Test override and fallback behavior for each environment.
+4. Plan cleanup path for stale flags and expired experiments.
+
+## 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-flags-dashboard/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-flags-dashboard
+description: "Manage Flags entities, targeting segments, and draft/publish lifecycle."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, flags, dashboard
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: feature-forge, qa-automation-engineer, monitoring-expert
+---
+
+# Vercel Flags Dashboard
+
+## Purpose
+Manage Flags entities, targeting segments, and draft/publish lifecycle.
+
+## When To Use
+- Vercel platform changes in the `flags` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define rollout cohorts and success/failure metrics before toggling flags.
+2. Implement flag evaluation boundaries close to request decision points.
+3. Test override and fallback behavior for each environment.
+4. Plan cleanup path for stale flags and expired experiments.
+
+## 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-flags-explorer/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-flags-explorer
+description: "Use Flags Explorer and local overrides for safe experiment debugging."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, flags, explorer
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: feature-forge, qa-automation-engineer, monitoring-expert
+---
+
+# Vercel Flags Explorer
+
+## Purpose
+Use Flags Explorer and local overrides for safe experiment debugging.
+
+## When To Use
+- Vercel platform changes in the `flags` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define rollout cohorts and success/failure metrics before toggling flags.
+2. Implement flag evaluation boundaries close to request decision points.
+3. Test override and fallback behavior for each environment.
+4. Plan cleanup path for stale flags and expired experiments.
+
+## 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-flags-openfeature/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-flags-openfeature
+description: "Integrate Vercel Flags with OpenFeature-compatible interfaces."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, flags, openfeature
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: feature-forge, qa-automation-engineer, monitoring-expert
+---
+
+# Vercel Flags Openfeature
+
+## Purpose
+Integrate Vercel Flags with OpenFeature-compatible interfaces.
+
+## When To Use
+- Vercel platform changes in the `flags` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define rollout cohorts and success/failure metrics before toggling flags.
+2. Implement flag evaluation boundaries close to request decision points.
+3. Test override and fallback behavior for each environment.
+4. Plan cleanup path for stale flags and expired experiments.
+
+## 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-flags-platform/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-flags-platform
+description: "Operate Vercel Flags as the primary feature flag and rollout system."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, flags, platform
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: feature-forge, qa-automation-engineer, monitoring-expert
+---
+
+# Vercel Flags Platform
+
+## Purpose
+Operate Vercel Flags as the primary feature flag and rollout system.
+
+## When To Use
+- Vercel platform changes in the `flags` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define rollout cohorts and success/failure metrics before toggling flags.
+2. Implement flag evaluation boundaries close to request decision points.
+3. Test override and fallback behavior for each environment.
+4. Plan cleanup path for stale flags and expired experiments.
+
+## 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-flags-sdk/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-flags-sdk
+description: "Implement Vercel Flags SDK in app code with deterministic evaluation."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, flags, sdk
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: feature-forge, qa-automation-engineer, monitoring-expert
+---
+
+# Vercel Flags SDK
+
+## Purpose
+Implement Vercel Flags SDK in app code with deterministic evaluation.
+
+## When To Use
+- Vercel platform changes in the `flags` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define rollout cohorts and success/failure metrics before toggling flags.
+2. Implement flag evaluation boundaries close to request decision points.
+3. Test override and fallback behavior for each environment.
+4. Plan cleanup path for stale flags and expired experiments.
+
+## 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-fluid-compute/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-fluid-compute
+description: "Tune Fluid Compute behavior for latency, concurrency, and cost targets."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, fluid, compute
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Fluid Compute
+
+## Purpose
+Tune Fluid Compute behavior for latency, concurrency, and cost targets.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-function-config/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-function-config
+description: "Set per-function runtime, duration, memory, and region configuration safely."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, function, config
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Function Config
+
+## Purpose
+Set per-function runtime, duration, memory, and region configuration safely.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-functions-core/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-functions-core
+description: "Build and operate Vercel Functions with reliable request lifecycle handling."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, core
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Functions Core
+
+## Purpose
+Build and operate Vercel Functions with reliable request lifecycle handling.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-functions-edge-runtime/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-functions-edge-runtime
+description: "Build on Vercel Edge Runtime with compatibility and performance guardrails."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, edge, runtime
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Functions Edge Runtime
+
+## Purpose
+Build on Vercel Edge Runtime with compatibility and performance guardrails.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-functions-nodejs/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-functions-nodejs
+description: "Implement Node.js runtime patterns specific to Vercel Functions."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, nodejs
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Functions Nodejs
+
+## Purpose
+Implement Node.js runtime patterns specific to Vercel Functions.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-functions-python/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-functions-python
+description: "Implement Python runtime patterns specific to Vercel Functions."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, python
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Functions Python
+
+## Purpose
+Implement Python runtime patterns specific to Vercel Functions.
+
+## When To Use
+- Vercel platform changes in the `compute` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Choose runtime and region behavior from measurable latency and compatibility needs.
+2. Set duration and memory limits that match workload characteristics.
+3. Validate cold start, steady-state latency, and failure handling paths.
+4. Record runtime constraints and escalation triggers for incidents.
+
+## 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-generated-urls/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-generated-urls
+description: "Handle generated deployment URLs, branch URL behavior, and preview URL policies."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, generated, urls
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Generated Urls
+
+## Purpose
+Handle generated deployment URLs, branch URL behavior, and preview URL policies.
+
+## 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-git-deployments/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-git-deployments
+description: "Manage Git-based deployment flows and production-branch promotion strategy."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, git, deployments
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Git Deployments
+
+## Purpose
+Manage Git-based deployment flows and production-branch promotion strategy.
+
+## 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