visual-evidence-gate
Use after requirements are approved and before UI implementation when a product feature needs Pencil or Figma visual design evidence.
它会碰到什么
扫了多少1 个文本文件,2 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Visual Evidence Gate
This skill turns Pencil/Figma images into a machine-reviewable handoff contract. It is the bridge between requirement approval, visual design, and HeroUI implementation.
Input Artifacts
00-stage.json00-artifact-registry.json- Product, IA, interaction, state, frontend/HeroUI, and acceptance contracts
10-visual-confirmation-plan.md- Pencil or Figma exports and approval record
Output Artifact
docs/full-stack-development/requirements/<feature-slug>/04-visual/visual-evidence.md
Required MCP Tool
generate_design_board_inventoryreview_visual_evidencereview_stage_gate
Hard Stops
- Do not start Pencil/Figma until requirement approval and the visual-design stage gate pass.
- Do not start UI implementation from a single screenshot, chat approval, or desktop-only export.
- Do not accept visual approval without desktop, mobile, component-detail, and state-matrix boards.
- Do not reuse stale visuals after
00-stage.json.latestChangeIdchanges. - Do not let
approvals.visualDesignApproved: truebypassreview_visual_evidence.
Pressure Test Responsibility
- Desktop-only export must block.
- Missing component-detail coverage must block.
- Missing state-matrix coverage must block.
- Missing user approval record must block.
- Stale change id must block after a requirement change.
Next Gate
implementationmay start only whenreview_visual_evidence.statusispassandreview_stage_gatealso passes fortargetStage: "implementation".
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
星标★ 1,027
本站分层T1
该仓技能数1910
原文件路径
plugins/kevin592/codex-full-stack-workflow/skills/visual-evidence-gate/SKILL.md