vercel-labs/agent-skills
Vercel's official collection of agent skills
https://skillcdn.ai/gh/vercel-labs/agent-skillsConnect this address to your AI to use these skills. How to connect
- Unverified
- Default branch
main - Commit
1a2c79d - License
None declared - Searchwords and meaning
Explore this repository
Searches the original text of skills and documents by words and by meaning; display translations are not searched.
Support topics are small, candidate-scoped investigation guardrails injected into sub-agent briefs.
Documents
- Support TopicsSupport topics are small, candidate-scoped investigation guardrails injected into sub-agent briefs.skills/vercel-optimize/references/support-topics/README.md
- Astro edge middleware scopeAstro middleware can run at the edge for broad request sets. If middleware volume is high, prove which paths actually need interception.skills/vercel-optimize/references/support-topics/astro-edge-middleware-scope.md
- Astro output mode and ISRAstro defaults to static output; server output makes pages render on demand unless route-level prerendering changes that. First decide whether the hot route truly needs SSR.skills/vercel-optimize/references/support-topics/astro-output-mode-and-isr.md
- Authorization-preserving parallelizationParallelizing awaits is safe only when it does not move private data access ahead of the auth, ownership, tenant, or permission check protecting that data.skills/vercel-optimize/references/support-topics/auth-preserving-parallelization.md
- Bot Protection product guardrailsBot Protection recommendations must be grounded in observed automated traffic or meaningful edge-request scale.skills/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md
- Build Minutes monorepo fanoutBuild Minutes climbs when commits rebuild unchanged work. Common causes: TURBO_FORCE, cache: false, missing outputs, or disabled build-skip settings.skills/vercel-optimize/references/support-topics/build-minutes-monorepo-fanout.md
- Cache Components static shell boundariesOn Next.js 16 with Cache Components, avoid older segment-config advice. The right question is whether the route can keep a static shell while dynamic data moves behind explicit cached or runtime boun…skills/vercel-optimize/references/support-topics/cache-components-static-shell-boundaries.md
- Cache Components Suspense dedupe pitfallDefault 'use cache' does not dedupe identical calls across separate <Suspense> boundaries on the same render. Each boundary re-invokes the cached function, multiplying function-duration and ISR write…skills/vercel-optimize/references/support-topics/cache-components-suspense-dedupe-pitfall.md
- CDN cache auth safetyTreat edge caching as a safety question first. The route must be a public, cacheable GET path before a shared-cache recommendation is allowed.skills/vercel-optimize/references/support-topics/cdn-cache-auth-safety.md
- Cold-start initialization and bundle weightCold-start candidates need a code-path check, not only a project-setting check. First prove whether cold requests are paying for imports, module-scope setup, runtime choice, or dependency weight.skills/vercel-optimize/references/support-topics/cold-start-initialization-bundle.md
- Core Web Vitals client bottlenecksCore Web Vitals candidates need metric-specific investigation. LCP, INP, and CLS usually have different causes and fixes.skills/vercel-optimize/references/support-topics/core-web-vitals-client-bottlenecks.md
- Database region and connection pressureOnly recommend database or region changes when source and metrics both point to downstream I/O rather than in-process compute.skills/vercel-optimize/references/support-topics/database-egress-pooling-region.md
- Dynamic rendering trapsRendering candidates are only actionable when the dynamic behavior is accidental. First prove that the route can be static, ISR, or partially static.skills/vercel-optimize/references/support-topics/dynamic-rendering-traps.md
- Cross-framework external API critical pathExternal API candidates are actionable only when the slow hostname is on a customer route's critical path. Prove the route waits on it before suggesting a cache, payload, or post-response change.skills/vercel-optimize/references/support-topics/external-api-critical-path-platform.md
- External API critical pathFor external API candidates, identify the customer route that waits on the slow hostname and whether the call is on the critical path.skills/vercel-optimize/references/support-topics/external-api-critical-path.md
- Fast Data Transfer payloadsWhen uncached routes carry high bandwidth, check payload shape before recommending only cache headers. Fast Data Transfer includes the bytes transferred by requests and responses; compare compressed…skills/vercel-optimize/references/support-topics/fast-data-transfer-payloads.md
- Fluid compute caveatsFluid compute is a project-level lever. Use it when the setting is off and metrics show cold-start or warm-instance reuse pressure. Fluid can handle multiple invocations in one function instance; avo…skills/vercel-optimize/references/support-topics/fluid-compute-caveats.md
- Function duration, I/O, and post-response workWhen wall-clock latency is much higher than CPU time, check critical-path awaits before blaming rendering or compute.skills/vercel-optimize/references/support-topics/function-duration-io-and-after.md
- Function invocation reductionFor slow routes, prove duplicated in-request work in the listed files before recommending consolidation or memoization.skills/vercel-optimize/references/support-topics/function-invocation-reduction.md
- Function region misconfiguration (TTFB)A single function region is pinned. Per-region TTFB data is unavailable today (evidence.dataGap); treat as an audit prompt — validate the pinned region against user geo and data-source location befor…skills/vercel-optimize/references/support-topics/function-region-misconfiguration-ttfb.md
- Image optimization cost controlImage recommendations should distinguish real user-facing image work from wasteful transformations.skills/vercel-optimize/references/support-topics/image-optimization-cost-control.md
- ISR revalidation and static generationFor ISR over-revalidation, the goal is to reduce unnecessary regeneration work without making content stale beyond the product’s tolerance.skills/vercel-optimize/references/support-topics/isr-revalidation-static-generation.md
- Middleware edge costMiddleware recommendations should reduce unnecessary interception, not remove required request handling.skills/vercel-optimize/references/support-topics/middleware-proxy-edge-cost.md
- Next.js fetch revalidation floorNext.js fetch options can set the route's effective cache floor. Low revalidate, revalidate: 0, or cache: 'no-store' can explain uncached traffic and excessive ISR work.skills/vercel-optimize/references/support-topics/next-fetch-revalidate-floor.md
- Next.js font CLS guardrailFor poor CLS, check fonts only when the route actually loads external font CSS or swaps text after render.skills/vercel-optimize/references/support-topics/next-font-cls-self-hosting.md
- Next.js heavy UI lazy-load boundariesHeavy above-the-fold or rarely used UI can hurt LCP and INP when it ships too much JavaScript on first load. Look for concrete route-local UI, not generic bundle advice.skills/vercel-optimize/references/support-topics/next-heavy-ui-lazy-load-boundaries.md
- Next.js image LCP preload and sizesFor poor LCP, identify whether the LCP element is an image before touching unrelated JavaScript. Hero images need correct sizing, priority behavior, and source-cache hygiene.skills/vercel-optimize/references/support-topics/next-image-lcp-preload-sizes.md
- Next.js Route Handler GET cache defaultsOn Next.js 15+, GET Route Handlers are dynamic by default. For hot public GET handlers, verify whether uncached behavior is intentional before recommending cache headers or route config.skills/vercel-optimize/references/support-topics/next-route-handler-get-cache-defaults.md
- Next.js third-party script strategyThird-party scripts are only actionable when they line up with the poor metric and route. For LCP or INP, prove a specific script blocks critical rendering, hydration, or interaction.skills/vercel-optimize/references/support-topics/next-script-third-party-strategy.md
- Next.js cache semantics by versionOn Next.js 15+, match the fix to the cache primitive already in use.skills/vercel-optimize/references/support-topics/nextjs-version-cache-semantics.md
- Not-found and catch-all request wasteHigh-volume 404 or catch-all traffic is often request waste. First determine whether the traffic is legacy URLs, bots, broken links, or a real product route.skills/vercel-optimize/references/support-topics/not-found-catchall-request-waste.md
- Nuxt routeRules cache and ISRFor Nuxt on Vercel, route-level caching usually belongs in routeRules. Match the lever to the route: prerender for static pages, ISR for shared content, and SSR for request-specific views.skills/vercel-optimize/references/support-topics/nuxt-route-rules-cache-isr.md
- Observability Events cost attributionObservability Events is the metered SKU under Observability Plus. When the current bill shows a large Observability Events share, event volume is the lever. Reduce upstream: lift cache hit rate, narr…skills/vercel-optimize/references/support-topics/observability-events-cost-attribution.md
- Post-response work with waitUntilFor stacks without Next.js after(), check whether non-critical work can run after the response instead of extending user-visible latency.skills/vercel-optimize/references/support-topics/post-response-work-waituntil.md
- Durable offload for timeout-heavy routesTimeout-heavy routes often need a job boundary, not a higher limit. Workflow fits durable multi-step work that can continue after the response; return a run ID instead of waiting on returnValue.skills/vercel-optimize/references/support-topics/route-error-durable-offload.md
- Route errors and runtime limitsRoute error candidates are reliability findings with cost impact. Determine whether the failures are app exceptions, timeouts, payload limits, or deployment-specific regressions.skills/vercel-optimize/references/support-topics/route-error-runtime-limits.md
- Runtime Cache for reusable server dataRuntime Cache is only useful when the same server-side result is reused across requests. Treat it as a measured alternative when CDN response caching is unsafe or incomplete.skills/vercel-optimize/references/support-topics/runtime-cache-reusable-data.md
- SvelteKit ISR and prerender safetyFor SvelteKit, the right lever is often prerender or adapter ISR on public consumer pages. First prove every visitor can safely see the same response for the configured interval.skills/vercel-optimize/references/support-topics/sveltekit-isr-prerender-safety.md
- SvelteKit split function cold-start tradeoffSvelteKit bundles routes together by default to avoid excessive cold starts. Treat split: true as a targeted tradeoff, not a blanket optimization.skills/vercel-optimize/references/support-topics/sveltekit-split-cold-start-tradeoff.md
- Usage spike triageA single-day or single-SKU spike needs cause before fix. Branches: bot or AI crawler on a cacheable route, viral moment, pricing-model migration, or code regression.skills/vercel-optimize/references/support-topics/usage-spike-triage.md
- 'use cache' date-stamp ISR write amplifier'use cache' keys on argument identity and prerender output. A new Date(), Date.now(), or Math.random() baked into the cached output forces a fresh ISR write on every regeneration even when the data i…skills/vercel-optimize/references/support-topics/use-cache-date-stamp-isr-write-amplifier.md
- Remote cache for shared origin dataFor 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 generat…skills/vercel-optimize/references/support-topics/use-cache-remote-shared-origin-data.md
- Workflow resumable stream routesStream-shaped routes may be Workflow SDK reconnection endpoints. Long wall-clock duration can be the live client connection.skills/vercel-optimize/references/support-topics/workflow-resumable-stream-routes.md
Skipped (2)
These manifests were not served. Fix them and push: the next commit is indexed again.
skills/react-best-practices/AGENTS.mdlink_missing3 links name no file of the repository (./async-defer-await.md, ./async-cheap-condition-before-await.md, ./server-hoist-static-io.md)skills/react-view-transitions/AGENTS.mdlink_missing20 links name no file of the repository (css-recipes.md, css-recipes.md#persistent-element-isolation, css-recipes.md#backdrop-blur-workaround, ...)