@cubis/foundry 0.3.11 → 0.3.13

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/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/copilot/workflows/database.md

@@ -11,16 +11,19 @@ Use this when data modeling, query quality, migration safety, or database perfor
 - Primary specialist: `@database-architect`
 - Backend integration: `@backend-specialist`
 - Verification support: `@test-engineer`
-- Core skill package: `database-skills`
+- Core skill hub: `database-skills`
+- Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
+- Mobile/local persistence companion: `drift-flutter`
 - Power bridge: `Ai Agent Workflow/powers/database-skills`
 - Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
 
 ## Steps
 1. Confirm data shape, access patterns, and workload size.
-2. Choose engine wrapper and define index strategy.
-3. Define pagination strategy (keyset first, offset only if justified).
-4. Plan migration and rollback.
-5. Validate with query-plan evidence and production-risk notes.
+2. Choose track: `database-design` (schema/migrations), `database-optimizer` (tuning), or `database-skills` (engine wrappers).
+3. Choose engine wrapper and define index strategy.
+4. Define pagination strategy (keyset first, offset only if justified).
+5. Plan migration and rollback.
+6. Validate with query-plan evidence and production-risk notes.
 
 ## Output Contract
 - Schema/query changes

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/rules/.cursorrules

@@ -12,6 +12,7 @@ This file defines mandatory behavior for Cursor projects installed via `cbx work
 ## 2) Smart Skill Selection (TIER 0)
 
 Before starting ANY task, the agent MUST:
+
 1.  **Analyze** the user's request against the keywords in `.cursor/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 cursor --bundle agent-environment-setup --scope project --overwrite`
+- Rebuild managed routing block:
+  `cbx workflows sync-rules --platform cursor --scope project`
+- Diagnose setup issues:
+  `cbx workflows doctor cursor --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=cursor 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 -->

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/skills_index.json

