design-review
SolidThe final quality gate before any design deliverable is reported done — two ISOLATED assessments (deterministic detection never in the same head as the subjective/visual read), P0-P3 findings with NO aggregate score ever, a bounded visual loop (max 2 fix cycles), and a mandatory in-loop challenger gate (fresh-context, blind PNG) before any 'done' claim.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- fusengine
- Repository
- fusengine/agents
- Created
- 6 months ago
- Last Updated
- yesterday
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
design-review-gate
Turns design review into observable checks. Load when you are judging a built UI surface ("does this look right/professional?", a visual QA request, before/after comparison of styling work), when generated design variants need comparison, or when any design document is about to be adopted, authored, or treated as authoritative - a DESIGN.md, tokens file, brand guide, or a reverse-engineered competitor analysis. NOT for producing the surface (ui-design-craft, motion-craft), for evidence rules on non-design deliverables (domain-evidence-discipline), or for code-correctness review (the code-review tooling).
review-design
Internal UI/UX design review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed UI against the project's design doc: consistency, states, responsiveness, and reuse — applies only when the project has a UI and the change touches it. Findings only; never edits code.
unikit-gd-review
Qualitative quality review of game design documents — answers "is this design good, and does it follow best practices?" — across all three GDD axes: systems, flows, and content types. Fans out adversarial lenses (completeness, clarity, pillar alignment, systems-math, fantasy-delivery, feasibility, scope) plus domain lenses that check it against the game-design rules, each prompted to find problems rather than validate; produces a severity-graded verdict and a two-bucket report (apply-ready fixes vs research), handed to /unikit-gd-apply or /unikit-gd-explore in one move. Scope is inferred: a named system, flow, or content type reviews that document; "all" runs a cross-document review. Use when the user wants a critique, quality judgment, or rules check of the design, e.g. "review the combat GDD", "review the onboarding flow". This is the subjective quality pass — for a mechanical consistency check (numbers, terms, IDs, references matching the registry) use /unikit-gd-verify.