@cubis/foundry 0.3.31 → 0.3.33

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

@@ -2,75 +2,23 @@
 ---
 inclusion: manual
 name: vercel-flags
-description: "Vercel Feature Flags: SDK integration, platform setup, CLI workflows, dashboard management, explorer UI, and OpenFeature compatibility for safe, targeted rollouts."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-delivery."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, feature flags, flags sdk, flags platform, openfeature, flags dashboard, flags explorer, feature toggle, rollout, a/b test
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-deployments, vercel-cli
-  consolidates: vercel-flags-platform, vercel-flags-sdk, vercel-flags-cli-workflows, vercel-flags-dashboard, vercel-flags-explorer, vercel-flags-openfeature
+  deprecated: true
+  replaced_by: vercel-delivery
+  removal_target: v0.6.0
 ---
 
 # Vercel Flags
 
-## Purpose
+## Compatibility Alias
 
-Implement Vercel Feature Flags end-to-end: platform configuration, SDK integration in application code, CLI management workflows, dashboard visibility, explorer UX for teams, and OpenFeature provider compatibility.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-delivery` as the canonical skill.
 
-- Setting up feature flags on Vercel platform.
-- Integrating `@vercel/flags` SDK into Next.js or other frameworks.
-- Managing flags via CLI for automated rollout pipelines.
-- Using the Flags Dashboard or Explorer for team visibility.
-- Implementing OpenFeature-compatible providers for portability.
+## Migration
 
-## Domain Areas
-
-### Platform Setup
-
-- Configure flag definitions and environments in Vercel dashboard.
-- Assign targeting rules, rollout percentages, and user segments.
-
-### SDK Integration
-
-- Install `@vercel/flags` and configure provider.
-- Use `unstable_flag`, `flag()`, and edge-compatible evaluation.
-- Integrate with Next.js middleware and React Server Components.
-
-### CLI Workflows
-
-- `vercel flags ls`, `vercel flags pull`, `vercel flags push`.
-- Automate flag state changes in CI/CD pipelines.
-
-### Dashboard & Explorer
-
-- Monitor flag state, overrides, and exposure metrics.
-- Use the Toolbar and Explorer for local override during development.
-
-### OpenFeature Compatibility
-
-- Register Vercel as an OpenFeature provider.
-- Maintain provider-agnostic flag evaluation logic.
-
-## Operating Checklist
-
-1. Define flag schema and targeting rules before implementation.
-2. Integrate SDK with appropriate edge/server evaluation context.
-3. Implement safe defaults for all flags (fail-closed).
-4. Validate flag exposure in dashboard before broad rollout.
-5. Automate flag lifecycle (create, rollout, cleanup) in CI.
-
-## Output Contract
-
-- Flag schema definitions and targeting rule design
-- SDK integration code and Next.js adapter config
-- CLI workflow scripts for CI/CD pipelines
-- Dashboard monitoring setup and exposure validation
-- Residual risks and cleanup checklist
+1. Replace direct references to `vercel-flags` with `vercel-delivery`.
+2. Apply the full workflow from `vercel-delivery` for new work.
 ````

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

@@ -1,73 +1,21 @@
 ---
 name: vercel-flags
-description: "Vercel Feature Flags: SDK integration, platform setup, CLI workflows, dashboard management, explorer UI, and OpenFeature compatibility for safe, targeted rollouts."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-delivery."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, feature flags, flags sdk, flags platform, openfeature, flags dashboard, flags explorer, feature toggle, rollout, a/b test
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-deployments, vercel-cli
-  consolidates: vercel-flags-platform, vercel-flags-sdk, vercel-flags-cli-workflows, vercel-flags-dashboard, vercel-flags-explorer, vercel-flags-openfeature
+  deprecated: true
+  replaced_by: vercel-delivery
+  removal_target: v0.6.0
 ---
 
 # Vercel Flags
 
-## Purpose
+## Compatibility Alias
 
-Implement Vercel Feature Flags end-to-end: platform configuration, SDK integration in application code, CLI management workflows, dashboard visibility, explorer UX for teams, and OpenFeature provider compatibility.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-delivery` as the canonical skill.
 
-- Setting up feature flags on Vercel platform.
-- Integrating `@vercel/flags` SDK into Next.js or other frameworks.
-- Managing flags via CLI for automated rollout pipelines.
-- Using the Flags Dashboard or Explorer for team visibility.
-- Implementing OpenFeature-compatible providers for portability.
+## Migration
 