@@ -1,50 +1,372 @@
 [
   {
-    "name": "flutter-expert",
-    "path": ".agent/skills/flutter-expert/SKILL.md",
-    "description": "Flutter app architecture, state management, and best practices.",
-    "triggers": ["flutter", "dart", "widget", "riverpod", "bloc", "buildcontext", "mobile app"]
+    "name": "backend-specialist",
+    "path": ".agent/skills/backend-specialist/SKILL.md",
+    "description": "Backend development, API design, and database management.",
+    "triggers": [
+      "api",
+      "backend",
+      "server",
+      "endpoint",
+      "database",
+      "sql",
+      "nosql",
+      "node",
+      "express"
+    ]
   },
   {
-    "name": "secure-code-guardian",
-    "path": ".agent/skills/secure-code-guardian/SKILL.md",
-    "description": "Security best practices, authentication, and vulnerability prevention.",
-    "triggers": ["security", "auth", "login", "password", "token", "jwt", "vulnerability", "hack"]
+    "name": "clean-code",
+    "path": ".agent/skills/clean-code/SKILL.md",
+    "description": "Clean code principles and refactoring.",
+    "triggers": [
+      "refactor",
+      "clean code",
+      "readability",
+      "structure",
+      "best practice"
+    ]
   },
   {
-    "name": "backend-specialist",
-    "path": ".agent/skills/backend-specialist/SKILL.md",
-    "description": "Backend development, API design, and database management.",
-    "triggers": ["api", "backend", "server", "endpoint", "database", "sql", "nosql", "node", "express"]
+    "name": "devops-engineer",
+    "path": ".agent/skills/devops-engineer/SKILL.md",
+    "description": "CI/CD, deployment, and infrastructure management.",
+    "triggers": [
+      "devops",
+      "deploy",
+      "ci/cd",
+      "pipeline",
+      "docker",
+      "kubernetes",
+      "cloud"
+    ]
+  },
+  {
+    "name": "flutter-expert",
+    "path": ".agent/skills/flutter-expert/SKILL.md",
+    "description": "Flutter app architecture, state management, and best practices.",
+    "triggers": [
+      "flutter",
+      "dart",
+      "widget",
+      "riverpod",
+      "bloc",
+      "buildcontext",
+      "mobile app"
+    ]
   },
   {
     "name": "frontend-design",
     "path": ".agent/skills/frontend-design/SKILL.md",
     "description": "UI/UX design principles, CSS, and component styling.",
-    "triggers": ["ui", "ux", "design", "css", "style", "component", "look and feel", "frontend"]
+    "triggers": [
+      "ui",
+      "ux",
+      "design",
+      "css",
+      "style",
+      "component",
+      "look and feel",
+      "frontend"
+    ]
+  },
+  {
+    "name": "performance-profiling",
+    "path": ".agent/skills/performance-profiling/SKILL.md",
+    "description": "Performance analysis and optimization.",
+    "triggers": [
+      "performance",
+      "speed",
+      "slow",
+      "optimize",
+      "profile",
+      "memory",
+      "cpu"
+    ]
+  },
+  {
+    "name": "secure-code-guardian",
+    "path": ".agent/skills/secure-code-guardian/SKILL.md",
+    "description": "Security best practices, authentication, and vulnerability prevention.",
+    "triggers": [
+      "security",
+      "auth",
+      "login",
+      "password",
+      "token",
+      "jwt",
+      "vulnerability",
+      "hack"
+    ]
   },
   {
     "name": "test-master",
     "path": ".agent/skills/test-master/SKILL.md",
     "description": "Comprehensive testing strategies and automation.",
-    "triggers": ["test", "testing", "unit test", "integration test", "e2e", "coverage", "qa"]
+    "triggers": [
+      "test",
+      "testing",
+      "unit test",
+      "integration test",
+      "e2e",
+      "coverage",
+      "qa"
+    ]
   },
   {
-    "name": "devops-engineer",
-    "path": ".agent/skills/devops-engineer/SKILL.md",
-    "description": "CI/CD, deployment, and infrastructure management.",
-    "triggers": ["devops", "deploy", "ci/cd", "pipeline", "docker", "kubernetes", "cloud"]
+    "name": "vercel-ai-gateway",
+    "path": ".agent/skills/vercel-ai-gateway/SKILL.md",
+    "description": "Complete Vercel AI Gateway integration: LLM traffic routing, authentication/BYOK, fallback chains, model-provider routing policies, usage observability, and OpenAI-compatible endpoints.",
+    "triggers": [
+      "vercel",
+      "ai gateway",
+      "llm",
+      "byok",
+      "fallback",
+      "model routing",
+      "openai compatible",
+      "token usage",
+      "ai observability"
+    ]
   },
   {
-    "name": "clean-code",
-    "path": ".agent/skills/clean-code/SKILL.md",
-    "description": "Clean code principles and refactoring.",
-    "triggers": ["refactor", "clean code", "readability", "structure", "best practice"]
+    "name": "vercel-ai-sdk",
+    "path": ".agent/skills/vercel-ai-sdk/SKILL.md",
+    "description": "Vercel AI SDK for building AI-powered applications: core providers/streaming patterns and React/Svelte UI hooks for chat, completion, and generative UX.",
+    "triggers": [
+      "vercel",
+      "ai sdk",
+      "useChat",
+      "useCompletion",
+      "streamText",
+      "generateText",
+      "streaming",
+      "generative ui"
+    ]
   },
   {
-    "name": "performance-profiling",
-    "path": ".agent/skills/performance-profiling/SKILL.md",
-    "description": "Performance analysis and optimization.",
-    "triggers": ["performance", "speed", "slow", "optimize", "profile", "memory", "cpu"]
+    "name": "vercel-caching",
+    "path": ".agent/skills/vercel-caching/SKILL.md",
+    "description": "Vercel caching strategies: CDN cache, cache-control headers, runtime cache, ISR, Next.js Data Cache, request collapsing, remote caching, and CDN purging.",
+    "triggers": [
+      "vercel",
+      "cdn cache",
+      "caching",
+      "isr",
+      "data cache",
+      "request collapsing",
+      "remote caching",
+      "cache-control"
+    ]
+  },
+  {
+    "name": "vercel-cli",
+    "path": ".agent/skills/vercel-cli/SKILL.md",
+    "description": "Vercel CLI mastery: core commands, flags, MCP integration, microfrontend management, and project/domain/environment variable operations.",
+    "triggers": [
+      "vercel cli",
+      "vercel command",
+      "npx vercel",
+      "vercel dev",
+      "vercel deploy",
+      "vercel env"
+    ]
+  },
+  {
+    "name": "vercel-deployments",
+    "path": ".agent/skills/vercel-deployments/SKILL.md",
+    "description": "Vercel deployment lifecycle: git deployments, build pipeline, build output API, deployment promotion, environment management, preview/production protection, and generated URL patterns.",
+    "triggers": [
+      "vercel",
+      "deployment",
+      "git deploy",
+      "build pipeline",
+      "deployment promotion",
+      "environments",
+      "preview",
+      "production"
+    ]
+  },
+  {
+    "name": "vercel-domains",
+    "path": ".agent/skills/vercel-domains/SKILL.md",
+    "description": "Vercel domain management: custom domains, DNS records, nameservers, SSL certificates, domain ownership verification, and static IP configuration.",
+    "triggers": [
+      "vercel",
+      "domain",
+      "dns",
+      "nameservers",
+      "ssl",
+      "certificate",
+      "custom domain",
+      "cname",
+      "static ip"
+    ]
+  },
+  {
+    "name": "vercel-firewall",
+    "path": ".agent/skills/vercel-firewall/SKILL.md",
+    "description": "Vercel security controls: WAF core, custom firewall rules, rate limiting, bot management, and BotID fingerprinting for DDoS protection and traffic filtering.",
+    "triggers": [
+      "vercel",
+      "firewall",
+      "waf",
+      "rate limiting",
+      "bot protection",
+      "botid",
+      "ddos",
+      "traffic filtering"
+    ]
+  },
+  {
+    "name": "vercel-flags",
+    "path": ".agent/skills/vercel-flags/SKILL.md",
+    "description": "Vercel Feature Flags: SDK integration, platform setup, CLI workflows, dashboard management, explorer UI, and OpenFeature compatibility.",
+    "triggers": [
+      "vercel",
+      "feature flags",
+      "flags sdk",
+      "openfeature",
+      "feature toggle",
+      "rollout",
+      "a/b test"
+    ]
+  },
+  {
+    "name": "vercel-functions",
+    "path": ".agent/skills/vercel-functions/SKILL.md",
+    "description": "Vercel Serverless and Edge Functions: core patterns, Node.js and Python runtimes, edge runtime, Fluid Compute, and function configuration.",
+    "triggers": [
+      "vercel",
+      "serverless",
+      "functions",
+      "edge function",
+      "nodejs runtime",
+      "python runtime",
+      "fluid compute",
+      "api route"
+    ]
+  },
+  {
+    "name": "vercel-observability",
+    "path": ".agent/skills/vercel-observability/SKILL.md",
+    "description": "Vercel observability stack: logs, tracing (OTel), session tracing, speed insights, web analytics, alerts, custom events, log drains, and audit logs.",
+    "triggers": [
+      "vercel",
+      "observability",
+      "runtime logs",
+      "tracing",
+      "opentelemetry",
+      "speed insights",
+      "web analytics",
+      "alerts",
+      "log drain",
+      "monitoring"
+    ]
+  },
+  {
+    "name": "vercel-platform",
+    "path": ".agent/skills/vercel-platform/SKILL.md",
+    "description": "Vercel platform operations: project config, 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 arch.",
+    "triggers": [
+      "vercel",
+      "project config",
+      "rbac",
+      "2fa",
+      "oidc",
+      "secure compute",
+      "rest api",
+      "webhooks",
+      "mcp for agents",
+      "image optimization",
+      "cron jobs",
+      "monorepo",
+      "multi-tenant"
+    ]
+  },
+  {
+    "name": "vercel-routing",
+    "path": ".agent/skills/vercel-routing/SKILL.md",
+    "description": "Vercel edge routing: middleware patterns, redirects/rewrites, Edge Config for real-time config without redeploys, Edge Config integrations, and migration paths.",
+    "triggers": [
+      "vercel",
+      "routing",
+      "middleware",
+      "redirects",
+      "rewrites",
+      "edge config",
+      "a/b routing",
+      "geo routing"
+    ]
+  },
+  {
+    "name": "vercel-storage",
+    "path": ".agent/skills/vercel-storage/SKILL.md",
+    "description": "Vercel Storage solutions: Blob for file storage, Marketplace Postgres, Marketplace Redis, and storage migration strategies.",
+    "triggers": [
+      "vercel",
+      "storage",
+      "blob",
+      "postgres",
+      "redis",
+      "kv",
+      "storage migration",
+      "vercel blob"
+    ]
+  },
+  {
+    "name": "database-skills",
+    "path": ".agent/skills/database-skills/SKILL.md",
+    "description": "Unified database skill hub with engine-specific packs for PostgreSQL, MySQL, Vitess, Neki, MongoDB, SQLite, Supabase, and Redis.",
+    "triggers": [
+      "database",
+      "sql",
+      "postgres",
+      "mysql",
+      "mongodb",
+      "sqlite",
+      "supabase",
+      "redis",
+      "schema",
+      "migration",
+      "index",
+      "query",
+      "performance"
+    ]
+  },
+  {
+    "name": "database-design",
+    "path": ".agent/skills/database-design/SKILL.md",
+    "description": "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.",
+    "triggers": [
+      "database",
+      "schema",
+      "indexing",
+      "migration"
+    ]
+  },
+  {
+    "name": "database-optimizer",
+    "path": ".agent/skills/database-optimizer/SKILL.md",
+    "description": "System-level database performance triage across engines.",
+    "triggers": [
+      "database",
+      "performance",
+      "query",
+      "index",
+      "tuning"
+    ]
+  },
+  {
+    "name": "drift-flutter",
+    "path": ".agent/skills/drift-flutter/SKILL.md",
+    "description": "Flutter Drift local persistence: DAOs, migrations, transactions.",
+    "triggers": [
+      "flutter",
+      "drift",
+      "sqlite",
+      "migration",
+      "dao"
+    ]
   }
 ]

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

