菜单
[ARCHIVED] The visual-proof-pr local dev-loop skill has been archived to docs/legacy/skills/visual-proof-pr/. This stub stays at the original path so references to .claude/skills/visual-proof-pr/ do not break. Do NOT trigger this skill — it no longer carries an active workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Non-technical install guide and onboarding walkthrough for TeamBrain. Reads INSTALL.md and narrates each step in plain Chinese for non-developers. Handles install errors by matching against known error patterns and explaining the fix aloud. Use when: "install", "onboarding", "walkthrough", "pnpm 是什么", "怎么安装", "我装不上", "non-technical install", "帮我安装", "安装步骤", "第一次使用", "how do I install", "set up this project".
Visual-proof guided PR workflow: design-shotgun variants → design-html finalization → Chrome pop-open human verify → implement → /review → squash-merge PR. Use when: "implement visual-proof PR", "visual proof workflow", "design → PR" Triggers: visual proof PR, design to PR, implement with visual proof
TeamBrain repo **24h window delta** report — 拉过去 N 小时窗口内 PR/issue 的创建/合并/关闭事件，按主题（features/bugfixes/docs/infra）分组，鸭语汇报。仅当用户问 `what happened since yesterday` / `explore today's issues and PRs` / `daily standup` / `/daily-standup` / `今天的 issue 和 PR` / `昨天到今天发生了啥` / `show me yesterday's activity` / `过去 24 小时 GitHub 活动` / `9 点到 9 点发生了什么` 这类**时间窗口 delta 类**问题时触发。**不要在以下情况触发**：(a) 用户问当前快照（`status of all issues` / `所有 open issue` → 用 `repo-issues-status` skill）；(b) 用户问今日开工晨报（`/newday` → 用 `newday` skill，覆盖 worktree + 当前开放工作而非 24h delta）；(c) 用户问单 issue/PR 状态（`#330 怎么样` → 用 `gh issue view`/`gh pr view`）。匹配命中后默认拉 yesterday 09:00 +0800 → today 09:00 +0800 的窗口，事件按 PRs merged / created / closed-without-merge / 还开着 + Issues created / closed / 还开着 六桶分组，再按主题二次归类，全文用 呷呷~ 鸭鸭 口吻包裹。
TeamBrain repo **24h window delta** report — 拉过去 N 小时窗口内 PR/issue 的创建/合并/关闭事件，按主题（features/bugfixes/docs/infra）分组，鸭语汇报。仅当用户问 `what happened since yesterday` / `explore today's issues and PRs` / `daily standup` / `/daily-standup` / `今天的 issue 和 PR` / `昨天到今天发生了啥` / `show me yesterday's activity` / `过去 24 小时 GitHub 活动` / `9 点到 9 点发生了什么` 这类**时间窗口 delta 类**问题时触发。**不要在以下情况触发**：(a) 用户问当前快照（`status of all issues` / `所有 open issue` → 用 `repo-issues-status` skill）；(b) 用户问今日开工晨报（`/newday` → 用 `newday` skill，覆盖 worktree + 当前开放工作而非 24h delta）；(c) 用户问单 issue/PR 状态（`#330 怎么样` → 用 `gh issue view`/`gh pr view`）。匹配命中后默认拉 yesterday 09:00 +0800 → today 09:00 +0800 的窗口，事件按 PRs merged / created / closed-without-merge / 还开着 + Issues created / closed / 还开着 六桶分组，再按主题二次归类，全文用 呷呷~ 鸭鸭 口吻包裹。
CEO 鸭的"今日开工"晨报 — 从远程拉取代码、检查所有 worktree、汇总开放 PR 与 issue，并用非技术语言告诉鸭老板"今天有什么决策要做、有什么活儿可以推进"。手动触发：/newday。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
| name | visual-proof-pr |
| preamble-tier | 2 |
| version | 2.0.0-archived |
| description | [ARCHIVED] The visual-proof-pr local dev-loop skill has been archived to docs/legacy/skills/visual-proof-pr/. This stub stays at the original path so references to .claude/skills/visual-proof-pr/ do not break. Do NOT trigger this skill — it no longer carries an active workflow. |
This skill is archived. It is no longer an active workflow.
The original visual-proof-pr skill (a local dev loop:
design-shotgun → design-html → Chrome verify → implement → /review → squash-merge)
plus its judge-harness.md were moved to:
docs/legacy/skills/visual-proof-pr/
├── SKILL.md # the original 7-step workflow
└── judge-harness.md # the original 4-probe judge harness
This stub remains at .claude/skills/visual-proof-pr/SKILL.md only so existing
references to the path stay valid.
A walkthrough of the archived skill — the 7 steps, the judge probes, the
"who commits them?" answer, and the name-collision caveat with
docs/VISUAL-PROOF-PR.md — was produced via /talk-html:
docs/VISUAL-PROOF-PR.md is a different thing with the same name: it is the
reviewer-facing evidence workflow (propose an issue → make the PR without asking
→ append an HTML proof comment). That doc is canonical and active. This skill is
not — it was the local design-to-PR dev loop, now archived.