@cubis/foundry 0.3.67 → 0.3.69

package/workflows/skills/vercel-deployments/SKILL.md

@@ -1,21 +0,0 @@
----
-name: vercel-deployments
-description: "Compatibility alias skill. Deprecated: use vercel-delivery."
-metadata:
-  deprecated: true
-  replaced_by: vercel-delivery
-  removal_target: v0.6.0
----
-
-# Vercel Deployments
-
-## Compatibility Alias
-
-This skill is deprecated and kept for backward compatibility.
-
-Use `vercel-delivery` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `vercel-deployments` with `vercel-delivery`.
-2. Apply the full workflow from `vercel-delivery` for new work.

package/workflows/skills/vercel-domains/SKILL.md

@@ -1,21 +0,0 @@
----
-name: vercel-domains
-description: "Compatibility alias skill. Deprecated: use vercel-delivery."
-metadata:
-  deprecated: true
-  replaced_by: vercel-delivery
-  removal_target: v0.6.0
----
-
-# Vercel Domains
-
-## Compatibility Alias
-
-This skill is deprecated and kept for backward compatibility.
-
-Use `vercel-delivery` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `vercel-domains` with `vercel-delivery`.
-2. Apply the full workflow from `vercel-delivery` for new work.

package/workflows/skills/vercel-firewall/SKILL.md

@@ -1,21 +0,0 @@
----
-name: vercel-firewall
-description: "Compatibility alias skill. Deprecated: use vercel-security."
-metadata:
-  deprecated: true
-  replaced_by: vercel-security
-  removal_target: v0.6.0
----
-
-# Vercel Firewall
-
-## Compatibility Alias
-
-This skill is deprecated and kept for backward compatibility.
-
-Use `vercel-security` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `vercel-firewall` with `vercel-security`.
-2. Apply the full workflow from `vercel-security` for new work.

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

@@ -1,21 +0,0 @@
----
-name: vercel-flags
-description: "Compatibility alias skill. Deprecated: use vercel-delivery."
-metadata:
-  deprecated: true
-  replaced_by: vercel-delivery
-  removal_target: v0.6.0
----
-
-# Vercel Flags
-
-## Compatibility Alias
-
-This skill is deprecated and kept for backward compatibility.
-
-Use `vercel-delivery` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `vercel-flags` with `vercel-delivery`.
-2. Apply the full workflow from `vercel-delivery` for new work.

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

@@ -1,21 +0,0 @@
----
-name: vercel-functions
-description: "Compatibility alias skill. Deprecated: use vercel-runtime."
-metadata:
-  deprecated: true
-  replaced_by: vercel-runtime
-  removal_target: v0.6.0
----
-
-# Vercel Functions
-
-## Compatibility Alias
-
-This skill is deprecated and kept for backward compatibility.
-
-Use `vercel-runtime` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `vercel-functions` with `vercel-runtime`.
-2. Apply the full workflow from `vercel-runtime` for new work.

package/workflows/skills/vercel-observability/SKILL.md

@@ -1,100 +0,0 @@
----
-name: vercel-observability
-description: "Vercel observability stack: logs, tracing (OTel), session tracing, speed insights, web analytics, alerts, custom events, log drains, audit logs, and structured monitoring."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, observability, runtime logs, tracing, opentelemetry, session tracing, speed insights, web analytics, alerts, log drain, audit log, custom events, monitoring
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: monitoring-expert, sre-engineer, vercel-functions, vercel-firewall
-  consolidates: vercel-observability-overview, vercel-alerts-monitoring, vercel-runtime-logs, vercel-log-drain-reference, vercel-log-trace-correlation, vercel-session-tracing, vercel-tracing-otel, vercel-speed-insights, vercel-web-analytics, vercel-custom-events, vercel-audit-logs, vercel-drains-setup
----
-
-# 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.
-- Correlating logs with traces and requests via trace IDs.
-- Monitoring Core Web Vitals with Speed Insights.
-- Collecting custom business events for product analytics.
-- Tracking user sessions for debugging with Session Tracing.
-- Reviewing audit logs for security and compliance.
-- Setting up threshold alerts on function errors, p99 latency, etc.
-
-## 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.
-4. Install Speed Insights and establish performance budgets.
-5. Configure alerts with non-noisy thresholds and on-call routing.
-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
-- Speed Insights dashboard and performance budget definition
-- Alert policy with thresholds and escalation routing