@@ -0,0 +1,69 @@
+---
+name: vercel-ai-gateway
+description: "Complete Vercel AI Gateway integration: LLM traffic routing, authentication/BYOK, fallback chains, model-provider routing policies, usage observability, and OpenAI-compatible endpoints."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, ai, gateway, llm, byok, fallback, model routing, openai compatible, token usage, ai observability
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian, vercel-observability
+  consolidates: vercel-ai-gateway-core, vercel-ai-gateway-auth-byok, vercel-ai-gateway-fallbacks, vercel-ai-gateway-model-routing, vercel-ai-gateway-observability, vercel-ai-gateway-openai-compatible
+---
+
+# Vercel AI Gateway
+
+## Purpose
+Route LLM traffic through Vercel AI Gateway with unified controls covering authentication, model-provider routing, resilient fallback chains, usage observability, and OpenAI-compatible endpoint compatibility.
+
+## When To Use
+- Routing AI/LLM requests through Vercel's managed gateway.
+- Configuring bring-your-own-key (BYOK) authentication for AI providers.
+- Implementing retries and fallback chains for resilient AI responses.
+- Designing model and provider routing policies for latency, quality, and cost.
+- Monitoring AI Gateway usage, latency, and spend.
+- Using OpenAI-compatible endpoints without provider lock-in.
+
+## Domain Areas
+
+### Core Routing
+- Define unified gateway endpoint and routing config.
+- Set per-model quality, latency, and cost objectives.
+
+### Authentication & BYOK
+- Configure provider API key management and BYOK controls.
+- Scope key access per project/environment.
+
+### Fallbacks & Resilience
+- Implement retry policies and fallback provider chains.
+- Define circuit-breaker thresholds.
+
+### Model Routing Policies
+- Route by latency, cost, capability, or custom weights.
+- Support multi-provider and multi-region strategies.
+
+### Observability
+- Instrument token usage, latency, and error rates per model.
+- Set spend thresholds and alerting.
+
+### OpenAI Compatibility
+- Use OpenAI-compatible request/response format.
+- Migrate between providers without application changes.
+
+## Operating Checklist
+1. Define model quality, latency, and cost objectives for each endpoint.
+2. Configure authentication and BYOK key scoping per environment.
+3. Implement routing, fallback, and retry policies explicitly.
+4. Instrument token usage, latency, and error classes for all calls.
+5. Validate OpenAI-compatible endpoint compatibility if needed.
+6. Run safety and regression checks before broad rollout.
+
+## Output Contract
+- Proposed routing and authentication architecture with tradeoffs
+- Required config, code, and environment changes
+- Fallback chain definition and circuit-breaker settings
+- Validation evidence (spend limits, latency targets, error budgets)
+- Residual risks and follow-up actions