vercel
/vercel
Pomaga w pracy z platformą Vercel: wdrożenia Next.js, Edge Middleware, funkcje serverless, Turborepo i analityka.
- Autor
- G1Joshi ↗
- Repozytorium
- Agent-Skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 01.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 01.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pomaga w pracy z platformą Vercel: wdrożenia Next.js, Edge Middleware, funkcje serverless, Turborepo i analityka.
Oryginalny opis (EN)
Expert Vercel platform assistance covering Next.js deployment, Edge Middleware, Serverless Functions, Turborepo, and analytics. Use when deploying frontend frameworks and serverless backends globally.
Jak działa
- When to Use
- Quick Start
- Core Concepts
- Common Patterns
- Best Practices
- Troubleshooting
- References
Podgląd SKILL.md
---
name: vercel
description: Expert Vercel platform assistance covering Next.js deployment, Edge Middleware, Serverless Functions, Turborepo, and analytics. Use when deploying frontend frameworks and serverless backends globally.
---
# Vercel
Vercel is a frontend cloud platform providing automated CI/CD deployments, edge middleware, global content distribution, and serverless compute tailored for modern web frameworks.
## When to Use
- **Production Next.js & Frontend Deployment**: First-party platform optimized for Next.js, React, SvelteKit, and Nuxt.
- **Vercel Edge Functions & Middleware**: Sub-millisecond routing, A/B testing, and authentication at the global edge.
- **Instant Preview Deployments**: Automated unique URLs for every pull request branch with visual feedback and commenting.
- **Serverless Compute with Fluid Compute**: Scaling serverless execution transparently without cold start delays.
## Quick Start
```bash
npm i -g vercel
# Deploy (Preview)
vercel
# Deploy (Production)
vercel --prod
```
## Core Concepts
### Edge Middleware Configuration (middleware.ts)
Executing routing and authentication checks at the network edge:
```typescript
// middleware.ts
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";
export function middleware(request: NextRequest) {
const token = request.cookies.get("auth_token")?.value;
// Protect dashboard routes
if (request.nextUrl.pathname.startsWith("/dashboard") && !token) {
const loginUrl = new URL("/login", request.url);
loginUrl.searchParams.set("from", request.nextUrl.pathname);
return NextResponse.redirect(loginUrl);
}
// Geolocation header injection
const response = NextResponse.next();
const country = request.geo?.country || "US";
response.headers.set("x-user-country", country);
return response;
}
export const config = {
matcher: ["/dashboard/:path*", "/api/secure/:path*"],
};
```
### Declarative Vercel Configuration (vercel.json)
Configuring custom headers, rewrites, and function memory:
```json
{
"$schema": "https://openapi.vercel.sh/vercel.json",
"cleanUrls": true,
"trailingSlash": false,
"headers": [
{
"source": "/(.*)",
"headers": [
{ "key": "X-Content-Type-Options", "value": "nosniff" },
{ "key": "X-Frame-Options", "value": "DENY" }
]
}
],
"functions": {
"api/export-pdf.ts": {
"memory": 1024,
"maxDuration": 30
}
}
}
```
### Vercel CLI Deployment Operations
Deploying and pulling remote environments:
```bash
# Link local repository to Vercel project
vercel link
# Pull production environment variables to local .env
vercel env pull .env.local
# Deploy preview build to Vercel edge network
vercel
# Deploy to production domain
vercel --prod
```
## Common Patterns
### Geolocation Edge Middleware with Custom Rewrites
**Problem**: Personalizing content by visitor country without server-side rendering latency.
**Solution**:
Use Vercel Edge Middleware with geolocation:
```typescript
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";
export function middleware(request: NextRequest) {
const country = request.geo?.country || "US";
if (country === "GB") {
return NextResponse.rewrite(new URL("/uk", request.url));
}
return NextResponse.next();
}
export const config = {
matcher: ["/"],
};
```
## Best Practices
**Do**:
- Leverage Vercel's native Next.js 15 App Router optimizations (RSC, Server Actions, streaming).
- Pull environment variables securely using `vercel env pull` rather than manually copying secrets.
- Use Edge Middleware for lightweight tasks (redirects, header injection); offload heavy computation to Serverless Functions.
- Configure `maxDuration` in `vercel.json` if background operations require more than default serverless timeout.
**Don't**:
- Perform long-running background tasks inside Vercel Edge Middleware; it has strict CPU runtime limits.
- Commit `.vercel` or `.env.local` directories to source control.
- Bypass Vercel deployment preview gates for production merges.
## Troubleshooting
| Error | Cause | Solution |
| :------------------------------ | :------------------------------------------------------------------------------------ | :---------------------------------------------------------------------------------------- |
| `FUNCTION_INVOCATION_TIMEOUT` | Serverless Function execution exceeded plan duration limit (15s hobby, 60s pro). | Optimize slow external queries or split into background task. |
| `Build Cache Miss on Turborepo` | Environment variables changing between builds without being declared in `turbo.json`. | Add cache-invalidating env vars to `globalEnv` in `turbo.json`. |
| `404 Not Found on static asset` | Asset path missing leading slash or output directory misconfigured. | Verify `outputDirectory` setting matches framework build output (e.g. `dist` or `.next`). |
## References
- [Vercel Documentation](https://vercel.com/docs)
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · G1Joshi/Agent-Skills | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| remotion-dev/remotion | 100 | MIT |
| OpenHands/extensions | 100 | MIT |
| AceDataCloud/Skills | 100 | Apache-2.0 |
| getsentry/junior | 100 | Apache-2.0 |
| Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations | 100 | MIT |
| vercel-labs/emulate | 95 | Apache-2.0 |
Migawka bazy z 28.10.2026 · wersja paczki 49281604e15f (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90vercel-functions-runtime
Pomaga budować funkcje serverless i Edge Runtime na Vercelu, w tym zadania cykliczne i middleware routingu. - 100managing-vercel
Obsługuje Vercel przez CLI: wdrożenia frontendu, funkcje bezserwerowe, sieć brzegową, domeny, zmienne środowiskowe i debugowanie wdrożeń. - 95vercel-functions
Doradza w konfiguracji i optymalizacji funkcji serwerowych Vercel: Edge, streaming, Fluid Compute i zadania cron. - 100vercel-developer
Obsługuje wdrożenia Next.js w Vercel: środowiska, zmienne, domeny, CLI, funkcje serverless, cache i integracje z bazami. - 100vercel-architecture-variants
Pomaga wybrać i wdrożyć architekturę projektów Vercel dla różnych skal: statyczną, serverless lub edge, oraz strukturę wielu projektów i monorepo. - 100serverless-development
Pomaga w budowie aplikacji serverless: AWS Lambda, Vercel Edge Functions, Cloudflare Workers, zimne starty, wzorce wdrożeń i infrastruktura jako kod w SST i Serverless Framework.