@cubis/foundry 0.3.10 → 0.3.12

package/Ai Agent Workflow/skills/vercel-functions/SKILL.md

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

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

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

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

@@ -0,0 +1,74 @@
+---
+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/manifest.json

@@ -52,7 +52,6 @@
         "database-skills",
         "debugging-wizard",
         "devops-engineer",
-        "drift-flutter",
         "error-ux-observability",
         "fastapi-expert",
         "feature-forge",
@@ -215,7 +214,10 @@
         "vercel-sdk",
         "vercel-integrations-native",
         "vercel-marketplace-partner-api",
-        "vercel-webhooks-and-checks"
+        "vercel-webhooks-and-checks",
+        "drift-flutter",
+        "database-design",
+        "database-optimizer"
       ],
       "rulesTemplate": "platforms/antigravity/rules/GEMINI.md",
       "hooks": [
@@ -280,7 +282,6 @@
         "database-skills",
         "debugging-wizard",
         "devops-engineer",
-        "drift-flutter",
         "error-ux-observability",
         "fastapi-expert",
         "feature-forge",
@@ -443,7 +444,10 @@
         "vercel-sdk",
         "vercel-integrations-native",
         "vercel-marketplace-partner-api",
-        "vercel-webhooks-and-checks"
+        "vercel-webhooks-and-checks",
+        "drift-flutter",
+        "database-design",
+        "database-optimizer"
       ],
       "rulesTemplate": "platforms/codex/rules/AGENTS.md",
       "hooks": [
@@ -508,7 +512,6 @@
         "database-skills",
         "debugging-wizard",
         "devops-engineer",
-        "drift-flutter",
         "error-ux-observability",
         "fastapi-expert",
         "feature-forge",
@@ -671,7 +674,10 @@
         "vercel-sdk",
         "vercel-integrations-native",
         "vercel-marketplace-partner-api",
-        "vercel-webhooks-and-checks"
+        "vercel-webhooks-and-checks",
+        "drift-flutter",
+        "database-design",
+        "database-optimizer"
       ],
       "rulesTemplate": "platforms/copilot/rules/AGENTS.md",
       "hooks": [

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/backend-specialist.md

@@ -3,7 +3,7 @@ name: backend-specialist
 description: Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: clean-code, nodejs-best-practices, python-patterns, api-patterns, database-skills, mcp-builder, lint-and-validate, powershell-windows, bash-linux, rust-pro, api-designer, architecture-designer, typescript-pro, nestjs-expert, fastapi-expert, secure-code-guardian, test-master
+skills: clean-code, nodejs-best-practices, python-patterns, api-patterns, database-design, database-optimizer, database-skills, mcp-builder, lint-and-validate, powershell-windows, bash-linux, rust-pro, api-designer, architecture-designer, typescript-pro, nestjs-expert, fastapi-expert, secure-code-guardian, test-master
 ---
 
 # Backend Development Architect
@@ -260,4 +260,4 @@ After editing any file:
 
 ---
 
-> **Note:** This agent loads relevant skills for detailed guidance. The skills teach PRINCIPLES—apply decision-making based on context, not copying patterns.
+> **Note:** For database-heavy backend work, route through `database-skills` plus `Ai Agent Workflow/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/database-architect.md

@@ -3,7 +3,7 @@ name: database-architect
 description: Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: clean-code, database-skills, test-master
+skills: clean-code, database-design, database-optimizer, database-skills, test-master
 ---
 
 # Database Architect
@@ -209,6 +209,15 @@ After database changes:
 
 ---
 
+## Database Power Routing (MANDATORY)
+
+1. Load `database-skills` as the core package.
+2. Use `database-design` for schema and migration design choices.
+3. Use `database-optimizer` for query-plan and tuning triage.
+4. Load power bridge: `Ai Agent Workflow/powers/database-skills/POWER.md`.
+5. Pick engine wrapper in `Ai Agent Workflow/powers/database-skills/engines/<engine>/POWER.md`.
+6. Always output indexing plan, pagination plan, query-plan evidence, and rollback.
+
 ## When You Should Be Used
 
 - Designing new database schemas
@@ -223,4 +232,4 @@ After database changes:
 
 ---
 
-> **Note:** This agent loads the unified `database-skills` skill package for detailed guidance. Apply principles to context; do not copy patterns blindly.
+> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `Ai Agent Workflow/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/mobile-developer.md

@@ -3,7 +3,7 @@ name: mobile-developer
 description: Expert in React Native and Flutter mobile development. Use for cross-platform mobile apps, native features, and mobile-specific patterns. Triggers on mobile, react native, flutter, ios, android, app store, expo.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: clean-code, mobile-design, flutter-expert, riverpod-3, gorouter-restoration, drift-flutter, flutter-test-master, accessibility, test-master
+skills: clean-code, mobile-design, flutter-expert, riverpod-3, gorouter-restoration, drift-flutter, database-skills, flutter-test-master, accessibility, test-master
 ---
 
 # Mobile Developer

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/performance-optimizer.md

@@ -3,7 +3,7 @@ name: performance-optimizer
 description: Expert in performance optimization, profiling, Core Web Vitals, and bundle optimization. Use for improving speed, reducing bundle size, and optimizing runtime performance. Triggers on performance, optimize, speed, slow, memory, cpu, benchmark, lighthouse.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: clean-code, performance-profiling, web-perf, monitoring-expert, database-skills, react-best-practices, test-master
+skills: clean-code, performance-profiling, web-perf, monitoring-expert, database-design, database-optimizer, database-skills, react-best-practices, test-master
 ---
 
 # Performance Optimizer
@@ -185,3 +185,5 @@ What's slow?
 ---
 
 > **Remember:** Users don't care about benchmarks. They care about feeling fast.
+
+> **Database path:** For query/storage bottlenecks, route through `database-skills` and `Ai Agent Workflow/powers/database-skills`, and lean on `database-design`/`database-optimizer` when narrowing schema vs tuning issues; report index/pagination/plan evidence.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/agents/vercel-expert.md

@@ -3,13 +3,15 @@ name: vercel-expert
 description: Expert in Vercel platform delivery, runtime behavior, security controls, observability, and automation. Use for deployments, project configuration, middleware/routing, domains, flags, AI Gateway, and incident-ready operations.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: vercel-automation, vercel-project-configuration, vercel-functions-core, vercel-routing-middleware, vercel-cdn-cache, vercel-observability-overview, vercel-deployment-protection, vercel-domains, vercel-cli-core, vercel-ai-gateway-core, vercel-flags-platform, nextjs-developer, devops-engineer, monitoring-expert, secure-code-guardian, web-perf
+skills: vercel-platform, vercel-functions, vercel-routing, vercel-caching, vercel-observability, vercel-deployments, vercel-domains, vercel-cli, vercel-ai-gateway, vercel-ai-sdk, vercel-flags, vercel-firewall, vercel-storage, nextjs-developer, devops-engineer, monitoring-expert, secure-code-guardian, web-perf
 ---
+
 # Vercel Expert
 
 You are a platform specialist for Vercel architecture, deployment workflows, runtime tuning, security hardening, and observability.
 
 ## Core Responsibilities
+
 - Design and troubleshoot Vercel project and deployment pipelines.
 - Guide runtime choices across Node, Python, and Edge contexts.
 - Implement cache, routing, domains, and certificate-safe rollout strategies.
@@ -17,12 +19,14 @@ You are a platform specialist for Vercel architecture, deployment workflows, run
 - Automate repetitive operations through Vercel CLI, REST API, and SDK.
 
 ## Working Protocol
+
 1. Confirm target environment, blast radius, and rollback path before edits.
 2. Prefer minimal reversible changes with explicit verification checkpoints.
 3. Prioritize user-impact metrics, latency, and reliability over static assumptions.
 4. Call out missing access, quotas, or plan limits before proceeding.
 
 ## Escalation Rules
+
 - Add database specialist support for storage schema/query changes.
 - Add security specialist support for auth, WAF, or sensitive-data controls.
 - Add QA specialist support for release gates and regression automation.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/antigravity/workflows/database.md

@@ -5,22 +5,30 @@ triggers: ["database", "sql", "schema", "migration", "index"]
 ---
 # Database Workflow
 
-Use this when data modeling, query quality, or migration safety is core to the task.
+Use this when data modeling, query quality, migration safety, or database performance is core to the task.
 
 ## Routing
 - 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 and access patterns.
-2. Design schema/index strategy.
-3. Plan migration with rollback.
-4. Validate performance and integrity impacts.
+1. Confirm data shape, access patterns, and workload size.
+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
+- Indexing plan
+- Pagination plan
 - Migration + rollback plan
-- Performance expectations
+- Query-plan evidence (`EXPLAIN` or equivalent)
 - Validation evidence