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

nexus-deployments

스타6

포크0

업데이트2026년 3월 4일 02:43

Deployment protocols for Vercel (Next.js Web App), Chrome Web Store packaging (Plasmo Extension), and Supabase production migrations. Use this when setting up CI/CD, preparing a release, or configuring deployment environment variables.

설치

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

Manus에서 실행

출처

MAX-786

MAX-786/project-nexus

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

다운로드

Manus에서 실행

Project Nexus: Deployment & DevOps Protocol

1. Vercel Deployment (Next.js Web App)

Monorepo Handling: If the project is structured as a monorepo (e.g., Turborepo or npm workspaces), ensure the Vercel Root Directory is set to apps/web (or the folder containing the Next.js app).
Build Command: The build command must strictly be npm run build (or pnpm build).
Environment Variables: Never commit .env files. When setting up deployments, explicitly list the required Vercel environment variables (e.g., NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY).
Edge Functions: For long-running AI summarization tasks, ensure the Next.js API routes specify export const maxDuration = 60; to prevent Vercel's default 10-second timeout on the hobby tier.

2. Plasmo Extension Deployment

Production Build: To build the extension for production, run plasmo build --target=chrome-mv3.
Zip Packaging: For Chrome Web Store submission, use plasmo package. This generates the .zip file.
Manifest Validation: Before building, ensure the package.json contains the correct version number, description, and permissions (e.g., storage, activeTab, scripting) required by the Chrome Web Store.

3. Supabase Production Migrations

Database Changes: Never make database schema changes directly in the Supabase production dashboard.
Migration Generation: Always use the Supabase CLI: supabase db diff -f feature_name to generate a migration file.
Type Generation: After a database change, run supabase gen types typescript --local > types/supabase.ts to keep the frontend types perfectly synced with the backend schema.

이 저장소의 다른 Skills

같은 저장소

nexus-docs-manager

MAX-786/project-nexus

Rules for creating, updating, and managing project documentation. Use this skill when analyzing Git commits, updating the README, writing API specs, or acting as the Technical Writer for Project Nexus.

2026-03-096

nexus-github-cli

MAX-786/project-nexus

Act as an autonomous project manager and lead developer. Use the GitHub CLI (`gh`) to orchestrate the entire development lifecycle: tracking tasks on Project Boards, organizing Sprints via Milestones, documenting progress via Issue Comments, and executing code changes via Pull Requests.

2026-03-046

nexus-code-quality

MAX-786/project-nexus

Rules for ESLint, Prettier, and TypeScript strictness. Use this skill when writing new files, refactoring code, or debugging build failures caused by type errors.

2026-03-046

nexus-git-workflow

MAX-786/project-nexus

Guidelines for Git branching, commit messages (Conventional Commits), and Pull Request structures. Use this skill when asked to commit code, create a branch, or write a PR description.

2026-03-046

nexus-marketing-growth

MAX-786/project-nexus

Guidelines for generating marketing copy, Reddit posts, Hacker News launches, and growth strategies for Project Nexus. Use this skill when asked to write public-facing content, launch announcements, or analyze product-market fit.

2026-03-026

nexus-nextjs-dev

MAX-786/project-nexus

Guidelines for writing Next.js App Router frontend code, using Shadcn UI, and TailwindCSS for Project Nexus. Use this when creating or modifying UI components, pages, or client/server interactions.

2026-03-026

name	nexus-deployments
description	Deployment protocols for Vercel (Next.js Web App), Chrome Web Store packaging (Plasmo Extension), and Supabase production migrations. Use this when setting up CI/CD, preparing a release, or configuring deployment environment variables.

Project Nexus: Deployment & DevOps Protocol

1. Vercel Deployment (Next.js Web App)

Monorepo Handling: If the project is structured as a monorepo (e.g., Turborepo or npm workspaces), ensure the Vercel Root Directory is set to apps/web (or the folder containing the Next.js app).
Build Command: The build command must strictly be npm run build (or pnpm build).
Environment Variables: Never commit .env files. When setting up deployments, explicitly list the required Vercel environment variables (e.g., NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY).
Edge Functions: For long-running AI summarization tasks, ensure the Next.js API routes specify export const maxDuration = 60; to prevent Vercel's default 10-second timeout on the hobby tier.

2. Plasmo Extension Deployment

Production Build: To build the extension for production, run plasmo build --target=chrome-mv3.
Zip Packaging: For Chrome Web Store submission, use plasmo package. This generates the .zip file.
Manifest Validation: Before building, ensure the package.json contains the correct version number, description, and permissions (e.g., storage, activeTab, scripting) required by the Chrome Web Store.

3. Supabase Production Migrations

Database Changes: Never make database schema changes directly in the Supabase production dashboard.
Migration Generation: Always use the Supabase CLI: supabase db diff -f feature_name to generate a migration file.
Type Generation: After a database change, run supabase gen types typescript --local > types/supabase.ts to keep the frontend types perfectly synced with the backend schema.