-## Domain Areas
-
-### Platform Setup
-
-- Configure flag definitions and environments in Vercel dashboard.
-- Assign targeting rules, rollout percentages, and user segments.
-
-### SDK Integration
-
-- Install `@vercel/flags` and configure provider.
-- Use `unstable_flag`, `flag()`, and edge-compatible evaluation.
-- Integrate with Next.js middleware and React Server Components.
-
-### CLI Workflows
-
-- `vercel flags ls`, `vercel flags pull`, `vercel flags push`.
-- Automate flag state changes in CI/CD pipelines.
-
-### Dashboard & Explorer
-
-- Monitor flag state, overrides, and exposure metrics.
-- Use the Toolbar and Explorer for local override during development.
-
-### OpenFeature Compatibility
-
-- Register Vercel as an OpenFeature provider.
-- Maintain provider-agnostic flag evaluation logic.
-
-## Operating Checklist
-
-1. Define flag schema and targeting rules before implementation.
-2. Integrate SDK with appropriate edge/server evaluation context.
-3. Implement safe defaults for all flags (fail-closed).
-4. Validate flag exposure in dashboard before broad rollout.
-5. Automate flag lifecycle (create, rollout, cleanup) in CI.
-
-## Output Contract
-
-- Flag schema definitions and targeting rule design
-- SDK integration code and Next.js adapter config
-- CLI workflow scripts for CI/CD pipelines
-- Dashboard monitoring setup and exposure validation
-- Residual risks and cleanup checklist
+1. Replace direct references to `vercel-flags` with `vercel-delivery`.
+2. Apply the full workflow from `vercel-delivery` for new work.

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

@@ -2,83 +2,23 @@
 ---
 inclusion: manual
 name: vercel-functions
-description: "Vercel Serverless and Edge Functions: core patterns, Node.js and Python runtimes, edge runtime, Fluid Compute for long-running tasks, and function configuration."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, serverless, functions, edge function, nodejs runtime, python runtime, fluid compute, function config, api route, edge runtime
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nodejs-best-practices, fastapi-expert, vercel-routing, vercel-caching
-  consolidates: vercel-functions-core, vercel-functions-edge-runtime, vercel-functions-nodejs, vercel-functions-python, vercel-function-config, vercel-fluid-compute
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Functions
 
-## Purpose
+## Compatibility Alias
 
-Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Writing Vercel API routes or serverless function handlers.
-- Choosing between Edge Runtime and Node.js runtime.
-- Configuring Python serverless functions on Vercel.
-- Implementing long-running tasks or streaming with Fluid Compute.
-- Tuning function memory, regions, timeout, and concurrency config.
+## Migration
 
-## Domain Areas
-
-### Core Patterns
-
-- Request/response handler structure for Vercel functions.
-- Environment-aware error handling and status codes.
-- Cold start mitigation strategies.
-
-### Node.js Runtime
-
-- Use `@vercel/node` and standard Node.js APIs.
-- Streaming responses with `Response` and `ReadableStream`.
-
-### Python Runtime
-
-- Configure `requirements.txt` and handler conventions.
-- Use WSGI/ASGI adapters where needed.
-
-### Edge Runtime
-
-- Use Web Standard APIs only (no Node.js built-ins).
-- Optimize for global low-latency execution at the edge.
-- Middleware-friendly patterns.
-
-### Fluid Compute
-
-- Enable for long-running tasks exceeding standard limits.
-- Stream output progressively for large responses.
-- Configure max duration and concurrency appropriately.
-
-### Function Config (`vercel.json`)
-
-- Set `runtime`, `regions`, `maxDuration`, `memory` per function.
-- Use `rewrites` to map routes to specific functions.
-
-## Operating Checklist
-
-1. Choose runtime (Edge vs Node.js vs Python) based on latency, API, and duration needs.
-2. Set explicit `maxDuration` and `memory` for non-default requirements.
-3. Implement structured error responses with proper HTTP status codes.
-4. Test cold-start behavior and streaming in staging environment.
-5. Validate regional deployment targets match latency requirements.
-6. Run regression checks before promoting to production.
-
-## Output Contract
-
-- Runtime selection rationale and tradeoffs
-- Handler implementation with error handling and streaming
-- `vercel.json` function config section
-- Performance validation (cold start, p99 latency targets)
-- Residual risks and follow-up actions
+1. Replace direct references to `vercel-functions` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.
 ````

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

