vercel-pack

Execute apply Vercel advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Vercel support escalation. Trigger with phrases like "vercel hard bug", "vercel mystery error", "vercel impossible to debug", "difficult vercel issue", "vercel deep debug".

Execute choose and implement Vercel validated architecture blueprints for different scales. Use when designing new Vercel integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Vercel applications. Trigger with phrases like "vercel architecture", "vercel blueprint", "how to structure vercel", "vercel project layout", "vercel microservice".

Configure Vercel CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Vercel tests into your build process. Trigger with phrases like "vercel CI", "vercel GitHub Actions", "vercel automated tests", "CI vercel".

Execute diagnose and fix Vercel common errors and exceptions. Use when encountering Vercel errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel".

Optimize Vercel costs through tier selection, sampling, and usage monitoring. Use when analyzing Vercel billing, reducing API costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "vercel cost", "vercel billing", "reduce vercel costs", "vercel pricing", "vercel expensive", "vercel budget".