@cubis/foundry 0.3.11 → 0.3.13

package/Ai Agent Workflow/skills/vercel-marketplace-storage-postgres/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-marketplace-storage-postgres
-description: "Operate Vercel Marketplace Postgres integrations and connection patterns."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, storage, marketplace, postgres
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: database-design, postgres-pro, server-management
----
-
-# Vercel Marketplace Storage Postgres
-
-## Purpose
-Operate Vercel Marketplace Postgres integrations and connection 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-marketplace-storage-redis/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-marketplace-storage-redis
-description: "Operate Vercel Marketplace Redis/KV integrations and caching patterns."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, storage, marketplace, redis
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: database-design, postgres-pro, server-management
----
-
-# Vercel Marketplace Storage Redis
-
-## Purpose
-Operate Vercel Marketplace Redis/KV integrations and caching 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-mcp-for-agents/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-mcp-for-agents
-description: "Build and deploy MCP patterns for agent-compatible Vercel workflows."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, ai, mcp, for, agents
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian
----
-
-# Vercel MCP For Agents
-
-## Purpose
-Build and deploy MCP patterns for agent-compatible Vercel workflows.
-
-## 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-microfrontends/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-microfrontends
-description: "Implement Vercel microfrontend composition, routing, and release coordination."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, deployment, microfrontends
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, devops-engineer, plan-writing
----
-
-# Vercel Microfrontends
-
-## Purpose
-Implement Vercel microfrontend composition, routing, and release coordination.
-
-## 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-monorepos/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-monorepos
-description: "Implement monorepo project linking, build isolation, and environment boundaries."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, deployment, monorepos
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, devops-engineer, plan-writing
----
-
-# Vercel Monorepos
-
-## Purpose
-Implement monorepo project linking, build isolation, and environment boundaries.
-
-## 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-multi-tenant/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-multi-tenant
-description: "Design multi-tenant Vercel architectures with domain and isolation controls."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, deployment, multi, tenant
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, devops-engineer, plan-writing
----
-
-# Vercel Multi Tenant
-
-## Purpose
-Design multi-tenant Vercel architectures with domain and isolation 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-nameservers/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-nameservers
-description: "Operate nameserver delegation and authoritative DNS strategy."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, domains, nameservers
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: devops-engineer, server-management, security-reviewer
----
-
-# Vercel Nameservers
-
-## Purpose
-Operate nameserver delegation and authoritative DNS strategy.
-
-## 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-observability-overview/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-observability-overview
-description: "Build complete observability baselines across logs, traces, and analytics."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, observability, overview
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: monitoring-expert, sre-engineer, error-ux-observability
----
-
-# Vercel Observability Overview
-
-## Purpose
-Build complete observability baselines across logs, traces, and analytics.
-
-## 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-og-image-generation/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-og-image-generation
-description: "Generate social preview images with @vercel/og and edge-safe rendering."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, functions, og, image, generation
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, nodejs-best-practices, devops-engineer
----
-
-# Vercel Og Image Generation
-
-## Purpose
-Generate social preview images with @vercel/og and edge-safe rendering.
-
-## 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-oidc-federation/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-oidc-federation
-description: "Implement OIDC federation for short-lived cloud credentials on Vercel."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, security, oidc, federation
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: security-reviewer, secure-code-guardian, devops-engineer
----
-
-# Vercel OIDC Federation
-
-## Purpose
-Implement OIDC federation for short-lived cloud credentials on Vercel.
-
-## 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-project-configuration/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-project-configuration
-description: "Configure Vercel project behavior through vercel.json and project-level settings."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, deployment, project, configuration
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, devops-engineer, plan-writing
----
-
-# Vercel Project Configuration
-
-## Purpose
-Configure Vercel project behavior through vercel.json and project-level settings.
-
-## 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-protection-bypass-automation/SKILL.md

@@ -1,36 +0,0 @@
----
-name: vercel-protection-bypass-automation
-description: "Design controlled bypass automation for CI and E2E workloads."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, security, protection, bypass, automation
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: security-reviewer, secure-code-guardian, devops-engineer
----
-
-# Vercel Protection Bypass Automation
-
-## Purpose
-Design controlled bypass automation for CI and E2E workloads.
-
-## 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-rbac-access-groups/SKILL.md

@@ -1,36 +0,0 @@
----
-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

@@ -1,36 +0,0 @@
----
-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

@@ -1,36 +0,0 @@
----
-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

@@ -1,36 +0,0 @@
----
-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

@@ -1,36 +0,0 @@
----
-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

@@ -1,36 +0,0 @@
----
-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