Vercel Platform

"Ship via git, run at the edge, pool every connection." [INFERENCE]

TL;DR

Builds and operates applications on Vercel — the frontend-cloud for Next.js and friends — across: Edge vs Serverless Functions, managed data stores (Postgres/Neon, KV, Blob), Incremental Static Regeneration, environment/secret scoping, and the git-driven deploy model. Closes the Vercel leg of the Firebase + Vercel + Hostinger Platform Lens. [EXPLICIT]

When to use

• Deploying a Next.js / frontend app to Vercel, with preview-per-PR environments. [EXPLICIT]
• Choosing Edge vs Serverless runtime for a route, or writing Edge Middleware. [EXPLICIT]
• Provisioning Vercel Postgres/Neon, KV, or Blob, with serverless-safe connections. [EXPLICIT]
• Configuring ISR (time-based or on-demand revalidateTag) and scoped secrets. [EXPLICIT]
• NOT for arbitrary container/VM workloads (use hostinger-platform/VPS) and NOT for Firebase-specific surfaces (use firebase-platform). [INFERENCE]

Sub-capabilities (resource map)

Procedure

1. Pick runtime per route (Edge for global low-latency/light; Serverless for Node APIs/heavy). [EXPLICIT]
2. Pick data store by workload; always use the pooled/serverless driver (fetch-based on Edge). [DOC]
3. Set caching explicitly per route: static, time-ISR, or on-demand revalidateTag. [DOC]
4. Scope secrets to Production/Preview/Development; never inline in client bundles. [CONFIG]
5. Deploy via git (preview on push, prod on merge); rollback = re-promote prior deployment. [DOC]

Quality Criteria

• Runtime chosen explicitly and justified (latency vs API needs). [EXPLICIT]
• Serverless/Edge data access uses pooled/fetch driver (no raw TCP pool). [DOC]
• Cache strategy explicit per route; on-demand revalidation wired to data changes. [DOC]
• Secrets scoped per environment; none in client bundles. [DOC]
• Claims evidence-tagged. [EXPLICIT]

Anti-Patterns

• Raw long-lived pg pool inside a Serverless Function (connection exhaustion). [DOC]
• Node built-ins (fs, Buffer) in an Edge route. [DOC]
• Middleware matching every request including static assets. [INFERENCE]

Contract

• Aceptación: runtime y store elegidos con justificación; conexiones pooled; caching explícito; secrets por entorno; deploy git-driven con rollback. [EXPLICIT]
• Límites: frontend-cloud/serverless; no contenedores arbitrarios ni VMs (eso es hostinger-platform). [EXPLICIT]
• Casos borde: Edge sin APIs Node → mover a Serverless; preview DB → branch Neon aislado, nunca producción. [DOC]
• Supuestos: proyecto Next.js/compatible con Vercel; tokens de deploy provistos por el usuario. [SUPUESTO]
• Trade-off: DX y edge global excelentes a cambio de lock-in al modelo Vercel y límites de runtime Edge. [EXPLICIT]

Related Skills

• firebase-platform, hostinger-platform — sibling target platforms (Platform Lens). [EXPLICIT]
• web-infra-foundation — DNS/SSL/CDN/backup concerns around the deployment. [EXPLICIT]
• cicd-release-engineering — pipelines and rollback strategy feeding Vercel deploys. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.