@@ -1,81 +1,21 @@
 ---
 name: vercel-functions
-description: "Vercel Serverless and Edge Functions: core patterns, Node.js and Python runtimes, edge runtime, Fluid Compute for long-running tasks, and function configuration."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, serverless, functions, edge function, nodejs runtime, python runtime, fluid compute, function config, api route, edge runtime
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nodejs-best-practices, fastapi-expert, vercel-routing, vercel-caching
-  consolidates: vercel-functions-core, vercel-functions-edge-runtime, vercel-functions-nodejs, vercel-functions-python, vercel-function-config, vercel-fluid-compute
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Functions
 
-## Purpose
+## Compatibility Alias
 
-Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Writing Vercel API routes or serverless function handlers.
-- Choosing between Edge Runtime and Node.js runtime.
-- Configuring Python serverless functions on Vercel.
-- Implementing long-running tasks or streaming with Fluid Compute.
-- Tuning function memory, regions, timeout, and concurrency config.
+## Migration
 
-## Domain Areas
-
-### Core Patterns
-
-- Request/response handler structure for Vercel functions.
-- Environment-aware error handling and status codes.
-- Cold start mitigation strategies.
-
-### Node.js Runtime
-
-- Use `@vercel/node` and standard Node.js APIs.
-- Streaming responses with `Response` and `ReadableStream`.
-
-### Python Runtime
-
-- Configure `requirements.txt` and handler conventions.
-- Use WSGI/ASGI adapters where needed.
-
-### Edge Runtime
-
-- Use Web Standard APIs only (no Node.js built-ins).
-- Optimize for global low-latency execution at the edge.
-- Middleware-friendly patterns.
-
-### Fluid Compute
-
-- Enable for long-running tasks exceeding standard limits.
-- Stream output progressively for large responses.
-- Configure max duration and concurrency appropriately.
-
-### Function Config (`vercel.json`)
-
-- Set `runtime`, `regions`, `maxDuration`, `memory` per function.
-- Use `rewrites` to map routes to specific functions.
-
-## Operating Checklist
-
-1. Choose runtime (Edge vs Node.js vs Python) based on latency, API, and duration needs.
-2. Set explicit `maxDuration` and `memory` for non-default requirements.
-3. Implement structured error responses with proper HTTP status codes.
-4. Test cold-start behavior and streaming in staging environment.
-5. Validate regional deployment targets match latency requirements.
-6. Run regression checks before promoting to production.
-
-## Output Contract
-
-- Runtime selection rationale and tradeoffs
-- Handler implementation with error handling and streaming
-- `vercel.json` function config section
-- Performance validation (cold start, p99 latency targets)
-- Residual risks and follow-up actions
+1. Replace direct references to `vercel-functions` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.

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

@@ -2,81 +2,23 @@
 ---
 inclusion: manual
 name: vercel-routing
-description: "Vercel edge routing: middleware patterns, redirects/rewrites, Edge Config for real-time config without redeploys, Edge Config integrations, and Node.js migration paths."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, routing, middleware, redirects, rewrites, edge config, edge config integrations, edge to node, a/b routing, geo routing, edge middleware
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-functions, vercel-caching, vercel-flags
-  consolidates: vercel-routing-middleware, vercel-redirects-rewrites, vercel-edge-config, vercel-edge-config-integrations, vercel-edge-to-node-migration
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Routing
 
-## Purpose
+## Compatibility Alias
 
-Configure Vercel's edge routing layer with middleware patterns, redirect/rewrite rules, real-time Edge Config for runtime configuration, and migration paths away from the edge runtime.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Writing Vercel Middleware for auth, geo-routing, A/B testing, or bot checks.
-- Configuring redirects and rewrites in `vercel.json` or Next.js config.
-- Using Edge Config for real-time feature toggling or config without redeploys.
-- Integrating Edge Config with third-party providers (LaunchDarkly, etc.).
-- Migrating edge-incompatible middleware to Node.js functions.
+## Migration
 
