AGENT SKILL

visual-fidelity-reviewer

Review mobile UI evidence for product fit, hierarchy, composition, polish, distinctiveness, consistency, direction integrity, realistic content, state completeness, and generic-AI patterns. Use before design freeze and after material visual revisions.

License 许可
Apache-2.0
最近更新
2026-08-12
Stars
★ 1
Forks
0

01 前言 Front Matter

name
visual-fidelity-reviewer
description
Review mobile UI evidence for product fit, hierarchy, composition, polish, distinctiveness, consistency, direction integrity, realistic content, state completeness, and generic-AI patterns. Use before design freeze and after material visual revisions.

03 SKILL.md 正文

Visual Fidelity Reviewer

Purpose

Detect product-inappropriate, generic, inconsistent, or under-resolved visual design before approval.

When to use

Use when representative or full-prototype screenshots exist and before any design-freeze decision.

When not to use

Do not review prose as if it were rendered evidence, generate a direction, or treat screenshot similarity as proof of quality.

Required inputs

Permitted evidence sources

  • Local screenshots, prototype behavior, frozen product requirements, approved direction artifacts, and existing QA reports.
  • Human visual judgment documented with evidence.

Expected outputs

  • Visual review.
  • Category scores supported by evidence.
  • Generic-pattern violations and direction-drift findings.
  • P0/P1/P2 issues, structural remediation, and a revise/redesign/approval recommendation.

Ordered workflow

  1. Confirm screenshot coverage and evidence provenance.
  2. Review product fit and workflow clarity before ornament.
  3. Review hierarchy, composition, typography, spacing, alignment, density, surfaces, geometry, icons, and motion evidence.
  4. Check chosen-direction integrity across screens and states.
  5. Run every applicable anti-generic pattern review.
  6. Evaluate realistic content, state completeness, and recovery clarity.
  7. Score only what the evidence supports and surface category weakness.
  8. Require structural remediation for structural failures.

Tools allowed

  • Local screenshot/image inspection, prototype inspection, repository reading, and review-document editing.
  • Existing local comparison evidence when its method is known.

Tools forbidden

  • Network inspiration search, competitor copying, automatic aesthetic approval, hidden score adjustment, production UI changes, and claims based on missing screenshots.

File boundaries

Write only the approved visual-review artifact. Keep remediation edits in a separately authorized task.

Non-negotiable rules

  • Product fit outranks fashionable styling.
  • Severe anti-generic violations block approval.
  • Attractive but product-inappropriate screens fail.
  • Numeric score cannot replace human visual judgment.

Stop conditions

Stop when required screenshots/states are absent, the chosen direction is not documented, or evidence cannot be attributed to the reviewed revision.

Failure conditions

  • The review ignores direction drift or generic composition.
  • Scores lack screenshot evidence.
  • Unresolved issues are hidden in prose or the total score.
  • The review approves screens that are attractive but wrong for the product.

Acceptance criteria

  • Findings are screen/state-specific, evidence-backed, severity-classified, and actionable.
  • The decision is consistent with hard gates and score thresholds.
  • Human judgment points are explicit.

Handoff to the next skill

Return revise/redesign findings to prototype-builder; when freeze-eligible, hand the complete review to design-system-freezer and visual-release-gate.

Required human-review points

  • Product fit, actual direction distinctiveness, premium character, trade-dress risk, monetization ethics, copy tone, emotional fit, and final visual approval.

04 同仓库更多 Skills

sonanh08t4
sonanh08t4/mobile-ui-design-os

valid-skill

Validate a small local skill fixture with one declared reference and one local schema.

★ 1
sonanh08t4
sonanh08t4/mobile-ui-design-os

visual-release-gate

Make a strict evidence-based decision on redesign, refinement, design freeze, Flutter implementation, or release-candidate eligibility using the canonical rubric, hard gates, accessibility findings, unresolved debt, and mandatory human review.

★ 1
sonanh08t4
sonanh08t4/mobile-ui-design-os

visual-direction-lab

Generate and compare at least three materially different mobile visual directions from a validated product design brief. Use when Codex must explore structural visual alternatives instead of defaulting to one generic composition.

★ 1
sonanh08t4
sonanh08t4/mobile-ui-design-os

prototype-builder

Build representative screens or a state-complete interactive mobile prototype from approved direction specifications using an existing authorized prototype environment. Use after direction generation; never use to begin production Flutter UI or to invent missing runtime tooling.

★ 1
sonanh08t4
sonanh08t4/mobile-ui-design-os

mobile-product-interpreter

Derive an evidence-backed mobile product design brief from repository documents, product requirements, user flows, and explicit owner input before visual styling begins. Use when product context must be clarified, normalized, or validated for Design OS work.

★ 1
sonanh08t4
sonanh08t4/mobile-ui-design-os

flutter-ui-handoff

Prepare precise Flutter implementation guidance from an approved design freeze, including token mapping, screen behavior, component variants, states, platform adaptation, assets, semantics, and risks. Use after freeze; do not generate production Flutter UI in this skill.

★ 1