Back to Details

ship

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Step 0 — is the kit here? This skill reads files from the kit. Check once: 
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING
On 
KIT_MISSING
only the skill folders were installed, which is what 
npx skills add
does. Say so plainly, point the user at 
npx ux-ui-agent-skills init
or the plugin install, and stop. Do not guess the contents of a file you could not open.
Gate first, then prepare the release. Do nothing destructive without explicit confirmation (no tag, no publish) — this command verifies and drafts only.
  1. Quality gate (must be fully green before continuing):
    • node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs
      — report the real N/N.
    • node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs examples
      — no overflow at 280/320/414.
    • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/check_no_emoji.py
      — UI + taste + instruction surface. If anything fails, stop and fix; do not proceed to the checklist.
  2. Release checklist (per the project release rule):
    • Update 
      README.md
      : version badge, "current" line, and changelog entry.
    • Confirm the bump level (major/minor/patch) with the user — it is their call.
    • Confirm 
      examples/apple-home
      stays gitignored (local IP).
    • List the commits since the last tag so the changelog is accurate.
  3. Output a ready-to-review summary: the green N/N line, the proposed version, and the drafted changelog entry. Wait for the user to approve before any 
    git tag
    / publish step.
步骤 0——kit 是否存在？ 此 skill 会从 kit 中读取文件。检查一次： 
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING
如果出现 
KIT_MISSING
，说明只安装了 skill 文件夹，这正是 
npx skills add
的作用。明确告知用户，指引用户使用 
npx ux-ui-agent-skills init
或安装 plugin，然后停止。不要猜测无法打开的文件内容。
先运行门禁，然后准备发布。没有明确确认时，不要执行任何破坏性操作（不创建 tag、不执行 publish）——此命令仅执行验证和起草。
  1. 质量门禁（继续之前必须全部通过）：
    • node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs
      ——报告实际的 N/N 结果。
    • node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs examples
      ——在 280/320/414 下均不得出现 overflow。
    • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/check_no_emoji.py
      ——检查 UI、审美与指令文案。 如果有任何检查失败，请停止并修复；不要继续生成检查清单。
  2. 发布检查清单（依据项目的发布规则）：
    • 更新 
      README.md
      ：version badge、“current” 行和 changelog 条目。
    • 与用户确认 bump 级别（major/minor/patch）——由用户决定。
    • 确认 
      examples/apple-home
      保持被 gitignore（本地 IP）。
    • 列出上一个 tag 以来的 commits，确保 changelog 准确。
  3. 输出可供审核的摘要：N/N 全绿的结果行、建议的版本号，以及起草的 changelog 条目。在执行任何 
    git tag
    / publish 步骤之前，等待用户批准。