What problem does it solve? Deploying a Rango RSC application to Vercel requires correctly assembling the Build Output API v3 directory, configuring a streaming Node Function, wiring the Runtime Cache, and handling tracing — all of which involve platform-specific details that are easy to get wrong manually. ## Core Features & Use Cases - Build Output API v3 assembly: The vercel preset builds like the node preset and emits a .vercel/output directory containing a single streaming Node Function plus static client assets, deployable with vercel deploy --prebuilt or Git integration. - Function configuration: Set runtime, maxDuration, memory, regions, and functionName under the vercel option, written into .vc-config.json. - Runtime Cache integration: VercelCacheStore wraps the Vercel Runtime Cache for segment, item, response, and PPR shell families, with an in-memory fallback for local development. - Host routers and tracing: Deploy multi-app host routers as a single function, and emit rango.* phase spans through OpenTelemetry via createVercelTracing() and @vercel/otel. - Use Case: You have a Rango app with loaders, Server Actions, and PPR shells and want to ship it on Vercel — this Skill walks through the preset config, cache setup, and local validation scripts. ## Quick Start Ask the assistant to configure your Rango app with the vercel preset in vite.config.ts and explain how to deploy the generated .vercel/output directory.