package/workflows/skills/vercel-platform/SKILL.md

@@ -1,124 +0,0 @@
----
-name: vercel-platform
-description: "Vercel platform operations: project configuration, RBAC, 2FA/OIDC/SSO, secure compute, REST API, SDK, webhooks, integrations, MCP for agents, image optimization, OG images, cron jobs, monorepos, microfrontends, and multi-tenant architecture."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, project config, rbac, 2fa, oidc, sso, secure compute, rest api, vercel sdk, webhooks, integrations marketplace, mcp for agents, image optimization, og image, cron jobs, monorepo, microfrontends, multi-tenant, automation, audit
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: devops-engineer, secure-code-guardian, monitoring-expert, vercel-deployments, vercel-observability
-  consolidates: vercel-automation, vercel-project-configuration, vercel-rbac-access-groups, vercel-2fa-enforcement, vercel-oidc-federation, vercel-secure-compute, vercel-rest-api, vercel-sdk, vercel-webhooks-and-checks, vercel-integrations-native, vercel-marketplace-partner-api, vercel-mcp-for-agents, vercel-agent-workflows, vercel-image-optimization, vercel-og-image-generation, vercel-cron-jobs, vercel-microfrontends, vercel-monorepos, vercel-multi-tenant
----
-
-# 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.
-- Using Secure Compute for private networking (VPC-like).
-- Automating Vercel operations via REST API or SDK.
-- Registering webhooks for deployment events.
-- Installing and building native integrations or marketplace partners.
-- Configuring Vercel MCP for agent-driven platform automation.
-- Optimizing images via `next/image` or Vercel's Image Optimization API.
-- Generating Open Graph images with `@vercel/og`.
-- Scheduling background jobs with Vercel Cron.
-- Structuring monorepo builds and microfrontend app groups.
-- Implementing multi-tenant SaaS on Vercel.
-
-## 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.
-4. Validate REST API token scopes; rotate stale tokens.
-5. Test webhook delivery with replay; implement idempotent handlers.
-6. Verify cron endpoint security with `CRON_SECRET` validation.
-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
-- REST API and SDK integration patterns
-- Webhook handler implementation with idempotency
-- Architecture diagram for monorepo/microfrontend/multi-tenant setup
-- Residual risks and follow-up actions

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

@@ -1,21 +0,0 @@
----
-name: vercel-routing
-description: "Compatibility alias skill. Deprecated: use vercel-runtime."
-metadata:
-  deprecated: true
-  replaced_by: vercel-runtime
-  removal_target: v0.6.0
----
-
-# Vercel Routing
-
-## Compatibility Alias
-
-This skill is deprecated and kept for backward compatibility.
-
-Use `vercel-runtime` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `vercel-routing` with `vercel-runtime`.
-2. Apply the full workflow from `vercel-runtime` for new work.

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

@@ -1,40 +0,0 @@
----
-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/skills/vercel-security/SKILL.md

@@ -1,40 +0,0 @@
----
-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/skills/vercel-storage/SKILL.md

