원클릭으로 Manus에서 모든 스킬 실행

vercel-developer

스타84

포크21

업데이트2026년 7월 6일 23:08

Full-stack Vercel developer skill for deploying and managing Next.js applications. Covers Deployment (preview, production, Git integration, CLI), Environment Variables (per-environment config, NEXT_PUBLIC_ prefix, secrets), Domains (custom domains, DNS, SSL), Vercel CLI (deploy, env, link, pull, dev, logs), Serverless & Edge Functions, Storage (Blob, KV, Postgres), Caching (ISR, CDN, revalidation), and Integrations (Supabase, Stripe). Use this skill whenever the user mentions Vercel, deploying, vercel deploy, vercel CLI, preview deployment, production deployment, vercel env, vercel domains, serverless functions, edge functions, custom domains, or any task involving deploying a Next.js app. Even if the user just says "deploy this", "push to production", "go live", or "set up hosting" — trigger immediately. Also trigger for deploying a Stripe + Supabase + Next.js stack to Vercel.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Sleestk

Sleestk/Skills-Pipeline

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Vercel Developer Skill

A comprehensive skill for deploying and managing Next.js applications on Vercel. Covers five domains: Deployment, Environment Variables, Domains & SSL, CLI, and Platform Features.

Architecture

vercel-developer/
├── SKILL.md                          ← You are here (orchestrator)
├── references/
│   ├── deployment.md                 ← Deploy flows (Git, CLI, preview, production)
│   ├── environment-variables.md      ← Env var management, secrets, per-environment config
│   ├── domains-ssl.md                ← Custom domains, DNS, SSL certificates
│   ├── cli.md                        ← Full Vercel CLI command reference
│   └── platform-features.md          ← Storage, caching, functions, integrations

Routing

Deployment

If the request involves deploying an app, Git integration, preview deployments, production deploys, rollbacks, CI/CD, or the deployment pipeline: → Read references/deployment.md

Environment Variables

If the request involves setting env vars, the NEXT_PUBLIC_ prefix, secrets management, per-environment configuration (development/preview/production), or pulling env vars locally: → Read references/environment-variables.md

Domains & SSL

If the request involves custom domains, DNS configuration, SSL certificates, domain verification, or domain aliases: → Read references/domains-ssl.md

CLI

If the request involves Vercel CLI commands (vercel, vercel deploy, vercel env, vercel link, vercel pull, vercel dev, vercel logs, etc.): → Read references/cli.md

Platform Features

If the request involves Vercel-specific features like Serverless Functions, Edge Functions, Vercel Blob/KV/Postgres storage, caching (ISR, CDN), Web Application Firewall, Speed Insights, Analytics, or integrations: → Read references/platform-features.md

Multiple Domains

Many requests touch multiple domains. For example, "deploy my Next.js + Stripe + Supabase app with a custom domain" requires Deployment + Environment Variables + Domains & SSL. Read all relevant files.

Default Stack

Framework: Next.js (App Router)
Deployment target: Vercel
CLI: vercel (latest)
Language: TypeScript

Key Principles

Zero-config for Next.js. Vercel auto-detects Next.js and configures builds, serverless functions, and routing automatically.
Git push = deploy. Connect a GitHub/GitLab/Bitbucket repo. Every push to main triggers a production deployment. Every PR gets a preview deployment.
Environment variables must be set before deployment. Env vars are baked into the build. If you add one after deploying, you must redeploy.
NEXT_PUBLIC_ prefix exposes to the browser. Without this prefix, env vars are server-only. Never prefix secret keys with NEXT_PUBLIC_.
Three environments: Development, Preview, Production. Each can have different env var values.
Preview deployments are free and automatic. Every push to a non-production branch creates a preview with a unique URL.
Rollbacks are instant. You can roll back to any previous deployment via Dashboard or CLI.
Edge Functions run globally. Serverless Functions run in a single region by default.

Quick Start

# Install CLI
npm i -g vercel

# Login
vercel login

# Link your project
vercel link

# Pull env vars for local dev
vercel env pull .env.local

# Deploy preview
vercel deploy

# Deploy to production
vercel --prod

Environment Variables for a SaaS Stack

When deploying a Next.js + Supabase + Stripe app, set these in Vercel:

Variable	Prefix?	Description
`NEXT_PUBLIC_SUPABASE_URL`	Yes	Supabase project URL (client-safe)
`NEXT_PUBLIC_SUPABASE_ANON_KEY`	Yes	Supabase anon key (client-safe)
`SUPABASE_SERVICE_ROLE_KEY`	No	Supabase service role (server-only)
`NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY`	Yes	Stripe publishable key (client-safe)
`STRIPE_SECRET_KEY`	No	Stripe secret key (server-only)
`STRIPE_WEBHOOK_SECRET`	No	Stripe webhook signing secret

이 저장소의 다른 Skills

같은 저장소

obsidian-power-user

Sleestk/Skills-Pipeline

Full-featured Obsidian expert covering every official feature, plugin, and syntax. Use this skill for ANYTHING Obsidian-related: vault design, note templates, canvas files, bases, Dataview queries, Templater templates, folder structures, core plugins, community plugins, Obsidian Publish, Web Clipper, CSS snippets, URI links, MOC notes, and more. Trigger on ANY mention of: Obsidian, vault, canvas, base, wikilinks, PKM, second brain, daily notes, note template, Dataview, Templater, MOC, Map of Content, backlinks, note structure, folder structure, knowledge management, markdown note, Obsidian plugin, graph view, properties, frontmatter, callout, embed, slash commands, obsidian publish, web clipper, obsidian URI, obsidian sync, workspaces, PARA method, Zettelkasten. Also trigger on: "organize my notes", "build a vault", "create a note system", "make a canvas", "set up a base", "import my notes". When in doubt — trigger this skill.

2026-07-0684

nextjs-developer

Sleestk/Skills-Pipeline

Expert Next.js 16.2.1 developer skill for frontend and server-side logic. Handles writing, scaffolding, debugging, and explaining Next.js code. Trigger on any mention of: Next.js, app router, pages router, server component, client component, use client, use server, use cache, proxy.ts, middleware.ts, getServerSideProps, getStaticProps, next/image, next/font, next/link, next.config, layout.tsx, page.tsx, loading.tsx, error.tsx, route.ts, or any Next.js file convention, routing question, caching question, or error. Covers routing, Server/Client Components, directives (use cache, use client, use server), Server Actions, Proxy (formerly Middleware), Route Handlers, parallel routes, intercepting routes, caching, metadata, and all file conventions. Even if the user just says "help me build this in Next" or "why is my Next app broken" — trigger immediately.

2026-07-0684

stripe-developer

Sleestk/Skills-Pipeline

Full-stack Stripe developer skill for building payment integrations with Next.js and Supabase. Covers Checkout (hosted and embedded), Products & Prices, Subscriptions & Billing, Webhooks (signature verification, event handling), Customer Portal, the Stripe Node.js SDK, client-side Stripe.js, and the Stripe CLI. Use this skill whenever the user mentions Stripe, payments, checkout, subscriptions, billing, pricing tiers, webhooks, recurring revenue, freemium, paywall, customer portal, Stripe CLI, or any task involving accepting payments. Even if the user just says "add payments", "wire up billing", "set up subscriptions", or "make this a SaaS" — trigger this skill immediately. Also trigger for connecting Stripe to Supabase (syncing subscription status via webhooks + RLS) or deploying a Stripe-integrated app to Vercel.

2026-07-0684

supabase-js

Sleestk/Skills-Pipeline

Full-stack Supabase developer skill for building Next.js applications with Supabase. Covers Database (Postgres tables, schemas, views, indexes, joins, JSON, RLS, CLS, roles, functions, triggers, webhooks, event triggers), Auth (email/password, magic link, OTP, OAuth, anonymous sign-ins, MFA, SSR/PKCE flows, sessions, redirect URLs, user management), the JavaScript client (`@supabase/supabase-js` — select, insert, update, upsert, delete, rpc, filters, modifiers, auth methods), and Next.js integration (`@supabase/ssr`, server/browser clients, proxy/middleware, cookie-based auth). Use this skill whenever the user mentions Supabase, supabase-js, @supabase/ssr, createClient from Supabase, RLS policies, Row Level Security with Supabase, Supabase Auth, supabase.auth, supabase.from, Postgres with Supabase, Supabase database, Supabase Next.js, or any task involving building with Supabase. Even if the user just says "set up auth" or "create a table" in the context of a Supabase project — trigger this skill immediately.

2026-07-0684

creator-editor-brief

Sleestk/Skills-Pipeline

