@cubis/foundry 0.3.11 → 0.3.12

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-deployments/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: vercel-deployments
+description: "Vercel deployment lifecycle: git-triggered deployments, build pipeline, build output API, deployment promotion, environment management, preview/production protection, and generated URL patterns."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, deployment, git deploy, build pipeline, build output api, deployment promotion, environments, preview, production, protection, generated urls, build image
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, vercel-cli, vercel-caching, vercel-domains
+  consolidates: vercel-git-deployments, vercel-deployment-promotion, vercel-deployment-protection, vercel-protection-bypass-automation, vercel-environments, vercel-build-pipeline, vercel-build-output-api, vercel-build-image-upgrades, vercel-generated-urls
+---
+
+# Vercel Deployments
+
+## Purpose
+Manage the full Vercel deployment lifecycle from git-triggered builds to production promotion, including environment management, deployment protection, build pipeline customization, and URL strategies.
+
+## When To Use
+- Setting up git-based automatic deployments (push-to-deploy).
+- Configuring build pipeline steps and custom build commands.
+- Using Build Output API for framework-agnostic output generation.
+- Promoting preview deployments to production.
+- Configuring deployment protection (password, SSO, Vercel Auth).
+- Automating protection bypass for CI/CD testing.
+- Managing multiple environments (production, preview, development).
+- Understanding and controlling generated deployment URL patterns.
+- Upgrading build image versions.
+
+## Domain Areas
+
+### Git Deployments
+- Branch → environment mapping (main → production, etc.).
+- Ignored build step configuration.
+- Monorepo detection and build filtering.
+
+### Build Pipeline
+- Custom `buildCommand`, `outputDirectory`, `installCommand`.
+- Build caching and artifact reuse.
+- Build environment variable injection.
+
+### Build Output API
+- Framework-agnostic output format: static files, functions, middleware.
+- `config.json`, `routes`, and prerender configs.
+
+### Build Image Upgrades
+- Choose and lock Node.js / system dependency versions.
+- Upgrade strategy and regression testing plan.
+
+### Deployment Promotion
+- Promote preview to production via CLI or dashboard.
+- Instant rollback to previous production deployment.
+
+### Deployment Protection
+- Configure Vercel Authentication, password protection, or IP allowlists for previews.
+- Set per-environment protection levels.
+
+### Protection Bypass Automation
+- Use `VERCEL_AUTOMATION_BYPASS_SECRET` for CI access to protected deployments.
+- Rotate secrets and audit bypass usage.
+
+### Environments
+- Manage production, preview, and development environment variables.
+- Scope secrets per target environment.
+- Use environment variable groups for shared config.
+
+### Generated URLs
+- Understand deployment URL anatomy (`project-hash-team.vercel.app`).
+- Configure custom domains alongside generated URLs.
+- Use deployment URLs in CI testing pipelines.
+
+## Operating Checklist
+1. Validate git branch → environment mapping before first deploy.
+2. Test build pipeline locally with `vercel build` before pushing.
+3. Set deployment protection for preview environments.
+4. Configure protection bypass secret for CI/CD pipelines.
+5. Stage → promote workflow: test on preview, promote to production.
+6. Verify instant rollback readiness before any risky deploy.
+
+## Output Contract
+- Build pipeline configuration (`vercel.json` / framework config)
+- Environment variable structure per environment tier
+- Deployment protection settings and bypass secret rotation plan
+- Promotion runbook with rollback steps
+- Residual risks and follow-up actions

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-domains/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: vercel-domains
+description: "Vercel domain management: custom domains, DNS records, nameservers, SSL certificates, domain ownership verification, and static IP configuration."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, domain, dns, nameservers, ssl, certificate, custom domain, cname, static ip, domain ownership
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, vercel-deployments, vercel-platform
+  consolidates: vercel-dns-records, vercel-nameservers, vercel-ssl-certificates, vercel-domain-ownership-claims, vercel-static-ips
+---
+
+# Vercel Domains
+
+## Purpose
+Manage custom domains on Vercel including DNS configuration, nameserver delegation, SSL certificate provisioning, domain ownership verification, and static IP assignment.
+
+## When To Use
+- Adding a custom domain to a Vercel project.
+- Configuring DNS records (A, CNAME, TXT, MX) for a domain.
+- Delegating nameservers to Vercel for full DNS management.
+- Troubleshooting SSL certificate provisioning failures.
+- Claiming domain ownership for enterprise configurations.
+- Assigning dedicated static IPs for allowlist-based firewall rules.
+
+## Domain Areas
+
+### Custom Domains
+- Add domains in Vercel project settings.
+- Configure redirect from www ↔ apex and production ↔ preview.
+
+### DNS Records
+- Manage A, AAAA, CNAME, TXT, MX, SRV records via Vercel DNS.
+- Priority ordering for MX and SRV records.
+
+### Nameservers
+- Delegate domain to Vercel nameservers for managed DNS.
+- Validate propagation with `dig`/`nslookup`.
+
+### SSL Certificates
+- Automatic cert provisioning via Let's Encrypt.
+- Troubleshoot DNS validation challenges.
+- Wildcard cert requirements for multi-tenant setups.
+
+### Domain Ownership Claims
+- Verify domain ownership using TXT record DNS challenges.
+- Required for enterprise team domain assignment.
+
+### Static IPs
+- Enable dedicated static egress IPs for firewall allowlisting.
+- Document IPs for downstream system configuration.
+
+## Operating Checklist
+1. Confirm ownership and DNS authority for each managed domain.
+2. Apply changes with TTL and propagation windows accounted for.
+3. Validate SSL cert provisioning and auto-renewal is active.
+4. Complete domain ownership claim if required by enterprise team.
+5. Document static IPs and communicate to downstream firewall owners.
+6. Prepare rollback records for every production DNS change.
+
+## Output Contract
+- DNS record configuration plan with TTL values
+- SSL certificate provisioning status and validation method
+- Nameserver delegation steps and verification commands
+- Static IP assignments and downstream firewall change requests
+- Residual risks (propagation delays, cert failures)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-firewall/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: vercel-firewall
+description: "Vercel security controls: WAF core, custom firewall rules, rate limiting, bot management, and BotID fingerprinting for DDoS protection, abuse prevention, and traffic filtering."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, firewall, waf, rate limiting, bot protection, botid, ddos, abuse, traffic filtering, custom rules
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: secure-code-guardian, security-reviewer, vercel-observability, vercel-domains
+  consolidates: vercel-firewall-core, vercel-waf-custom-rules, vercel-waf-rate-limiting, vercel-bot-management, vercel-botid
+---
+
+# Vercel Firewall
+
+## Purpose
+Protect Vercel deployments from abuse, DDoS, bots, and malicious traffic using WAF custom rules, rate limiting, bot management, and BotID fingerprinting.
+
+## When To Use
+- Setting up WAF rules to block or challenge malicious requests.
+- Implementing rate limiting to prevent API abuse.
+- Detecting and blocking bad bots while allowing good bots.
+- Using BotID for persistent bot fingerprinting.
+- Configuring IP allowlists/blocklists and geo-based rules.
+
+## Domain Areas
+
+### WAF Core & Custom Rules
+- Create IP-based, header-based, path-based, and geo-based rules.
+- Actions: `deny`, `challenge`, `log`, `redirect`.
+- Set rule priority and conflict resolution order.
+
+### Rate Limiting
+- Configure request rate limits per IP, route, or user segment.
+- Define burst allowances and penalty durations.
+- Use sliding window vs fixed window strategies.
+
+### Bot Management
+- Distinguish good bots (crawlers, monitors) from bad bots.
+- Apply challenge pages or blocks for detected bots.
+- Maintain an up-to-date allowed bot list.
+
+### BotID
+- Enable persistent bot fingerprinting via BotID header.
+- Use BotID signals in downstream application logic.
+- Monitor and tune BotID confidence thresholds.
+
+## Operating Checklist
+1. Audit current attack patterns and abuse vectors before rule creation.
+2. Define rule priorities and test in log-only mode first.
+3. Set rate limits with appropriate burst allowances to avoid false positives.
+4. Enable and tune bot management; validate good-bot pass-through.
+5. Monitor firewall metrics post-deploy for false positive spikes.
+6. Document all rules with justification for future maintenance.
+
+## Output Contract
+- WAF rule set definition with priorities and actions
+- Rate limiting configuration per route/IP
+- Bot management policy and BotID integration plan
+- Monitoring thresholds and alert definitions
+- False positive mitigation strategy

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-flags/SKILL.md

@@ -0,0 +1,64 @@
+---
+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
+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
+---
+
+# Vercel Flags
+
+## Purpose
+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.
+
+## When To Use
+- 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.
+
+## 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

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-functions/SKILL.md

@@ -0,0 +1,71 @@
+---
+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
+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
+---
+
+# Vercel Functions
+
+## Purpose
+Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
+
+## 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.
+
+## 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

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-observability/SKILL.md

@@ -0,0 +1,87 @@
+---
+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/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-platform/SKILL.md

@@ -0,0 +1,108 @@
+---
+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/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-routing/SKILL.md

@@ -0,0 +1,70 @@
+---
+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
+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
+---
+
+# 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.
+
+## 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.
+
+## 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)