-## Domain Areas
-
-### Middleware
-
-- Author `middleware.ts` with `NextRequest`/`NextResponse` or Web APIs.
-- Apply auth checks, geo-redirects, A/B bucket assignment.
-- Use `matcher` config to scope execution precisely.
-- Mind cold start and bundle size constraints (1MB limit).
-
-### Redirects & Rewrites
-
-- Configure in `vercel.json` under `redirects` / `rewrites`.
-- Permanent (308) vs temporary (307) redirects.
-- Capture groups and dynamic path rewriting.
-- Header-based and query-based conditional rewrites.
-
-### Edge Config
-
-- Create and populate Edge Config stores via dashboard or CLI.
-- Read in middleware with `@vercel/edge-config` SDK.
-- Zero-redeploy config changes for feature flags and kill switches.
-
-### Edge Config Integrations
-
-- Connect Edge Config to third-party providers.
-- Sync external flag state into Edge Config automatically.
-
-### Edge-to-Node Migration
-
-- Identify middleware using Node.js-incompatible APIs.
-- Refactor to Node.js serverless functions or API routes.
-- Use `runtime: 'nodejs'` config override.
-
-## Operating Checklist
-
-1. Audit middleware bundle size and strip unnecessary dependencies.
-2. Validate matcher patterns cover only intended routes.
-3. Test redirect rules for cyclic redirect risk.
-4. Populate Edge Config with safe defaults before enabling reads.
-5. Document Edge Config keys and owners; restrict write access.
-6. Plan edge-to-node migration with regression test coverage.
-
-## Output Contract
-
-- Middleware implementation with matcher config
-- Redirect/rewrite rule set with conflict analysis
-- Edge Config schema, population scripts, and read integration
-- Edge-to-node migration plan with test strategy
-- Performance impact assessment (middleware execution time)
+1. Replace direct references to `vercel-routing` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.
 ````

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

@@ -1,79 +1,21 @@
 ---
 name: vercel-routing
-description: "Vercel edge routing: middleware patterns, redirects/rewrites, Edge Config for real-time config without redeploys, Edge Config integrations, and Node.js migration paths."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, routing, middleware, redirects, rewrites, edge config, edge config integrations, edge to node, a/b routing, geo routing, edge middleware
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-functions, vercel-caching, vercel-flags
-  consolidates: vercel-routing-middleware, vercel-redirects-rewrites, vercel-edge-config, vercel-edge-config-integrations, vercel-edge-to-node-migration
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Routing
 
-## Purpose
+## Compatibility Alias
 
-Configure Vercel's edge routing layer with middleware patterns, redirect/rewrite rules, real-time Edge Config for runtime configuration, and migration paths away from the edge runtime.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Writing Vercel Middleware for auth, geo-routing, A/B testing, or bot checks.
-- Configuring redirects and rewrites in `vercel.json` or Next.js config.
-- Using Edge Config for real-time feature toggling or config without redeploys.
-- Integrating Edge Config with third-party providers (LaunchDarkly, etc.).
-- Migrating edge-incompatible middleware to Node.js functions.
+## Migration
 
-## Domain Areas
-
-### Middleware
-
-- Author `middleware.ts` with `NextRequest`/`NextResponse` or Web APIs.
-- Apply auth checks, geo-redirects, A/B bucket assignment.
-- Use `matcher` config to scope execution precisely.
-- Mind cold start and bundle size constraints (1MB limit).
-
-### Redirects & Rewrites
-
-- Configure in `vercel.json` under `redirects` / `rewrites`.
-- Permanent (308) vs temporary (307) redirects.
-- Capture groups and dynamic path rewriting.
-- Header-based and query-based conditional rewrites.
-
-### Edge Config
-
-- Create and populate Edge Config stores via dashboard or CLI.
-- Read in middleware with `@vercel/edge-config` SDK.
-- Zero-redeploy config changes for feature flags and kill switches.
-
-### Edge Config Integrations
-
-- Connect Edge Config to third-party providers.
-- Sync external flag state into Edge Config automatically.
-
-### Edge-to-Node Migration
-
-- Identify middleware using Node.js-incompatible APIs.
-- Refactor to Node.js serverless functions or API routes.
-- Use `runtime: 'nodejs'` config override.
-
-## Operating Checklist
-
-1. Audit middleware bundle size and strip unnecessary dependencies.
-2. Validate matcher patterns cover only intended routes.
-3. Test redirect rules for cyclic redirect risk.
-4. Populate Edge Config with safe defaults before enabling reads.
-5. Document Edge Config keys and owners; restrict write access.
-6. Plan edge-to-node migration with regression test coverage.
-
-## Output Contract
-
-- Middleware implementation with matcher config
-- Redirect/rewrite rule set with conflict analysis
-- Edge Config schema, population scripts, and read integration
-- Edge-to-node migration plan with test strategy
-- Performance impact assessment (middleware execution time)
+1. Replace direct references to `vercel-routing` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.

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

