playbook/antigravity-awesome-skills/skills/vercel-optimize/references/support-topics/use-cache-remote-shared-origin-data.md

id	title	status	candidateKinds	frameworks	priority	citations	maxBriefChars
use-cache-remote-shared-origin-data	Remote cache for shared origin data	active	external_api_slow slow_route uncached_route	next@>=16.0.0	87	https://vercel.com/docs/caching/runtime-cache https://nextjs.org/docs/app/api-reference/directives/use-cache-remote	950

Investigation Brief

For Next 16 candidates, check whether shared origin data or reusable route-handler work belongs in remote cache. Default 'use cache' is not cross-request on Vercel. Use 'use cache: remote' or generateStaticParams.

Evidence To Check

Hostname p75, caller routes, call count, bytes. Verify data is shared and tolerates the freshness window. Confirm 'use cache: remote'.

Do Not Recommend When

Skip per-user, mutation, secret, or freshness-critical data. Skip when upstream is fast or rarely called. Avoid sub-ms reads (Edge Config) — overhead exceeds source latency.

Verification

Name hostname, shared data, freshness window, and exact boundary. State 'use cache: remote'.