@cubis/foundry 0.3.31 → 0.3.33

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/vercel-functions/SKILL.md

@@ -1,71 +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
-Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
+## Compatibility Alias
 
-## When To Use
-- 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.
+This skill is deprecated and kept for backward compatibility.
 
-## Domain Areas
+Use `vercel-runtime` as the canonical skill.
 
-### Core Patterns
-- Request/response handler structure for Vercel functions.
-- Environment-aware error handling and status codes.
-- Cold start mitigation strategies.
+## Migration
 
-### 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/workflows/agent-environment-setup/platforms/cursor/skills/vercel-observability/SKILL.md

@@ -17,9 +17,11 @@ metadata:
 # Vercel Observability
 
 ## Purpose
+
 Instrument, collect, and act on observability signals from Vercel deployments: structured runtime logs, distributed traces, session tracing, performance metrics, analytics, and audit events.
 
 ## When To Use
+
 - Setting up runtime log viewing and structured log queries.
 - Configuring log drains to export to external systems (Datadog, Baselime, etc.).
 - Implementing OpenTelemetry (OTel) tracing in Vercel functions.
@@ -33,45 +35,55 @@ Instrument, collect, and act on observability signals from Vercel deployments: s
 ## Domain Areas
 
 ### Runtime Logs
+
 - View and filter logs in Vercel dashboard or CLI.
 - Structure logs with consistent fields (level, traceId, userId).
 
 ### Log Drains
+
 - Configure HTTP or HTTPS log drain endpoints.
 - Filter by source (functions, edge, build) and log level.
 - Validate drain delivery and handle backpressure.
 
 ### OpenTelemetry Tracing
+
 - Instrument functions with `@vercel/otel` or standard OTel SDK.
 - Export spans to Vercel or external OTLP endpoints.
 - Correlate log entries with trace IDs for unified debugging.
 
 ### Session Tracing
+
 - Enable session capture for replay-based debugging.
 - Scope to error sessions or specific user segments.
 
 ### Speed Insights
+
 - Install `@vercel/speed-insights` in Next.js or other frameworks.
 - Monitor LCP, FID/INP, CLS per route.
 - Set performance budgets and track regressions.
 
 ### Web Analytics
+
 - Enable Vercel Web Analytics for privacy-first traffic data.
 - Track page views, referrers, and custom events.
 
 ### Custom Events
+
 - Emit custom events via `@vercel/analytics/react` or REST API.
 - Use for funnel tracking, feature adoption, and error reporting.
 
 ### Alerts & Monitoring
+
 - Configure threshold alerts on error rate, latency, and availability.
 - Route alerts to Slack, PagerDuty, or webhooks.
 
 ### Audit Logs
+
 - Review deployment, permission, and configuration changes.
 - Export audit logs for compliance reporting.
 
 ## Operating Checklist
+
 1. Enable runtime logs and configure structured log format.
 2. Set up log drain to external system if needed.
 3. Instrument functions with OTel and validate trace export.
@@ -80,6 +92,7 @@ Instrument, collect, and act on observability signals from Vercel deployments: s
 6. Schedule audit log review cadence for security compliance.
 
 ## Output Contract
+
 - Observability architecture diagram (logs → traces → metrics → alerts)
 - Log structure schema and drain configuration
 - OTel instrumentation code and exporter config

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/vercel-platform/SKILL.md

@@ -17,9 +17,11 @@ metadata:
 # Vercel Platform
 
 ## Purpose
+
 Administer Vercel at the platform level — project configuration, team access control, identity/SSO, secure networking, REST API automation, webhooks, native integrations, architecture patterns (monorepos, microfrontends, multi-tenant), and platform-level features like image optimization, OG image generation, and cron jobs.
 
 ## When To Use
+
 - Configuring project-level settings in `vercel.json`.
 - Managing team RBAC roles and access groups.
 - Enforcing 2FA or configuring OIDC/SSO federation.
@@ -37,59 +39,72 @@ Administer Vercel at the platform level — project configuration, team access c
 ## Domain Areas
 
 ### Project Configuration
+
 - `vercel.json` schema: functions, headers, redirects, rewrites, regions.
 - Framework detection and override settings.
 
 ### RBAC & Access Groups
+
 - Assign Owner, Member, Viewer roles per project or team.
 - Access groups for project-level permission scoping.
 
 ### Identity & Security (2FA / OIDC / Secure Compute)
+
 - Enforce 2FA for all team members.
 - Configure OIDC federation for CI/CD token-based auth.
 - Use Secure Compute for private egress to internal services.
 
 ### REST API & SDK
+
 - Authenticate with `VERCEL_TOKEN`; respect rate limits.
 - Use `@vercel/sdk` (TypeScript) for typed API access.
 - Common endpoints: deployments, env vars, domains, projects.
 
 ### Webhooks & Checks
