@cubis/foundry 0.3.32 → 0.3.34

package/workflows/powers/vercel-ai-gateway/SKILL.md

@@ -1,79 +1,21 @@
 ---
 name: vercel-ai-gateway
-description: "Complete Vercel AI Gateway integration: LLM traffic routing, authentication/BYOK, fallback chains, model-provider routing policies, usage observability, and OpenAI-compatible endpoints."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-ai."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, ai, gateway, llm, byok, fallback, model routing, openai compatible, token usage, ai observability
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian, vercel-observability
-  consolidates: vercel-ai-gateway-core, vercel-ai-gateway-auth-byok, vercel-ai-gateway-fallbacks, vercel-ai-gateway-model-routing, vercel-ai-gateway-observability, vercel-ai-gateway-openai-compatible
+  deprecated: true
+  replaced_by: vercel-ai
+  removal_target: v0.6.0
 ---
 
-# Vercel AI Gateway
+# Vercel Ai Gateway
 
-## Purpose
+## Compatibility Alias
 
-Route LLM traffic through Vercel AI Gateway with unified controls covering authentication, model-provider routing, resilient fallback chains, usage observability, and OpenAI-compatible endpoint compatibility.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-ai` as the canonical skill.
 
-- Routing AI/LLM requests through Vercel's managed gateway.
-- Configuring bring-your-own-key (BYOK) authentication for AI providers.
-- Implementing retries and fallback chains for resilient AI responses.
-- Designing model and provider routing policies for latency, quality, and cost.
-- Monitoring AI Gateway usage, latency, and spend.
-- Using OpenAI-compatible endpoints without provider lock-in.
+## Migration
 
-## Domain Areas
-
-### Core Routing
-
-- Define unified gateway endpoint and routing config.
-- Set per-model quality, latency, and cost objectives.
-
-### Authentication & BYOK
-
-- Configure provider API key management and BYOK controls.
-- Scope key access per project/environment.
-
-### Fallbacks & Resilience
-
-- Implement retry policies and fallback provider chains.
-- Define circuit-breaker thresholds.
-
-### Model Routing Policies
-
-- Route by latency, cost, capability, or custom weights.
-- Support multi-provider and multi-region strategies.
-
-### Observability
-
-- Instrument token usage, latency, and error rates per model.
-- Set spend thresholds and alerting.
-
-### OpenAI Compatibility
-
-- Use OpenAI-compatible request/response format.
-- Migrate between providers without application changes.
-
-## Operating Checklist
-
-1. Define model quality, latency, and cost objectives for each endpoint.
-2. Configure authentication and BYOK key scoping per environment.
-3. Implement routing, fallback, and retry policies explicitly.
-4. Instrument token usage, latency, and error classes for all calls.
-5. Validate OpenAI-compatible endpoint compatibility if needed.
-6. Run safety and regression checks before broad rollout.
-
-## Output Contract
-
-- Proposed routing and authentication architecture with tradeoffs
-- Required config, code, and environment changes
-- Fallback chain definition and circuit-breaker settings
-- Validation evidence (spend limits, latency targets, error budgets)
-- Residual risks and follow-up actions
+1. Replace direct references to `vercel-ai-gateway` with `vercel-ai`.
+2. Apply the full workflow from `vercel-ai` for new work.

package/workflows/powers/vercel-ai-sdk/POWER.md

@@ -2,61 +2,23 @@
 ---
 inclusion: manual
 name: vercel-ai-sdk
-description: "Vercel AI SDK for building AI-powered applications: core providers/streaming patterns and React/Svelte UI hooks for chat, completion, and generative UX."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-ai."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, ai sdk, useChat, useCompletion, streamText, generateText, ai ui, streaming, generative ui
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: react-expert, nextjs-developer, prompt-engineer, vercel-ai-gateway
-  consolidates: vercel-ai-sdk-core, vercel-ai-sdk-ui
+  deprecated: true
+  replaced_by: vercel-ai
+  removal_target: v0.6.0
 ---
 
-# Vercel AI SDK
+# Vercel Ai Sdk
 
-## Purpose
+## Compatibility Alias
 
-Build AI-powered applications with Vercel AI SDK covering core provider integration, streaming primitives, and framework UI hooks for chat, completion, and generative interfaces.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-ai` as the canonical skill.
 