@@ -0,0 +1,43 @@
+````markdown
+---
+inclusion: manual
+name: vercel-runtime
+description: "Canonical Vercel runtime skill covering functions, routing, and caching with production guardrails."
+metadata:
+  deprecated: false
+  replaced_by: null
+  removal_target: null
+---
+
+# Vercel Runtime
+
+## Purpose
+
+Design and operate Vercel runtime behavior across serverless/edge functions, routing/middleware, and caching strategy as one coherent runtime layer.
+
+## Use This For
+
+- Function runtime selection (Node, Python, Edge, Fluid Compute)
+- Middleware, redirects/rewrites, Edge Config routing behavior
+- Cache-control, CDN behavior, ISR, Data Cache, invalidation
+
+## Decision Flow
+
+1. Confirm execution boundary (edge vs serverless vs region).
+2. Select routing strategy and middleware scope.
+3. Choose caching policy by data volatility and SLA.
+4. Validate failure behavior, fallback path, and observability.
+
+## Verification
+
+- Runtime logs confirm expected execution target.
+- Latency and cache hit ratio are measured.
+- No blocking regressions in auth/routing flows.
+
+## Related Skills
+
+- `vercel-platform`
+- `vercel-delivery`
+- `vercel-security`
+- `vercel-observability`
+````

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

@@ -0,0 +1,40 @@
+---
+name: vercel-runtime
+description: "Canonical Vercel runtime skill covering functions, routing, and caching with production guardrails."
+metadata:
+  deprecated: false
+  replaced_by: null
+  removal_target: null
+---
+
+# Vercel Runtime
+
+## Purpose
+
+Design and operate Vercel runtime behavior across serverless/edge functions, routing/middleware, and caching strategy as one coherent runtime layer.
+
+## Use This For
+
+- Function runtime selection (Node, Python, Edge, Fluid Compute)
+- Middleware, redirects/rewrites, Edge Config routing behavior
+- Cache-control, CDN behavior, ISR, Data Cache, invalidation
+
+## Decision Flow
+
+1. Confirm execution boundary (edge vs serverless vs region).
+2. Select routing strategy and middleware scope.
+3. Choose caching policy by data volatility and SLA.
+4. Validate failure behavior, fallback path, and observability.
+
+## Verification
+
+- Runtime logs confirm expected execution target.
+- Latency and cache hit ratio are measured.
+- No blocking regressions in auth/routing flows.
+
+## Related Skills
+
+- `vercel-platform`
+- `vercel-delivery`
+- `vercel-security`
+- `vercel-observability`

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

@@ -0,0 +1,43 @@
+````markdown
+---
+inclusion: manual
+name: vercel-security
+description: "Canonical Vercel security skill covering WAF, rate limiting, bot controls, and traffic-protection policy."
+metadata:
+  deprecated: false
+  replaced_by: null
+  removal_target: null
+---
+
+# Vercel Security
+
+## Purpose
+
+Secure Vercel deployments with enforceable edge protections: WAF policy, rate limiting, bot filtering, and abuse mitigation tied to observability signals.
+
+## Use This For
+
+- WAF and custom firewall rules
+- Rate-limit and abuse protection controls
+- Bot management and traffic filtering
+- Security hardening for public endpoints
+
+## Decision Flow
+
+1. Identify threat surface and high-risk routes.
+2. Apply least-disruptive controls first.
+3. Add strict controls for abusive patterns.
+4. Validate against false positives and critical user paths.
+
+## Verification
+
+- Attack traffic is blocked/challenged as expected.
+- Legitimate traffic remains unaffected on critical paths.
+- Security alerts and logs are correlated in observability tools.
+
+## Related Skills
+
+- `security-reviewer`
+- `secure-code-guardian`
+- `vercel-observability`
+````