Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

vercel-next-deploy

Étoiles24

Forks8

Mis à jour15 février 2026 à 13:21

Deploy and manage this Next.js app on Vercel (project linking, env vars, preview/prod, domains). Use when the user mentions Vercel, deployment, environment variables, previews, or domains.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

gradient-industrial-robotics

gradient-industrial-robotics/GradientOS

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	vercel-next-deploy
description	Deploy and manage this Next.js app on Vercel (project linking, env vars, preview/prod, domains). Use when the user mentions Vercel, deployment, environment variables, previews, or domains.

Vercel deploy (Next.js)

Quick checklist (before deploying)

npm run lint
npm run build
No secrets committed (env vars belong in Vercel and .env.local)

Deploy via Vercel dashboard (recommended)

Import the repo in Vercel.
Framework preset: Next.js (auto-detected).
Install command: npm install (default).
Build command: npm run build (default).
Output: leave default (Next.js uses .next).
Add environment variables:
- Vercel → Project → Settings → Environment Variables
- Set values per environment (Development / Preview / Production)

Deploy via CLI (optional)

First deploy: npx vercel
Promote to production: npx vercel --prod

Common fixes

If builds fail due to missing env vars, add them in Vercel settings and redeploy.
Don’t add vercel.json unless you need custom rewrites/headers/cron jobs.

Plus depuis ce dépôt

même dépôt

devlog-loop

gradient-industrial-robotics/GradientOS

Keep a concise, chronological DEVLOG for meaningful tasks. Use when work should be documented for handoff, traceability, or future debugging.

2026-02-1524

learning-scratchpad-loop

gradient-industrial-robotics/GradientOS

Maintain a repo-local learning scratchpad that compounds improvements across sessions by recording mistakes, user corrections, preferences, what worked, and what failed. Use when a user asks for persistent self-improvement, memory across sessions, agent notes, a scratchpad, or a workflow where Codex should adapt based on prior errors and feedback.

2026-02-1524

next-upgrade

gradient-industrial-robotics/GradientOS

Upgrade Next.js to the latest version following official migration guides and codemods

2026-02-1524

name	vercel-next-deploy
description	Deploy and manage this Next.js app on Vercel (project linking, env vars, preview/prod, domains). Use when the user mentions Vercel, deployment, environment variables, previews, or domains.

Vercel deploy (Next.js)

Quick checklist (before deploying)

npm run lint
npm run build
No secrets committed (env vars belong in Vercel and .env.local)

Deploy via Vercel dashboard (recommended)

Import the repo in Vercel.
Framework preset: Next.js (auto-detected).
Install command: npm install (default).
Build command: npm run build (default).
Output: leave default (Next.js uses .next).
Add environment variables:
- Vercel → Project → Settings → Environment Variables
- Set values per environment (Development / Preview / Production)

Deploy via CLI (optional)

First deploy: npx vercel
Promote to production: npx vercel --prod

Common fixes

If builds fail due to missing env vars, add them in Vercel settings and redeploy.
Don’t add vercel.json unless you need custom rewrites/headers/cron jobs.