-- Integrating LLM providers (OpenAI, Anthropic, Google, etc.) via unified SDK.
-- Streaming text, objects, or tool calls from the server to the client.
-- Building chat or completion UIs with `useChat` / `useCompletion` hooks.
-- Implementing generative UI and multi-step agent flows.
+## Migration
 
-## Domain Areas
-
-### Core (Provider & Streaming)
-
-- Configure providers with `createOpenAI`, `createAnthropic`, etc.
-- Use `streamText`, `generateText`, `streamObject`, `generateObject`.
-- Handle tool calls, multi-step flows, and error recovery.
-
-### UI Hooks (React / Svelte / Vue)
-
-- `useChat`: managed chat history, streaming, form submission.
-- `useCompletion`: single-prompt streaming completions.
-- `useAssistant`: OpenAI Assistants API integration.
-- Attach metadata, handle events, and control abort signals.
-
-## Operating Checklist
-
-1. Select and configure the appropriate provider.
-2. Choose streaming vs. non-streaming based on UX requirements.
-3. Implement error handling and loading states in UI hooks.
-4. Validate type safety of generated objects with schema validation.
-5. Test streaming under latency and partial-response conditions.
-
-## Output Contract
-
-- Provider configuration and env var requirements
-- Stream handler and UI hook implementation
-- Tool call schemas and multi-step flow definitions
-- Error and abort handling patterns
-- Validation evidence and rollback notes
+1. Replace direct references to `vercel-ai-sdk` with `vercel-ai`.
+2. Apply the full workflow from `vercel-ai` for new work.
 ````

package/workflows/powers/vercel-ai-sdk/SKILL.md

@@ -1,59 +1,21 @@
 ---
 name: vercel-ai-sdk
-description: "Vercel AI SDK for building AI-powered applications: core providers/streaming patterns and React/Svelte UI hooks for chat, completion, and generative UX."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-ai."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, ai sdk, useChat, useCompletion, streamText, generateText, ai ui, streaming, generative ui
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: react-expert, nextjs-developer, prompt-engineer, vercel-ai-gateway
-  consolidates: vercel-ai-sdk-core, vercel-ai-sdk-ui
+  deprecated: true
+  replaced_by: vercel-ai
+  removal_target: v0.6.0
 ---
 
-# Vercel AI SDK
+# Vercel Ai Sdk
 
-## Purpose
+## Compatibility Alias
 
