Back to Details

deploy

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Deploy Skill

部署Skill

NEVER deploy without completing ALL steps below.
绝对不能在未完成以下所有步骤的情况下部署。

Required Workflow

必备工作流程

Before ANY deployment (vercel, git push to main, etc.):
在任何部署操作（vercel、git push到main分支等）之前：

1. Build Locally

1. 本地构建

bash
pnpm build
  • Must complete with zero errors
  • Check output for warnings
bash
pnpm build
  • 必须零错误完成
  • 检查输出中的警告信息

2. Start Local Dev Server

2. 启动本地开发服务器

bash
pnpm dev
  • Server must start successfully
bash
pnpm dev
  • 服务器必须成功启动

3. Test in Browser

3. 浏览器测试

  • 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
  • 在Chrome DevTools MCP中打开本地URL
  • 手动测试所有变更的功能：
    • 点击按钮，验证功能正常
    • 如有需要，测试键盘输入
    • 提交表单，验证响应结果
    • 检查控制台是否有错误

4. Verify Tests Pass (if tests exist)

4. 验证测试通过（如果存在测试用例）

bash
pnpm test
bash
pnpm test

5. Only Then Deploy

5. 仅在此时执行部署

After ALL above steps pass:
bash
vercel --prod
在所有上述步骤都通过后：
bash
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
  1. 禁止走捷径 - 必须完成每一个步骤
  2. 禁止主观假设 - "之前正常工作"不能作为验证依据
  3. 变更后必须测试 - 任何代码变更都需要重新测试
  4. 本地优先 - 绝不能通过部署来验证功能是否正常

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"
  • 构建完成后立即部署，跳过浏览器测试
  • 假设依赖变更不会破坏任何功能
  • 跳过键盘/交互测试
  • 为了“验证在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
  1. 询问：“你已经在本地验证过了吗？让我过一遍检查清单。”
  2. 执行构建
  3. 启动开发服务器
  4. 通过Chrome DevTools MCP在浏览器中测试
  5. 只有在确认所有功能正常后，再进行部署