'vercel' 검색 결과

Manage Vercel environment variables safely. Environments, vercel env ls/add/update/rm/pull/run, sensitive variables, NEXT_PUBLIC exposure, when changes take effect. Use when adding, rotating, auditing or pulling Vercel env vars.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy and optimize applications on Vercel with preview deployments, edge functions, environment variables, and performance monitoring. Use when deploying Next.js applications, setting up preview deployments per pull request, configuring environment variables, using Vercel Edge Functions, optimizing build performance, implementing redirects and rewrites, configuring custom domains, or monitoring application performance with Vercel Analytics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy applications and websites to Vercel using the bundled `scripts/deploy.sh` claimable-preview flow. Use when the user asks to deploy to Vercel, wants a preview URL, or says to push a project live on Vercel.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React와 Next.js의 로딩과 조작 반응 속도를 점검하는 지침입니다. 데이터 요청 대기, 초기 JavaScript 용량, 반복 렌더링 등을 우선순위에 따라 살펴봅니다.

• 페이지 로딩 지연 조사
• 브라우저에 전달하는 JavaScript 용량 점검
• 반복 렌더링과 조작 지연 줄이기

Build HTML/CSS pages using visual specifications from 54 established websites, including Stripe, Linear, and Vercel. Templates provide colors, typography, spacing, component styles, and layouts that adapt to different screen sizes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a landing page inspired by Stripe
• Designing a dashboard inspired by Linear
• Styling a documentation website

Prepare current changes for a GitHub pull request by formatting affected files, checking builds and style, committing, and pushing. Create or update the PR, link related issues, and add page previews when available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Opening a pull request for the current feature
• Updating an existing PR with local changes
• Formatting changes and checking builds before submission

Collect daily AI release news from major labs, product changelogs, blogs, and Hacker News. Remove previously reported items and email a digest with source links and brief explanations tailored to the intended audience.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Receiving a daily AI release digest
• Tracking changes to AI development tools
• Sharing relevant AI updates with a team

Write, review, and refactor React and Next.js code using performance guidelines ranked by impact. Covers sequential data requests, downloaded code size, server work, and unnecessary rendering to guide concrete implementation improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review React and Next.js code for performance issues
• Improve data fetching that waits on sequential requests
• Reduce downloaded code size and loading time

Get documentation-based help with deepsec, an AI vulnerability scanner. Initialize or resume setup, configure scans and model credentials, and create detection rules or plugins using the documentation bundled with the installed version.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Initializing deepsec and resuming interrupted setup
• Configuring scans, models, and credentials
• Creating or customizing vulnerability detection rules

Apply Vercel Engineering’s performance guidelines when writing, reviewing, or refactoring React and Next.js code. Prioritize improvements to data fetching, downloaded code size, server processing, and unnecessary rendering using rules with explanations and code examples.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review React components for performance issues
• Improve data fetching in Next.js pages
• Reduce downloaded code and loading time

Write, review, and refactor React and Next.js code using performance guidelines from Vercel Engineering. Prioritize improvements to data fetching, downloaded code size, server processing, and unnecessary rendering, with rule files providing explanations and code examples.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing React code for performance issues
• Reducing delays in Next.js data fetching
• Reducing downloaded code size and load times

Investigate subdomain takeover risks caused by DNS records pointing to abandoned services. The skill covers discovery, provider error checks, resource claimability, and evidence collection, then examines potential effects on login flows, shared cookies, and trusted content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding DNS records that point to abandoned services
• Manually verifying automated takeover scan results
• Assessing effects on login flows and shared cookies

Build Next.js 14+ applications with App Router, covering pages, server-side processing, data fetching, and caching. The skill also guides performance improvements, search engine metadata, and production deployment to Vercel or a self-hosted environment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building pages and layouts with App Router
• Implementing form updates with Server Actions
• Configuring data fetching and cache revalidation

Next.js adapter for embedding emulators directly in a Next.js app via @emulators/adapter-next. Use when the user needs to embed emulators in Next.js, set up same-origin OAuth for Vercel preview deployments, create an emulate catch-all route handler, configure Auth.js/NextAuth with embedded emulators, add persistence to embedded emulators, or wrap next.config with withEmulate. Triggers include "Next.js emulator", "adapter-next", "embedded emulator", "same-origin OAuth", "Vercel preview", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Next.js app.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guide for Vercel AI SDK (Core, UI, RSC), streaming structured data, multi-provider model switching, tool calling loops, and React 19/Next.js 15 AI engineering / Panduan ahli Vercel AI SDK, streaming data terstruktur, dan integrasi AI pada React 19/Next.js 15.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply Vercel deployment, edge function, and environment variable patterns. Use when deploying to Vercel.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work with the @upstash/redis TypeScript/JavaScript SDK, a serverless HTTP-based Redis client for Next.js, Vercel, Cloudflare Workers, edge runtimes, and Node.js. Use when adding a cache (cache-aside, write-through, TTL and expiration strategies), session storage and user sessions, a key-value store, leaderboards and rankings with sorted sets, counters, distributed locks, queues with lists, streams and consumer groups, sparse index-addressed arrays and ring buffers (ARSET, ARINSERT, ARRING, ARGREP, AROP), embeddings and nearest-neighbour vector search stored inside Redis (VECTOR commands via redis.vector, separate from @upstash/vector), JSON documents, pipelines and MULTI/EXEC transactions, Lua scripting, read replicas, or full-text search, typo-tolerant search, facets, aggregations, and search over Redis stream entries with Upstash Redis Search (different from regular FT.SEARCH; also available for TCP clients via @upstash/search-redis and @upstash/search-ioredis). Also use when migrating from ioredis or node-redis, when a Redis connection is needed from a serverless function without connection pooling, when integrating @upstash/ratelimit, or when the user says Redis cache, KV store, session store, serverless Redis, or Upstash Redis. Also use when building AI agents on Redis with Upstash AgentKit (agent memory, chat history, RAG tools, tool caching, chat persistence, resumable streams, distributed locks) for the Vercel AI SDK, TanStack AI, or Vercel Eve. Supports automatic serialization/deserialization of JavaScript types.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use @vercel/error to design, implement, migrate, audit, or review structured TypeScript errors. Trigger when a project uses or adopts the package, or when work involves its codes, fields, factories, HTTP APIs, telemetry, or terminal output. Use native Error for local failures that need no stable identity, recovery guidance, observability, or transport.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Vercel deployments, projects, environment variables, domains, DNS, and build/runtime logs via REST API. Use when the user wants to deploy, check a deploy status, rotate env vars, attach custom domains, or investigate failed builds without the Vercel MCP installed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.