@cubis/foundry 0.3.10

package/Ai Agent Workflow/skills/vercel-cache-control-headers/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cache-control-headers
+description: "Apply Cache-Control and related headers for deterministic content freshness."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cache, control, headers
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, web-perf, seo-fundamentals
+---
+
+# Vercel Cache Control Headers
+
+## Purpose
+Apply Cache-Control and related headers for deterministic content freshness.
+
+## When To Use
+- Vercel platform changes in the `cache` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define freshness and consistency targets before setting cache behavior.
+2. Apply headers and routing rules that enforce those targets deterministically.
+3. Test cache hits, misses, and invalidation behavior under repeated requests.
+4. Capture operational guidance for purge and rollback procedures.
+
+## 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-cdn-cache/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cdn-cache
+description: "Design cache behavior across Vercel Edge Network and origin workloads."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cache, cdn
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, web-perf, seo-fundamentals
+---
+
+# Vercel Cdn Cache
+
+## Purpose
+Design cache behavior across Vercel Edge Network and origin workloads.
+
+## When To Use
+- Vercel platform changes in the `cache` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define freshness and consistency targets before setting cache behavior.
+2. Apply headers and routing rules that enforce those targets deterministically.
+3. Test cache hits, misses, and invalidation behavior under repeated requests.
+4. Capture operational guidance for purge and rollback procedures.
+
+## 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-cdn-purging/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cdn-purging
+description: "Run cache purge/invalidation workflows with low blast radius."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cache, cdn, purging
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, web-perf, seo-fundamentals
+---
+
+# Vercel Cdn Purging
+
+## Purpose
+Run cache purge/invalidation workflows with low blast radius.
+
+## When To Use
+- Vercel platform changes in the `cache` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Define freshness and consistency targets before setting cache behavior.
+2. Apply headers and routing rules that enforce those targets deterministically.
+3. Test cache hits, misses, and invalidation behavior under repeated requests.
+4. Capture operational guidance for purge and rollback procedures.
+
+## 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-cli-core/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cli-core
+description: "Use Vercel CLI core commands for deploy, inspect, logs, and diagnostics."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, core
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel Cli Core
+
+## Purpose
+Use Vercel CLI core commands for deploy, inspect, logs, and diagnostics.
+
+## When To Use
+- Vercel platform changes in the `cli` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Authenticate with least-privilege credentials for automation context.
+2. Use idempotent command patterns and explicit environment targeting.
+3. Capture machine-readable output for CI validation and alerting.
+4. Validate failure-path handling and retry behavior.
+
+## 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-cli-flags/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cli-flags
+description: "Manage Vercel Flags lifecycle through CLI-driven workflows."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, flags
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel Cli Flags
+
+## Purpose
+Manage Vercel Flags lifecycle through CLI-driven workflows.
+
+## When To Use
+- Vercel platform changes in the `cli` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Authenticate with least-privilege credentials for automation context.
+2. Use idempotent command patterns and explicit environment targeting.
+3. Capture machine-readable output for CI validation and alerting.
+4. Validate failure-path handling and retry behavior.
+
+## 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-cli-mcp/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cli-mcp
+description: "Use Vercel CLI MCP capabilities for agent and tooling integration."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, mcp
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel Cli MCP
+
+## Purpose
+Use Vercel CLI MCP capabilities for agent and tooling integration.
+
+## When To Use
+- Vercel platform changes in the `cli` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Authenticate with least-privilege credentials for automation context.
+2. Use idempotent command patterns and explicit environment targeting.
+3. Capture machine-readable output for CI validation and alerting.
+4. Validate failure-path handling and retry behavior.
+
+## 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-cli-microfrontends/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cli-microfrontends
+description: "Operate microfrontend-specific CLI workflows and validations."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, microfrontends
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel Cli Microfrontends
+
+## Purpose
+Operate microfrontend-specific CLI workflows and validations.
+
+## When To Use
+- Vercel platform changes in the `cli` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Authenticate with least-privilege credentials for automation context.
+2. Use idempotent command patterns and explicit environment targeting.
+3. Capture machine-readable output for CI validation and alerting.
+4. Validate failure-path handling and retry behavior.
+
+## 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-cli-project-domain-env/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cli-project-domain-env
+description: "Automate project, domain, and environment management via CLI."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, project, domain, env
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel Cli Project Domain Env
+
+## Purpose
+Automate project, domain, and environment management via CLI.
+
+## When To Use
+- Vercel platform changes in the `cli` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Authenticate with least-privilege credentials for automation context.
+2. Use idempotent command patterns and explicit environment targeting.
+3. Capture machine-readable output for CI validation and alerting.
+4. Validate failure-path handling and retry behavior.
+
+## 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-cron-jobs/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-cron-jobs
+description: "Configure and verify scheduled cron jobs with idempotency and retry controls."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, cron, jobs
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Cron Jobs
+
+## Purpose
+Configure and verify scheduled cron jobs with idempotency and retry controls.
+
+## 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-custom-events/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-custom-events
+description: "Track and analyze custom events across frontend and backend contexts."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, custom, events
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Custom Events
+
+## Purpose
+Track and analyze custom events across frontend and backend contexts.
+
+## 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-data-cache-nextjs/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-data-cache-nextjs
+description: "Operate Next.js data cache strategy on Vercel for App Router workloads."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, data, cache, nextjs
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Data Cache Nextjs
+
+## Purpose
+Operate Next.js data cache strategy on Vercel for App Router workloads.
+
+## 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-deployment-promotion/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-deployment-promotion
+description: "Promote deployments safely across environments with rollback-ready controls."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, promotion
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Deployment Promotion
+
+## Purpose
+Promote deployments safely across environments with rollback-ready controls.
+
+## 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-deployment-protection/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-deployment-protection
+description: "Configure deployment protection using auth, passwords, and IP gates."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, deployment, protection
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Deployment Protection
+
+## Purpose
+Configure deployment protection using auth, passwords, and IP gates.
+
+## 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-dns-records/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-dns-records
+description: "Manage DNS records and propagation-sensitive change workflows."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, domains, dns, records
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, server-management, security-reviewer
+---
+
+# Vercel DNS Records
+
+## Purpose
+Manage DNS records and propagation-sensitive change workflows.
+
+## When To Use
+- Vercel platform changes in the `network` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm ownership and DNS authority for each managed domain.
+2. Apply changes with TTL and propagation windows accounted for.
+3. Validate certificate state and endpoint reachability after updates.
+4. Prepare rollback records for every production DNS change.
+
+## 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-domain-ownership-claims/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-domain-ownership-claims
+description: "Handle domain ownership claims and re-verification procedures."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, domains, domain, ownership, claims
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, server-management, security-reviewer
+---
+
+# Vercel Domain Ownership Claims
+
+## Purpose
+Handle domain ownership claims and re-verification procedures.
+
+## When To Use
+- Vercel platform changes in the `network` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm ownership and DNS authority for each managed domain.
+2. Apply changes with TTL and propagation windows accounted for.
+3. Validate certificate state and endpoint reachability after updates.
+4. Prepare rollback records for every production DNS change.
+
+## 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-domains/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-domains
+description: "Manage custom domain lifecycle: add, assign, verify, and remove."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, domains
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, server-management, security-reviewer
+---
+
+# Vercel Domains
+
+## Purpose
+Manage custom domain lifecycle: add, assign, verify, and remove.
+
+## When To Use
+- Vercel platform changes in the `network` domain.
+- Tasks requiring production-safe rollout and verification evidence.
+- Work that needs explicit Vercel-specific constraints and guardrails.
+
+## Operating Checklist
+1. Confirm ownership and DNS authority for each managed domain.
+2. Apply changes with TTL and propagation windows accounted for.
+3. Validate certificate state and endpoint reachability after updates.
+4. Prepare rollback records for every production DNS change.
+
+## 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-drains-setup/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-drains-setup
+description: "Configure drains for exporting telemetry to external observability stacks."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, drains, setup
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Drains Setup
+
+## Purpose
+Configure drains for exporting telemetry to external observability stacks.
+
+## 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-edge-config/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-edge-config
+description: "Use Edge Config for low-latency dynamic config reads at edge locations."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, storage, edge, config
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: database-design, postgres-pro, server-management
+---
+
+# Vercel Edge Config
+
+## Purpose
+Use Edge Config for low-latency dynamic config reads at edge locations.
+
+## 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