Receber por email
← Voltar para o catálogo

deploy

Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/deploy-mpsza9uk/svg)](https://www.skillteca.com.br/skills/deploy-mpsza9uk)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Deploy Skill

NEVER deploy without completing ALL steps below.

Required Workflow

Before ANY deployment (vercel, git push to main, etc.):

1. Build Locally

pnpm build
  • Must complete with zero errors
  • Check output for warnings

2. Start Local Dev Server

pnpm dev
  • Server must start successfully

3. Test in Browser

  • Open the local URL in Chrome DevTools MCP
  • Test ALL changed functionality manually:
  • Click buttons, verify they work
  • Test keyboard input if applicable
  • Submit forms, verify responses
  • Check for console errors

4. Verify Tests Pass (if tests exist)

pnpm test

5. Only Then Deploy

After ALL above steps pass:

vercel --prod

Rules

  1. NO SHORTCUTS - Every step must be completed
  2. NO ASSUMPTIONS - "It worked before" is not verification
  3. TEST AFTER CHANGES - Any code change requires re-testing
  4. LOCAL FIRST - Never deploy to see if something works

Common Mistakes to Avoid

  • Deploying immediately after build without browser testing
  • Assuming dependency changes don't break anything
  • Skipping keyboard/interaction testing
  • Deploying to "check if it works on Vercel"

When User Says "Deploy"

  1. Ask: "Have you verified locally? Let me run through the checklist."
  2. Run build
  3. Start dev server
  4. Test in browser via Chrome DevTools MCP
  5. Only after confirming everything works, deploy
Compartilhar X LinkedIn