+
 - Register webhooks for `deployment.created`, `deployment.succeeded`, etc.
 - Implement deployment checks (CI gates) via the Checks API.
 
 ### Integrations & Marketplace
+
 - Install native integrations (e.g., observability, storage).
 - Build marketplace partner integrations with OAuth and webhooks.
 
 ### MCP for Agents
+
 - Run Vercel MCP server locally or in CI for agent workflows.
 - Use for automated deployment queries, log retrieval, and config changes.
 
 ### Image Optimization & OG Images
+
 - Use `next/image` for automatic format conversion and resizing.
 - Generate OG images on the fly with `@vercel/og` (ImageResponse).
 - Cache OG images appropriately.
 
 ### Cron Jobs
+
 - Define cron schedules in `vercel.json` under `crons`.
 - Secure cron handler endpoints with `CRON_SECRET`.
 - Monitor cron execution logs in Vercel dashboard.
 
 ### Monorepos
+
 - Configure `rootDirectory` per project for monorepo packages.
 - Use Turborepo + Vercel Remote Cache for fast incremental builds.
 
 ### Microfrontends
+
 - Define app groups and routing in Vercel Microfrontends config.
 - Route per-path segments to independent Next.js apps.
 
 ### Multi-Tenant Architecture
+
 - Use hostname-based routing in middleware for tenant resolution.
 - Scope environment variables and storage per tenant.
 - Combine with Edge Config for real-time tenant config.
 
 ## Operating Checklist
+
 1. Audit and lock project configuration in `vercel.json`.
 2. Review and tighten RBAC roles; remove over-privileged members.
 3. Enforce 2FA for all team members; configure OIDC for CI.
@@ -99,6 +114,7 @@ Administer Vercel at the platform level — project configuration, team access c
 7. Validate monorepo build filtering and Turborepo cache hit rates.
 
 ## Output Contract
+
 - `vercel.json` configuration with annotated sections
 - RBAC role matrix and access group definitions
 - Identity/SSO configuration steps and validation evidence

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/vercel-routing/SKILL.md

@@ -1,70 +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
-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.
+## Compatibility Alias
 
-## When To Use
-- 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.
+This skill is deprecated and kept for backward compatibility.
 
-## Domain Areas
+Use `vercel-runtime` as the canonical skill.
 
-### 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).
+## Migration
 
-### 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/workflows/agent-environment-setup/platforms/cursor/skills/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/workflows/agent-environment-setup/platforms/cursor/skills/vercel-security/SKILL.md

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

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/vercel-storage/SKILL.md

@@ -17,9 +17,11 @@ metadata:
 # Vercel Storage
 
 ## Purpose
+
 Implement and manage Vercel Storage solutions including Blob for file/object storage, Marketplace Postgres for relational data, Marketplace Redis for caching/session state, and strategies for migrating between storage providers.
 
 ## When To Use
+
 - Storing user-uploaded files, assets, or binary objects with Vercel Blob.
 - Provisioning a managed Postgres database via Vercel Marketplace.
 - Using managed Redis for session storage, caching, or pub/sub.
@@ -28,29 +30,34 @@ Implement and manage Vercel Storage solutions including Blob for file/object sto
 ## Domain Areas
 
 ### Vercel Blob
+
 - Upload, list, and delete blobs with `@vercel/blob` SDK.
 - Client-side uploads using multipart upload tokens.
 - Set Content-Type, cache-control, and access control.
 - Integrate blob URLs with CDN delivery.
 
 ### Marketplace Postgres
+
 - Provision and connect via `POSTGRES_URL` environment variable.
 - Use with Prisma, Drizzle, or `pg`/`postgres` client.
 - Connection pooling with Vercel Postgres connection pool.
 - Schema migrations and backup strategy.
 
 ### Marketplace Redis
+
 - Connect via `KV_URL` / `REDIS_URL` environment variable.
 - Use `@vercel/kv` SDK or `ioredis` for session state, queues, and rate limiting.
 - Understand persistence and eviction policy defaults.
 - Multi-region replication considerations.
 
 ### Storage Migrations
+
 - Audit current storage usage volume and access patterns.
 - Plan zero-downtime migration with dual-write phase.
 - Validate data integrity post-migration before cutover.
 
 ## Operating Checklist
+
 1. Choose storage type based on access pattern (object vs relational vs KV).
 2. Inject connection strings via environment variables (never hard-code).
 3. Set appropriate TTL/eviction policies for Redis.
@@ -59,6 +66,7 @@ Implement and manage Vercel Storage solutions including Blob for file/object sto
 6. Enable auto-backup or export schedule for production data.
 
 ## Output Contract
+
 - Storage selection rationale and architecture
 - SDK integration code and environment variable setup
 - Connection pooling and scaling configuration