runtime-parity-verification
防止仅凭编译/截图判断通过，覆盖真实运行态验证场景。
需要访问运行环境或凭证以查询/比对运行态，可能涉及敏感数据访问。
在声称完成前核验运行中应用核心流程与后端源的一致性。
在你说功能做完前，把运行中的应用流程和后端真实状态（DB/API/daemon 等）逐步比对核验，确保 UI 表现不是假象。适合在验收/迭代阶段对任何用户可见流（Web、macOS、iOS、agent、CLI/TUI）做最后确认，尤其遇到“点了没反应”“不显示/显示错误数据”这种症状。特别之处是屏幕无关的实时校验——不接受仅靠编译绿灯、单测或截图作为完成证明。
▸ 展开 SKILL.md 英文原文
Use in Phase 4/5 (Validate/Iterate) for ANY change to a user-visible flow — web, macOS, iOS, agent, or CLI/TUI — before claiming "done". Verifies the RUNNING app's core flow by cross-checking the rendered/queryable UI against the backing source-of-truth (DB/API/daemon/tool-state), screen-independently. Triggers — "verify it works", "confirm the fix", "does X actually work", "nothing happens when I…", "not showing", "shows empty/wrong data", uiTarget != null, or any "action does nothing / data not displaying / stale projection" symptom. Compile-green and a passing unit test do NOT satisfy this; neither does a screenshot alone.
帮我安装这个 skill：https://raw.githubusercontent.com/tyroneross/build-loop/main/skills/runtime-parity-verification/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/tyroneross/build-loop/main/skills/runtime-parity-verification/SKILL.md"# Runtime Parity Verification **The recurring failure this prevents:** an agent ships UI/feature work, reports "compiles green / tests pass / committed," and never confirms the **running** app's core flow actually works — or confirms it only by **screenshot**, which is screen-dependent and gets silently deferred (e.g. the user's display locks). The whole "X doesn't work / isn't showing / shows mock/empty despite real data / stale projection" bug class is a **divergence between what the UI renders and the authoritative backend state.** One cheap, headless check catches the entire family. ## The invariant to assert > For the user's core flow, the **rendered/queryable UI state must equal the