-Build AI-powered applications with Vercel AI SDK covering core provider integration, streaming primitives, and framework UI hooks for chat, completion, and generative interfaces.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-ai` as the canonical skill.
 
-- Integrating LLM providers (OpenAI, Anthropic, Google, etc.) via unified SDK.
-- Streaming text, objects, or tool calls from the server to the client.
-- Building chat or completion UIs with `useChat` / `useCompletion` hooks.
-- Implementing generative UI and multi-step agent flows.
+## Migration
 
-## Domain Areas
-
-### Core (Provider & Streaming)
-
-- Configure providers with `createOpenAI`, `createAnthropic`, etc.
-- Use `streamText`, `generateText`, `streamObject`, `generateObject`.
-- Handle tool calls, multi-step flows, and error recovery.
-
-### UI Hooks (React / Svelte / Vue)
-
-- `useChat`: managed chat history, streaming, form submission.
-- `useCompletion`: single-prompt streaming completions.
-- `useAssistant`: OpenAI Assistants API integration.
-- Attach metadata, handle events, and control abort signals.
-
-## Operating Checklist
-
-1. Select and configure the appropriate provider.
-2. Choose streaming vs. non-streaming based on UX requirements.
-3. Implement error handling and loading states in UI hooks.
-4. Validate type safety of generated objects with schema validation.
-5. Test streaming under latency and partial-response conditions.
-
-## Output Contract
-
-- Provider configuration and env var requirements
-- Stream handler and UI hook implementation
-- Tool call schemas and multi-step flow definitions
-- Error and abort handling patterns
-- Validation evidence and rollback notes
+1. Replace direct references to `vercel-ai-sdk` with `vercel-ai`.
+2. Apply the full workflow from `vercel-ai` for new work.

package/workflows/powers/vercel-caching/POWER.md

@@ -2,85 +2,23 @@
 ---
 inclusion: manual
 name: vercel-caching
-description: "Vercel caching strategies: CDN cache, cache-control headers, runtime cache, ISR, Next.js Data Cache, request collapsing, remote caching (Turborepo), and CDN purging."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, cdn cache, caching, isr, incremental static regeneration, data cache, request collapsing, remote caching, turborepo cache, cache purge, stale-while-revalidate, cache-control
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-functions, vercel-routing, web-perf
-  consolidates: vercel-cdn-cache, vercel-cdn-purging, vercel-cache-control-headers, vercel-runtime-cache, vercel-isr, vercel-data-cache-nextjs, vercel-request-collapsing, vercel-remote-caching
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Caching
 
-## Purpose
+## Compatibility Alias
 
-Implement and tune Vercel's full caching stack to maximize performance and reduce origin load, including CDN edge caching, ISR, Next.js Data Cache, request collapsing, and Turborepo remote caching.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Setting cache-control headers and CDN TTL for static/dynamic assets.
-- Configuring ISR revalidation periods and on-demand revalidation.
-- Using Next.js Data Cache (`fetch` caching, `unstable_cache`).
-- Purging CDN cache after deploys or content updates.
-- Enabling request collapsing to prevent cache stampedes.
-- Setting up Turborepo remote caching for faster CI.
+## Migration
 
-## Domain Areas
-
-### CDN Cache & Cache-Control
-
-- Set `Cache-Control: s-maxage`, `stale-while-revalidate` headers.
-- Configure edge cache TTL per route in `vercel.json`.
-- Understand Vercel's cache key construction.
-
-### CDN Purging
-
-- On-demand cache invalidation via Vercel dashboard or REST API.
-- Tag-based purge strategies for content updates.
-
-### ISR (Incremental Static Regeneration)
-
-- Configure `revalidate` in Next.js page/route handlers.
-- On-demand revalidation with `revalidatePath` / `revalidateTag`.
-- ISR fallback behavior and error handling.
-
-### Next.js Data Cache
-
-- `fetch` cache with `cache`, `next.revalidate`, `next.tags` options.
-- `unstable_cache` for non-fetch data sources.
-- Cache invalidation with `revalidateTag`.
-
-### Request Collapsing
-
-- Enable to coalesce concurrent cache-miss requests.
-- Validate behavior under load with simulated stampedes.
-
-### Remote Caching (Turborepo)
-
-- Configure Vercel Remote Cache for Turborepo.
-- Authenticate with `TURBO_TOKEN` and `TURBO_TEAM`.
-- Monitor cache hit rates and artifact sizes.
-
-## Operating Checklist
-
-1. Audit current cache-control headers and TTL values.
-2. Define caching strategy per route type (static, dynamic, API).
-3. Implement ISR or Data Cache with explicit revalidation tags.
-4. Set up cache purge automation for content updates.
-5. Enable and validate request collapsing in staging under load.
-6. Configure Turborepo remote caching and verify hit rates in CI.
-
-## Output Contract
-
-- Cache-control header strategy per route type
-- ISR/Data Cache configuration with revalidation tags
-- CDN purge automation plan and trigger events
-- Turborepo remote cache setup instructions
-- Performance validation (cache hit ratios, TTFB targets)
+1. Replace direct references to `vercel-caching` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.
 ````

package/workflows/powers/vercel-caching/SKILL.md

@@ -1,83 +1,21 @@
 ---
 name: vercel-caching
-description: "Vercel caching strategies: CDN cache, cache-control headers, runtime cache, ISR, Next.js Data Cache, request collapsing, remote caching (Turborepo), and CDN purging."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, cdn cache, caching, isr, incremental static regeneration, data cache, request collapsing, remote caching, turborepo cache, cache purge, stale-while-revalidate, cache-control
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-functions, vercel-routing, web-perf
-  consolidates: vercel-cdn-cache, vercel-cdn-purging, vercel-cache-control-headers, vercel-runtime-cache, vercel-isr, vercel-data-cache-nextjs, vercel-request-collapsing, vercel-remote-caching
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Caching
 
-## Purpose
+## Compatibility Alias
 
-Implement and tune Vercel's full caching stack to maximize performance and reduce origin load, including CDN edge caching, ISR, Next.js Data Cache, request collapsing, and Turborepo remote caching.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Setting cache-control headers and CDN TTL for static/dynamic assets.
-- Configuring ISR revalidation periods and on-demand revalidation.
-- Using Next.js Data Cache (`fetch` caching, `unstable_cache`).
-- Purging CDN cache after deploys or content updates.
-- Enabling request collapsing to prevent cache stampedes.
-- Setting up Turborepo remote caching for faster CI.
+## Migration
 
-## Domain Areas
-
-### CDN Cache & Cache-Control
-
-- Set `Cache-Control: s-maxage`, `stale-while-revalidate` headers.
-- Configure edge cache TTL per route in `vercel.json`.
-- Understand Vercel's cache key construction.
-
-### CDN Purging
-
-- On-demand cache invalidation via Vercel dashboard or REST API.
-- Tag-based purge strategies for content updates.
-
-### ISR (Incremental Static Regeneration)
-
-- Configure `revalidate` in Next.js page/route handlers.
-- On-demand revalidation with `revalidatePath` / `revalidateTag`.
-- ISR fallback behavior and error handling.
-
-### Next.js Data Cache
-
-- `fetch` cache with `cache`, `next.revalidate`, `next.tags` options.
-- `unstable_cache` for non-fetch data sources.
-- Cache invalidation with `revalidateTag`.
-
-### Request Collapsing
-
-- Enable to coalesce concurrent cache-miss requests.
-- Validate behavior under load with simulated stampedes.
-
-### Remote Caching (Turborepo)
-
-- Configure Vercel Remote Cache for Turborepo.
-- Authenticate with `TURBO_TOKEN` and `TURBO_TEAM`.
-- Monitor cache hit rates and artifact sizes.
-
-## Operating Checklist
-
-1. Audit current cache-control headers and TTL values.
-2. Define caching strategy per route type (static, dynamic, API).
-3. Implement ISR or Data Cache with explicit revalidation tags.
-4. Set up cache purge automation for content updates.
-5. Enable and validate request collapsing in staging under load.
-6. Configure Turborepo remote caching and verify hit rates in CI.
-
-## Output Contract
-
-- Cache-control header strategy per route type
-- ISR/Data Cache configuration with revalidation tags
-- CDN purge automation plan and trigger events
-- Turborepo remote cache setup instructions
-- Performance validation (cache hit ratios, TTFB targets)
+1. Replace direct references to `vercel-caching` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.

package/workflows/powers/vercel-cli/POWER.md

@@ -2,87 +2,23 @@
 ---
 inclusion: manual
 name: vercel-cli
-description: "Vercel CLI mastery: core commands, flags, MCP integration, microfrontend management, and project/domain/environment variable operations from the command line."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-delivery."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel cli, vercel command, npx vercel, vercel dev, vercel deploy, vercel env, vercel domains cli, vercel pull, vercel link, vercel mcp, vercel microfrontends cli
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: devops-engineer, wrangler, vercel-deployments, vercel-domains
-  consolidates: vercel-cli-core, vercel-cli-flags, vercel-cli-mcp, vercel-cli-microfrontends, vercel-cli-project-domain-env
+  deprecated: true
+  replaced_by: vercel-delivery
+  removal_target: v0.6.0
 ---
 
-# Vercel CLI
+# Vercel Cli
 
-## Purpose
+## Compatibility Alias
 
-Use the Vercel CLI for local development, deployments, environment management, domain operations, microfrontend orchestration, and MCP-based automation workflows.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-delivery` as the canonical skill.
 
