Communitygithub.com

visual-verdict

結構化的視覺問答判決,用於截圖與參考圖像的比對。

visual-verdict 是什麼?

這個技能用於比較生成的 UI 截圖與一張或多張參考圖像,並回傳一個嚴格的 JSON 判決,以驅動下一次編輯迭代。它特別適合需要確保版面、間距、字體排版與元件樣式等視覺保真度的任務。此技能支援多種平台,且能透過可選的類別提示(例如 `hackernews`、`sns-feed`、`dashboard`)來輔助比對。運作方式包括設定 90 分以上的通過門檻、在分數不足時自動建議重跑技能以進行修復,以及利用像素級差異工具作為次要除錯輔助。最終輸出包含分數、判決結果、類別匹配狀態、具體差異清單、可操作的修改建議以及簡短的原因說明,讓開發者能精準地進行下一步修改。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/visual-verdict

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

<Use_When>

  • 任務包含視覺保真度要求(版面、間距、字體排版、元件樣式)
  • 你已有一張生成的截圖以及至少一張參考圖像
  • 你需要在繼續編輯之前取得確定性的通過/失敗指引 </Use_When>

<Output_Contract> 回傳 僅 JSON,格式如下:

{
  "score": 0,
  "verdict": "revise",
  "category_match": false,
  "differences": ["..."],
  "suggestions": ["..."],
  "reasoning": "short explanation"
}

規則:

  • score:整數 0-100
  • verdict:簡短狀態(pass、revise 或 fail)
  • category_match:當生成的截圖符合預期的 UI 類別/樣式時為 true
  • differences[]:具體的視覺差異(版面、間距、字體排版、顏色、層級)
  • suggestions[]:可操作的下一步編輯建議,與差異相關聯
  • reasoning:1-2 句摘要說明 </Output_Contract>

<Threshold_And_Loop>

  • 目標通過門檻為 90+。
  • 如果 score < 90,請繼續編輯,並在進行任何進一步的視覺審查之前重新執行 /oh-my-claudecode:visual-verdict。
  • 不要 將視覺任務視為完成,直到下一張截圖通過門檻為止。 </Threshold_And_Loop>

<Debug_Visualization> 當差異診斷困難時:

  1. 以 $visual-verdict 作為權威決策。
  2. 使用像素級差異工具(像素差異 / pixelmatch 疊加)作為次要除錯輔助,以定位熱點區域。
  3. 將像素差異熱點轉換為具體的 differences[] 和 suggestions[] 更新。 </Debug_Visualization>

任務:{{ARGUMENTS}}

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

agent-doc-discipline

Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

ask

Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly

ask-navigator

Shipyard

autopilot

Full autonomous execution from idea to working code

autoresearch

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

cancel

Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

configure-notifications

Configure notification integrations (Telegram, Discord, Slack) via natural language

debug

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

drydock

Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.

execute

Carry an approved task through to working, verified code

external-context

Invoke parallel document-specialist agents for external web searches and documentation lookup

graph

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

harbor

Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.

hud

Configure HUD display options (layout, presets, display elements)

launch

Shipyard

loft

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

相關技能