@cubis/foundry 0.3.11 → 0.3.12

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/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/cursor/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)

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

@@ -0,0 +1,66 @@
+---
+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/Ai Agent Workflow/workflows/agent-environment-setup/platforms/windsurf/rules/.windsurfrules

@@ -12,6 +12,7 @@ This file defines mandatory behavior for Windsurf projects installed via `cbx wo
 ## 2) Smart Skill Selection (TIER 0)
 
 Before starting ANY task, the agent MUST:
+
 1.  **Analyze** the user's request against the keywords in `.windsurf/skills/skills_index.json`.
 2.  **Select** the most relevant skill(s) if a strong match is found.
 3.  **Load** the selected skill's `SKILL.md` using `view_file` **BEFORE** proceeding.
@@ -24,18 +25,70 @@ Before starting ANY task, the agent MUST:
 3.  Keep context lean; avoid loading unrelated skill documents.
 4.  If a mapped skill is missing, continue with best fallback and state it.
 
-## 4) Agent Routing Policy
+## 4) Request Classifier
+
+1. Question/explanation requests: answer directly.
+2. Survey/intel requests: inspect and summarize before editing.
+3. Simple code changes: minimal edits with focused verification.
+4. Complex code/design changes: plan first, then implement and verify.
+
+## 5) Agent Routing Policy
 
 Use the best specialist first:
+
 - Backend/API/database: `@backend-specialist`, `@database-architect`
 - Frontend/UI: `@frontend-specialist`
 - Mobile: `@mobile-developer`
 - Security: `@security-auditor`, `@penetration-tester`
 - DevOps/release: `@devops-engineer`
 - Testing/QA: `@test-engineer`, `@qa-automation-engineer`
+- Debugging/performance: `@debugger`, `@performance-optimizer`
+- Cross-domain orchestration: `@orchestrator`
+
+## 6) Socratic Gate (Before Complex Work)
 
-## 5) Quality and Safety Gates
+Before multi-file or architecture-impacting changes, ask targeted questions when requirements are unclear:
+
+1. Goal and success criteria
+2. Constraints and compatibility requirements
+3. Validation expectations (tests, lint, release checks)
+
+## 7) Quality and Safety Gates
 
 1.  Do not run destructive actions without explicit user confirmation.
 2.  Keep diffs small and reversible when possible.
 3.  Verify behavior with focused checks before finalizing.
+4.  State what was not validated.
+
+## 8) CBX Maintenance Commands
+
+Use these commands to keep this setup healthy:
+
+- Install/update bundle:
+  `cbx workflows install --platform windsurf --bundle agent-environment-setup --scope project --overwrite`
+- Rebuild managed routing block:
+  `cbx workflows sync-rules --platform windsurf --scope project`
+- Diagnose setup issues:
+  `cbx workflows doctor windsurf --scope project`
+
+## 9) Managed Section Contract
+
+1. Preserve all user content outside managed markers.
+2. Do not manually edit content between managed markers.
+3. `cbx workflows sync-rules` is the source of truth for the managed block.
+
+<!-- cbx:workflows:auto:start platform=windsurf version=1 -->
+
+## CBX Workflow Routing (auto-managed)
+
+Use the following workflows proactively when task intent matches:
+
+- No installed workflows found yet.
+
+Selection policy:
+
+1. Match explicit slash command first.
+2. Else match user intent to workflow description and triggers.
+3. Prefer one primary workflow; reference others only when needed.
+
+<!-- cbx:workflows:auto:end -->