-- Running `vercel dev` for local development with edge function support.
-- Deploying with `vercel --prod` or `vercel deploy` from CI/CD.
-- Managing environment variables with `vercel env add/pull/rm`.
-- Managing domains and DNS with `vercel domains`.
-- Linking, inspecting, and managing project config with `vercel link`.
-- Using the Vercel MCP for agent-based CLI automation.
-- Managing microfrontend apps from the CLI.
+## Migration
 
-## Domain Areas
-
-### Core Commands
-
-| Command                    | Purpose                                    |
-| -------------------------- | ------------------------------------------ |
-| `vercel` / `vercel deploy` | Deploy current directory                   |
-| `vercel --prod`            | Deploy to production                       |
-| `vercel dev`               | Local dev server with edge emulation       |
-| `vercel build`             | Build locally (mirrors Vercel cloud build) |
-| `vercel inspect <url>`     | Inspect deployment details                 |
-| `vercel rollback`          | Instant rollback to previous deployment    |
-| `vercel link`              | Link local directory to Vercel project     |
-| `vercel pull`              | Pull project settings and env vars locally |
-
-### Flags
-
-- `--env`, `--build-env`, `--token`, `--scope`, `--yes`, `--no-wait`.
-- `--regions` for targeted regional deployment.
-- `--archive=tgz` for artifact-based deployments.
-
-### Project / Domain / Env
-
-- `vercel env add/pull/rm` — manage environment variables.
-- `vercel domains add/rm/inspect` — domain management.
-- `vercel alias set <url> <alias>` — assign deployment aliases.
-
-### MCP Integration
-
-- Use Vercel MCP server for agent-driven CLI automation.
-- Query deployment state, logs, and project config programmatically.
-
-### Microfrontends
-
-- `vercel microfrontends` commands for app group management.
-- Register and route microfrontend applications from CLI.
-
-## Operating Checklist
-
-1. Authenticate with `vercel login` and verify scope with `vercel whoami`.
-2. Link project with `vercel link` before running local commands.
-3. Pull env vars with `vercel env pull .env.local` for local dev.
-4. Use `vercel build` to validate build output before deploying.
-5. Automate deployments in CI with `--token` and `--yes` flags.
-6. Use `vercel rollback` as the immediate incident response action.
-
-## Output Contract
-
-- CLI authentication and project linking steps
-- Environment variable management workflow
-- CI/CD pipeline CLI integration commands
-- Relevant flags and flags rationale
-- Rollback procedure and verification steps
+1. Replace direct references to `vercel-cli` with `vercel-delivery`.
+2. Apply the full workflow from `vercel-delivery` for new work.
 ````

