[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RS249WNA0BJTC01NDPCGG":3,"skill-same:01M79RS249WNA0BJTC01NDPCGG":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79RS249WNA0BJTC01NDPCGG","visual-fidelity-reviewer",null,"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.","sonanh08t4\u002Fmobile-ui-design-os","sonanh08t4","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10031096?v=4","01M79RQXCCPT1T97F1XZNBYDDP","Lã Phan Sơn Anh","01M79RQXDFWHMJ84WDAY5B3V34",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-fidelity-reviewer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: visual-fidelity-reviewer\ndescription: \"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.\"\n---\n\n# Visual Fidelity Reviewer\n\n## Purpose\n\nDetect product-inappropriate, generic, inconsistent, or under-resolved visual design before approval.\n\n## When to use\n\nUse when representative or full-prototype screenshots exist and before any design-freeze decision.\n\n## When not to use\n\nDo not review prose as if it were rendered evidence, generate a direction, or treat screenshot similarity as proof of quality.\n\n## Required inputs\n\n- Validated brief and chosen direction rationale.\n- Direction specifications and representative-screen comparison.\n- Available screenshots for key screens and states.\n- Accessibility findings.\n- [UI Constitution](..\u002F..\u002Fknowledge\u002FUI_CONSTITUTION.md), [Anti-Generic UI](..\u002F..\u002Fknowledge\u002FANTI_GENERIC_UI.md), and [Visual Quality Rubric](..\u002F..\u002Fbenchmark\u002Frubric.md).\n\n## Permitted evidence sources\n\n- Local screenshots, prototype behavior, frozen product requirements, approved direction artifacts, and existing QA reports.\n- Human visual judgment documented with evidence.\n\n## Expected outputs\n\n- [Visual review](..\u002F..\u002Ftemplates\u002Fvisual-review\u002Fvisual-review.md).\n- Category scores supported by evidence.\n- Generic-pattern violations and direction-drift findings.\n- P0\u002FP1\u002FP2 issues, structural remediation, and a revise\u002Fredesign\u002Fapproval recommendation.\n\n## Ordered workflow\n\n1. Confirm screenshot coverage and evidence provenance.\n2. Review product fit and workflow clarity before ornament.\n3. Review hierarchy, composition, typography, spacing, alignment, density, surfaces, geometry, icons, and motion evidence.\n4. Check chosen-direction integrity across screens and states.\n5. Run every applicable anti-generic pattern review.\n6. Evaluate realistic content, state completeness, and recovery clarity.\n7. Score only what the evidence supports and surface category weakness.\n8. Require structural remediation for structural failures.\n\n## Tools allowed\n\n- Local screenshot\u002Fimage inspection, prototype inspection, repository reading, and review-document editing.\n- Existing local comparison evidence when its method is known.\n\n## Tools forbidden\n\n- Network inspiration search, competitor copying, automatic aesthetic approval, hidden score adjustment, production UI changes, and claims based on missing screenshots.\n\n## File boundaries\n\nWrite only the approved visual-review artifact. Keep remediation edits in a separately authorized task.\n\n## Non-negotiable rules\n\n- Product fit outranks fashionable styling.\n- Severe anti-generic violations block approval.\n- Attractive but product-inappropriate screens fail.\n- Numeric score cannot replace human visual judgment.\n\n## Stop conditions\n\nStop when required screenshots\u002Fstates are absent, the chosen direction is not documented, or evidence cannot be attributed to the reviewed revision.\n\n## Failure conditions\n\n- The review ignores direction drift or generic composition.\n- Scores lack screenshot evidence.\n- Unresolved issues are hidden in prose or the total score.\n- The review approves screens that are attractive but wrong for the product.\n\n## Acceptance criteria\n\n- Findings are screen\u002Fstate-specific, evidence-backed, severity-classified, and actionable.\n- The decision is consistent with hard gates and score thresholds.\n- Human judgment points are explicit.\n\n## Handoff to the next skill\n\nReturn revise\u002Fredesign findings to `prototype-builder`; when freeze-eligible, hand the complete review to `design-system-freezer` and `visual-release-gate`.\n\n## Required human-review points\n\n- Product fit, actual direction distinctiveness, premium character, trade-dress risk, monetization ethics, copy tone, emotional fit, and final visual approval.\n\n","# Visual Fidelity Reviewer\n\n## Purpose\n\nDetect product-inappropriate, generic, inconsistent, or under-resolved visual design before approval.\n\n## When to use\n\nUse when representative or full-prototype screenshots exist and before any design-freeze decision.\n\n## When not to use\n\nDo not review prose as if it were rendered evidence, generate a direction, or treat screenshot similarity as proof of quality.\n\n## Required inputs\n\n- Validated brief and chosen direction rationale.\n- Direction specifications and representative-screen comparison.\n- Available screenshots for key screens and states.\n- Accessibility findings.\n- [UI Constitution](..\u002F..\u002Fknowledge\u002FUI_CONSTITUTION.md), [Anti-Generic UI](..\u002F..\u002Fknowledge\u002FANTI_GENERIC_UI.md), and [Visual Quality Rubric](..\u002F..\u002Fbenchmark\u002Frubric.md).\n\n## Permitted evidence sources\n\n- Local screenshots, prototype behavior, frozen product requirements, approved direction artifacts, and existing QA reports.\n- Human visual judgment documented with evidence.\n\n## Expected outputs\n\n- [Visual review](..\u002F..\u002Ftemplates\u002Fvisual-review\u002Fvisual-review.md).\n- Category scores supported by evidence.\n- Generic-pattern violations and direction-drift findings.\n- P0\u002FP1\u002FP2 issues, structural remediation, and a revise\u002Fredesign\u002Fapproval recommendation.\n\n## Ordered workflow\n\n1. Confirm screenshot coverage and evidence provenance.\n2. Review product fit and workflow clarity before ornament.\n3. Review hierarchy, composition, typography, spacing, alignment, density, surfaces, geometry, icons, and motion evidence.\n4. Check chosen-direction integrity across screens and states.\n5. Run every applicable anti-generic pattern review.\n6. Evaluate realistic content, state completeness, and recovery clarity.\n7. Score only what the evidence supports and surface category weakness.\n8. Require structural remediation for structural failures.\n\n## Tools allowed\n\n- Local screenshot\u002Fimage inspection, prototype inspection, repository reading, and review-document editing.\n- Existing local comparison evidence when its method is known.\n\n## Tools forbidden\n\n- Network inspiration search, competitor copying, automatic aesthetic approval, hidden score adjustment, production UI changes, and claims based on missing screenshots.\n\n## File boundaries\n\nWrite only the approved visual-review artifact. Keep remediation edits in a separately authorized task.\n\n## Non-negotiable rules\n\n- Product fit outranks fashionable styling.\n- Severe anti-generic violations block approval.\n- Attractive but product-inappropriate screens fail.\n- Numeric score cannot replace human visual judgment.\n\n## Stop conditions\n\nStop when required screenshots\u002Fstates are absent, the chosen direction is not documented, or evidence cannot be attributed to the reviewed revision.\n\n## Failure conditions\n\n- The review ignores direction drift or generic composition.\n- Scores lack screenshot evidence.\n- Unresolved issues are hidden in prose or the total score.\n- The review approves screens that are attractive but wrong for the product.\n\n## Acceptance criteria\n\n- Findings are screen\u002Fstate-specific, evidence-backed, severity-classified, and actionable.\n- The decision is consistent with hard gates and score thresholds.\n- Human judgment points are explicit.\n\n## Handoff to the next skill\n\nReturn revise\u002Fredesign findings to `prototype-builder`; when freeze-eligible, hand the complete review to `design-system-freezer` and `visual-release-gate`.\n\n## Required human-review points\n\n- Product fit, actual direction distinctiveness, premium character, trade-dress risk, monetization ethics, copy tone, emotional fit, and final visual approval.\n\n",{"name":5,"description":7},"main","d05fff827f6fb0baeb18be5127a043b7ade8045d","skills\u002Fvisual-fidelity-reviewer",0,"https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os","https:\u002F\u002Fgithub.com\u002Fsonanh08t4","Open-source maintainer and security researcher building reproducible developer tools for AI-assisted mobile product design.","2026-08-12 14:30:23",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add sonanh08t4\u002Fmobile-ui-design-os --skill visual-fidelity-reviewer",{"tool":38,"command":39},"bunx","bunx skills add sonanh08t4\u002Fmobile-ui-design-os --skill visual-fidelity-reviewer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sonanh08t4\u002Fmobile-ui-design-os --skill visual-fidelity-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-fidelity-reviewer\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79RSAR75H6JMDAFNVVV1KKY","valid-skill","Validate a small local skill fixture with one declared reference and one local schema.","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Ftests\u002Fpackage\u002Ffixtures\u002Fvalid-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79RS79E75KTC5A4BNPZV13P","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.","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-release-gate\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79RRYYJ75MJ8BVDSZJK98HJ","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.","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-direction-lab\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79RRTFGP0QPRE3WN1PWPDC3","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.","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fprototype-builder\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79RRP712C3YKV3NR4S2A7JF","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.","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-product-interpreter\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79RRGF7VY1P6BQ7WQXYA7FN","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.","https:\u002F\u002Fgithub.com\u002Fsonanh08t4\u002Fmobile-ui-design-os\u002Fblob\u002Fmain\u002Fskills\u002Fflutter-ui-handoff\u002FSKILL.md",[],[]]