@cubis/foundry 0.3.10

package/Ai Agent Workflow/skills/vercel-rbac-access-groups/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-rbac-access-groups
+description: "Design RBAC and access-group policy with least-privilege defaults."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, rbac, access, groups
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel RBAC Access Groups
+
+## Purpose
+Design RBAC and access-group policy with least-privilege defaults.
+
+## 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-redirects-rewrites/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-redirects-rewrites
+description: "Implement redirects and rewrites with routing safety and SEO awareness."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cache, redirects, rewrites
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, web-perf, seo-fundamentals
+---
+
+# Vercel Redirects Rewrites
+
+## Purpose
+Implement redirects and rewrites with routing safety and SEO awareness.
+
+## 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-remote-caching/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-remote-caching
+description: "Operate Turborepo remote cache integration and cache-safety controls."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, remote, caching
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, devops-engineer, plan-writing
+---
+
+# Vercel Remote Caching
+
+## Purpose
+Operate Turborepo remote cache integration and cache-safety 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-request-collapsing/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-request-collapsing
+description: "Use request collapsing to protect origins under burst traffic."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cache, request, collapsing
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, web-perf, seo-fundamentals
+---
+
+# Vercel Request Collapsing
+
+## Purpose
+Use request collapsing to protect origins under burst traffic.
+
+## 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-rest-api/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-rest-api
+description: "Automate Vercel operations through REST APIs with robust error handling."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, rest, api
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel Rest API
+
+## Purpose
+Automate Vercel operations through REST APIs with robust error handling.
+
+## 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-routing-middleware/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-routing-middleware
+description: "Use Routing Middleware for pre-cache control, auth checks, and traffic shaping."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, routing, middleware
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Routing Middleware
+
+## Purpose
+Use Routing Middleware for pre-cache control, auth checks, and traffic shaping.
+
+## 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-runtime-cache/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-runtime-cache
+description: "Apply runtime cache policies with freshness and correctness guarantees."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, functions, runtime, cache
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
+---
+
+# Vercel Runtime Cache
+
+## Purpose
+Apply runtime cache policies with freshness and correctness guarantees.
+
+## 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-runtime-logs/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-runtime-logs
+description: "Query and triage runtime logs for incident diagnosis and regression detection."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, runtime, logs
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Runtime Logs
+
+## Purpose
+Query and triage runtime logs for incident diagnosis and regression detection.
+
+## 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-sdk/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-sdk
+description: "Build internal automation using Vercel SDK abstractions."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, cli, sdk
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: powershell-windows, bash-linux, devops-engineer
+---
+
+# Vercel SDK
+
+## Purpose
+Build internal automation using Vercel SDK abstractions.
+
+## 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-secure-compute/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-secure-compute
+description: "Configure Secure Compute and private network access patterns."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, secure, compute
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Secure Compute
+
+## Purpose
+Configure Secure Compute and private network access patterns.
+
+## 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-session-tracing/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-session-tracing
+description: "Capture and inspect session traces to debug real user request paths."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, session, tracing
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Session Tracing
+
+## Purpose
+Capture and inspect session traces to debug real user request paths.
+
+## 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-speed-insights/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-speed-insights
+description: "Use Speed Insights to improve Core Web Vitals and render performance."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, speed, insights
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Speed Insights
+
+## Purpose
+Use Speed Insights to improve Core Web Vitals and render performance.
+
+## 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-ssl-certificates/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-ssl-certificates
+description: "Operate SSL certificate provisioning, renewal, and incident response."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, domains, ssl, certificates
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, server-management, security-reviewer
+---
+
+# Vercel SSL Certificates
+
+## Purpose
+Operate SSL certificate provisioning, renewal, and incident response.
+
+## 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-static-ips/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-static-ips
+description: "Use static egress IPs for partner allowlists and controlled outbound paths."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, static, ips
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel Static Ips
+
+## Purpose
+Use static egress IPs for partner allowlists and controlled outbound paths.
+
+## 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-storage-migrations/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-storage-migrations
+description: "Plan migrations from legacy Vercel storage offerings with minimal downtime."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, storage, migrations
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: database-design, postgres-pro, server-management
+---
+
+# Vercel Storage Migrations
+
+## Purpose
+Plan migrations from legacy Vercel storage offerings with minimal downtime.
+
+## 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-tracing-otel/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-tracing-otel
+description: "Instrument and analyze traces with OpenTelemetry on Vercel."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, tracing, otel
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, error-ux-observability
+---
+
+# Vercel Tracing OTEL
+
+## Purpose
+Instrument and analyze traces with OpenTelemetry on Vercel.
+
+## 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-waf-custom-rules/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-waf-custom-rules
+description: "Author and tune custom WAF rules for exploit and abuse patterns."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, waf, custom, rules
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel WAF Custom Rules
+
+## Purpose
+Author and tune custom WAF rules for exploit and abuse patterns.
+
+## 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-waf-rate-limiting/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: vercel-waf-rate-limiting
+description: "Apply rate-limiting strategy to protect expensive or sensitive endpoints."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, security, waf, rate, limiting
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: security-reviewer, secure-code-guardian, devops-engineer
+---
+
+# Vercel WAF Rate Limiting
+
+## Purpose
+Apply rate-limiting strategy to protect expensive or sensitive endpoints.
+
+## 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