package/workflows/powers/vercel-cli/SKILL.md

@@ -1,85 +1,21 @@
 ---
 name: vercel-cli
-description: "Vercel CLI mastery: core commands, flags, MCP integration, microfrontend management, and project/domain/environment variable operations from the command line."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-delivery."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel cli, vercel command, npx vercel, vercel dev, vercel deploy, vercel env, vercel domains cli, vercel pull, vercel link, vercel mcp, vercel microfrontends cli
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: devops-engineer, wrangler, vercel-deployments, vercel-domains
-  consolidates: vercel-cli-core, vercel-cli-flags, vercel-cli-mcp, vercel-cli-microfrontends, vercel-cli-project-domain-env
+  deprecated: true
+  replaced_by: vercel-delivery
+  removal_target: v0.6.0
 ---
 
-# Vercel CLI
+# Vercel Cli
 
-## Purpose
+## Compatibility Alias
 
-Use the Vercel CLI for local development, deployments, environment management, domain operations, microfrontend orchestration, and MCP-based automation workflows.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-delivery` as the canonical skill.
 
-- Running `vercel dev` for local development with edge function support.
-- Deploying with `vercel --prod` or `vercel deploy` from CI/CD.
-- Managing environment variables with `vercel env add/pull/rm`.
-- Managing domains and DNS with `vercel domains`.
-- Linking, inspecting, and managing project config with `vercel link`.
-- Using the Vercel MCP for agent-based CLI automation.
-- Managing microfrontend apps from the CLI.
+## Migration
 
-## Domain Areas
-
-### Core Commands
-
-| Command                    | Purpose                                    |
-| -------------------------- | ------------------------------------------ |
-| `vercel` / `vercel deploy` | Deploy current directory                   |
-| `vercel --prod`            | Deploy to production                       |
-| `vercel dev`               | Local dev server with edge emulation       |
-| `vercel build`             | Build locally (mirrors Vercel cloud build) |
-| `vercel inspect <url>`     | Inspect deployment details                 |
-| `vercel rollback`          | Instant rollback to previous deployment    |
-| `vercel link`              | Link local directory to Vercel project     |
-| `vercel pull`              | Pull project settings and env vars locally |
-
-### Flags
-
-- `--env`, `--build-env`, `--token`, `--scope`, `--yes`, `--no-wait`.
-- `--regions` for targeted regional deployment.
-- `--archive=tgz` for artifact-based deployments.
-
-### Project / Domain / Env
-
-- `vercel env add/pull/rm` — manage environment variables.
-- `vercel domains add/rm/inspect` — domain management.
-- `vercel alias set <url> <alias>` — assign deployment aliases.
-
-### MCP Integration
-
-- Use Vercel MCP server for agent-driven CLI automation.
-- Query deployment state, logs, and project config programmatically.
-
-### Microfrontends
-
-- `vercel microfrontends` commands for app group management.
-- Register and route microfrontend applications from CLI.
-
-## Operating Checklist
-
-1. Authenticate with `vercel login` and verify scope with `vercel whoami`.
-2. Link project with `vercel link` before running local commands.
-3. Pull env vars with `vercel env pull .env.local` for local dev.
-4. Use `vercel build` to validate build output before deploying.
-5. Automate deployments in CI with `--token` and `--yes` flags.
-6. Use `vercel rollback` as the immediate incident response action.
-
-## Output Contract
-
-- CLI authentication and project linking steps
-- Environment variable management workflow
-- CI/CD pipeline CLI integration commands
-- Relevant flags and flags rationale
-- Rollback procedure and verification steps
+1. Replace direct references to `vercel-cli` with `vercel-delivery`.
+2. Apply the full workflow from `vercel-delivery` for new work.

package/workflows/powers/vercel-delivery/POWER.md

@@ -0,0 +1,45 @@
+````markdown
+---
+inclusion: manual
+name: vercel-delivery
+description: "Canonical Vercel delivery skill covering deployments, domains, flags, and CLI-driven release operations."
+metadata:
+  deprecated: false
+  replaced_by: null
+  removal_target: null
+---
+
+# Vercel Delivery
+
+## Purpose
+
+Run reliable Vercel release operations end-to-end: build/deploy lifecycle, environment promotion, domain management, feature-flag rollout, and CLI automation.
+
+## Use This For
+
+- Deployment pipelines and promotion policy
+- Preview/production environment controls
+- Custom domains, DNS/SSL readiness
+- Controlled rollouts with feature flags
+- Vercel CLI operational workflows
+
+## Decision Flow
+
+1. Lock release target and rollback checkpoint.
+2. Choose rollout strategy (direct, staged, flag-gated).
+3. Verify domain/certificate/environment integrity.
+4. Execute release with post-deploy checks.
+
+## Verification
+
+- Deployment health is green in target environment.
+- Domain resolution and TLS are valid.
+- Rollback command/path is tested and documented.
+
+## Related Skills
+
+- `vercel-platform`
+- `vercel-runtime`
+- `vercel-security`
+- `devops-engineer`
+````