Editor Brief Agent for [Channel]'s YouTube production pipeline. Acts as [Creator]'s Post-Production Director — synthesizes the completed Script, Visual Director Brief, and SEO package into a complete, standalone Editor Brief that a human editor or AI editing tool can execute with zero additional context. Use this skill whenever [Creator] wants to generate an editor brief, editing instructions, cut notes, audio notes, graphics instructions, or post-production direction for a video. Trigger on any mention of: editor brief, editing instructions, post-production, cut notes, timeline structure, B-roll integration, audio mix, export specs, thumbnail pull, Shorts extraction, or when [Creator] uploads a script + visual brief and wants to move into post-production. Even if [Creator] just says 'write the editor brief' or 'give me the edit doc' — trigger this skill immediately.

2026-07-0684

creator-research-agent

Sleestk/Skills-Pipeline

Research Agent for [Channel]'s YouTube production pipeline. Acts as a Frontier Scout — gathering structured intelligence on a video topic so the Script Agent (or [Creator]) can immediately build around it. Use this skill whenever [Creator] asks to "research a video idea", "scout a topic", "research this for me", "pull research on X", or any variation of wanting YouTube video research done. Even if [Creator] only gives a rough idea or one-liner topic, trigger this skill and run the full research brief. Do NOT wait for all the details — start scouting and ask clarifying questions inline if needed.

2026-07-0684

name

vercel-developer

description

Vercel Developer Skill

A comprehensive skill for deploying and managing Next.js applications on Vercel. Covers five domains: Deployment, Environment Variables, Domains & SSL, CLI, and Platform Features.

Architecture

vercel-developer/
├── SKILL.md                          ← You are here (orchestrator)
├── references/
│   ├── deployment.md                 ← Deploy flows (Git, CLI, preview, production)
│   ├── environment-variables.md      ← Env var management, secrets, per-environment config
│   ├── domains-ssl.md                ← Custom domains, DNS, SSL certificates
│   ├── cli.md                        ← Full Vercel CLI command reference
│   └── platform-features.md          ← Storage, caching, functions, integrations

Routing

Deployment

If the request involves deploying an app, Git integration, preview deployments, production deploys, rollbacks, CI/CD, or the deployment pipeline: → Read references/deployment.md

Environment Variables

Domains & SSL

If the request involves custom domains, DNS configuration, SSL certificates, domain verification, or domain aliases: → Read references/domains-ssl.md

CLI

If the request involves Vercel CLI commands (vercel, vercel deploy, vercel env, vercel link, vercel pull, vercel dev, vercel logs, etc.): → Read references/cli.md

Platform Features

Multiple Domains

Default Stack

Framework: Next.js (App Router)
Deployment target: Vercel
CLI: vercel (latest)
Language: TypeScript

Key Principles

Zero-config for Next.js. Vercel auto-detects Next.js and configures builds, serverless functions, and routing automatically.
Git push = deploy. Connect a GitHub/GitLab/Bitbucket repo. Every push to main triggers a production deployment. Every PR gets a preview deployment.
Environment variables must be set before deployment. Env vars are baked into the build. If you add one after deploying, you must redeploy.
NEXT_PUBLIC_ prefix exposes to the browser. Without this prefix, env vars are server-only. Never prefix secret keys with NEXT_PUBLIC_.
Three environments: Development, Preview, Production. Each can have different env var values.
Preview deployments are free and automatic. Every push to a non-production branch creates a preview with a unique URL.
Rollbacks are instant. You can roll back to any previous deployment via Dashboard or CLI.
Edge Functions run globally. Serverless Functions run in a single region by default.

Quick Start

# Install CLI
npm i -g vercel

# Login
vercel login

# Link your project
vercel link

# Pull env vars for local dev
vercel env pull .env.local

# Deploy preview
vercel deploy

# Deploy to production
vercel --prod

Environment Variables for a SaaS Stack

When deploying a Next.js + Supabase + Stripe app, set these in Vercel:

Variable	Prefix?	Description
`NEXT_PUBLIC_SUPABASE_URL`	Yes	Supabase project URL (client-safe)
`NEXT_PUBLIC_SUPABASE_ANON_KEY`	Yes	Supabase anon key (client-safe)
`SUPABASE_SERVICE_ROLE_KEY`	No	Supabase service role (server-only)
`NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY`	Yes	Stripe publishable key (client-safe)
`STRIPE_SECRET_KEY`	No	Stripe secret key (server-only)
`STRIPE_WEBHOOK_SECRET`	No	Stripe webhook signing secret