Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Optimize Vercel build and deploy speed — audit checklist for new and existing projects.
Optimize Vercel build and deploy speed — audit checklist for new and existing projects.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Optimize Vercel build and deploy speed for any project. Run as a checklist when starting new projects or auditing existing ones.
New project setup — configure optimal defaults from day one Build times creeping up — audit and fix performance regressions Deploy queue bottlenecks — eliminate waiting on concurrent builds Production incidents — use instant rollback instead of waiting for a new build Cost optimization — balance speed vs spend on build infrastructure
Before running the full checklist, measure and assess: # 1. Check current build times cd <project> && npx vercel ls --limit 5 # 2. Check team/plan tier npx vercel team ls Decision tree: Build TimeAction< 20sOnly do items 0, 1, 3-5, 10. Skip GitHub Actions (#8), skip barrel file audit (#6) unless codebase is large.20-60sDo items 0-7, 10. GitHub Actions (#8) is optional.60s+Do everything. GitHub Actions (#8) becomes high-value. Auth-gated app? (All pages behind login) → Skip ISR (#9) entirely. ISR caches one response for all users — incompatible with per-user content. Framework: → SvelteKit: Also read docs/sveltekit.md — includes adapter-vercel switch, prerendering, $env tips. → Next.js/Nuxt/Other: docs/general.md covers framework-agnostic items.
#OptimizationImpactCLI-checkable?Plan Required0Use explicit adapter (e.g., adapter-vercel not adapter-auto)Faster, no detection overhead✅ Check configAny1Turbo Build Machines50-70% faster builds❌ Dashboard onlyPro+2On-Demand Concurrent BuildsEliminates deploy queue❌ Dashboard onlyPro+3Prerender Static PagesFewer functions, faster TTFB✅ Audit codeAny4Ignored Build StepSkip irrelevant builds✅ Check vercel.jsonAny5Prioritize Production BuildsProd deploys go first❌ Dashboard onlyPro+6Eliminate Barrel Files10-30% build speedup✅ Audit codeAny7Audit & Trim DependenciesFaster install + bundle✅ Run depcheckAny8GitHub Actions + --prebuiltFull cache control, skip Vercel build✅ Add workflowAny9ISR for Dynamic PagesFewer cold starts✅ Audit routesAny10Instant RollbackZero-downtime recovery✅ vercel rollbackHobby: last only; Pro+: any Pro plan items (#1, #2, #5): If not on Pro, check team plan first. These are the highest-impact free wins on Pro.
For a team called <team-slug>: Turbo machines: https://vercel.com/<team-slug>/<project>/settings → General → Build Machine Concurrent builds: https://vercel.com/teams/<team-slug>/settings → Build Queue Prioritize prod: https://vercel.com/<team-slug>/<project>/settings → Git → Production prioritization
docs/checklist.md — Full detailed checklist with how-to for each item docs/sveltekit.md — SvelteKit-specific optimizations docs/general.md — Framework-agnostic Vercel optimizations docs/github-actions-prebuilt.md — GitHub Actions + vercel deploy --prebuilt guide
Real-world findings from running all 10 checks on a SvelteKit project with 16-18s builds: Half the checklist was overkill — builds were already fast. Triage step now prevents wasted effort. ISR is irrelevant for auth-gated apps — every page served per-user content. Added decision tree. adapter-auto → adapter-vercel was a missed win — not in original 10 but came up in dep audit. Now item #0. Dashboard-only settings are the highest-impact items (Turbo, concurrent, priority) but can't be verified via CLI. Added direct links. GitHub Actions + prebuilt only worth it at 60s+ — for fast builds, the Vercel Git integration is simpler and equally fast. The dep audit found the project was already lean (11 deps, 84MB node_modules, 472K client bundle). Only one unused dep (clsx). Team/plan tier gates most high-impact items — checking plan should be step 1.
Triage: Measure build times + check plan tier Run applicable items from the checklist based on decision tree If SvelteKit, also review docs/sveltekit.md Track findings in a report file (e.g., vercel-speed-report.md) For complex CI needs, follow docs/github-actions-prebuilt.md
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.