@@ -1,74 +0,0 @@
----
-name: vercel-storage
-description: "Vercel Storage solutions: Blob for file storage, Marketplace Postgres, Marketplace Redis, and storage migration strategies between providers."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, storage, blob, postgres, redis, kv, storage migration, file upload, vercel blob, vercel postgres, vercel redis
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: database-design, database-optimizer, vercel-functions, vercel-deployments
-  consolidates: vercel-blob, vercel-marketplace-storage-postgres, vercel-marketplace-storage-redis, vercel-storage-migrations
----
-
-# 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.
-- Migrating existing storage workloads onto or off Vercel-managed storage.
-
-## 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.
-4. Validate connection pooling config for Postgres under load.
-5. Run migration dry-run and verify checksums before full cutover.
-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
-- Migration plan with dry-run and rollback steps
-- Residual risks and data integrity validation evidence

package/workflows/skills/vulnerability-scanner/docs/checklists.md

@@ -1,121 +0,0 @@
-# Security Checklists
-
-> Quick reference checklists for security audits. Use alongside vulnerability-scanner principles.
-
----
-
-## OWASP Top 10 Audit Checklist
-
-### A01: Broken Access Control
-- [ ] Authorization on all protected routes
-- [ ] Deny by default
-- [ ] Rate limiting implemented
-- [ ] CORS properly configured
-
-### A02: Cryptographic Failures
-- [ ] Passwords hashed (bcrypt/argon2, cost 12+)
-- [ ] Sensitive data encrypted at rest
-- [ ] TLS 1.2+ for all connections
-- [ ] No secrets in code/logs
-
-### A03: Injection
-- [ ] Parameterized queries
-- [ ] Input validation on all user data
-- [ ] Output encoding for XSS
-- [ ] No eval() or dynamic code execution
-
-### A04: Insecure Design
-- [ ] Threat modeling done
-- [ ] Security requirements defined
-- [ ] Business logic validated
-
-### A05: Security Misconfiguration
-- [ ] Unnecessary features disabled
-- [ ] Error messages sanitized
-- [ ] Security headers configured
-- [ ] Default credentials changed
-
-### A06: Vulnerable Components
-- [ ] Dependencies up to date
-- [ ] No known vulnerabilities
-- [ ] Unused dependencies removed
-
-### A07: Authentication Failures
-- [ ] MFA available
-- [ ] Session invalidation on logout
-- [ ] Session timeout implemented
-- [ ] Brute force protection
-
-### A08: Integrity Failures
-- [ ] Dependency integrity verified
-- [ ] CI/CD pipeline secured
-- [ ] Update mechanism secured
-
-### A09: Logging Failures
-- [ ] Security events logged
-- [ ] Logs protected
-- [ ] No sensitive data in logs
-- [ ] Alerting configured
-
-### A10: SSRF
-- [ ] URL validation implemented
-- [ ] Allow-list for external calls
-- [ ] Network segmentation
-
----
-
-## Authentication Checklist
-
-- [ ] Strong password policy
-- [ ] Account lockout
-- [ ] Secure password reset
-- [ ] Session management
-- [ ] Token expiration
-- [ ] Logout invalidation
-
----
-
-## API Security Checklist
-
-- [ ] Authentication required
-- [ ] Authorization per endpoint
-- [ ] Input validation
-- [ ] Rate limiting
-- [ ] Output sanitization
-- [ ] Error handling
-
----
-
-## Data Protection Checklist
-
-- [ ] Encryption at rest
-- [ ] Encryption in transit
-- [ ] Key management
-- [ ] Data minimization
-- [ ] Secure deletion
-
----
-
-## Security Headers
-
-| Header | Purpose |
-|--------|---------|
-| **Content-Security-Policy** | XSS prevention |
-| **X-Content-Type-Options** | MIME sniffing |
-| **X-Frame-Options** | Clickjacking |
-| **Strict-Transport-Security** | Force HTTPS |
-| **Referrer-Policy** | Referrer control |
-
----
-
-## Quick Audit Commands
-
-| Check | What to Look For |
-|-------|------------------|
-| Secrets in code | password, api_key, secret |
-| Dangerous patterns | eval, innerHTML, SQL concat |
-| Dependency issues | npm audit, snyk |
-
----
-
-> **Usage:** Copy relevant checklists into your PLAN.md or security report.