agency-ui-finish-gate-reviewer

Reviews web and iOS interfaces against a design contract and returns a pass or hold finish gate.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-ui-finish-gate-reviewer-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-ui-finish-gate-reviewer
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/design-ui-finish-gate-reviewer
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-ui-finish-gate-reviewer-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implemented interfaces often ship looking generic and interchangeable because no one checked whether the UI actually fits the product's users, workflows, and constraints. This Skill catches that problem before release by grounding critique in product evidence and enforcing a hard pass/fail finish gate. ## Core Features & Use Cases - Design Contract Creation: Captures the product's user, job, first-read object, density decision, interaction model, responsive priorities, and forbidden generic defaults before any critique begins. - Evidence-Based Review: Audits implemented screens across product legibility, hierarchy, pattern fit, states, responsive behavior, and implementation fidelity at desktop and mobile sizes. - Hard Finish Gate: Returns a clear PASS or HOLD decision with observable findings, required changes, and verification conditions instead of vague aesthetic feedback. - Use Case: Before releasing an analytics dashboard, run the review to discover that four equal-weight metric cards bury the retention decision, then get a concrete required change verified at 1440px and 390px including loading and empty states. ## Quick Start Review this implemented screen before release and return a finish-gate decision with evidence and required changes.

Frequently Asked Questions about agency-ui-finish-gate-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a UI implementation before shipping?

Audit the implemented screens against a design contract covering product legibility, hierarchy, pattern fit, states, responsive behavior, and implementation fidelity. Return a PASS or HOLD decision where every finding maps to a visible screen state and a verification method.

What is a design contract in UI review?

A design contract is a written document capturing the user and job, first-read object, primary action, density decision, hierarchy, interaction model, responsive priorities, reference patterns, and forbidden generic defaults. It is written before proposing implementation changes so critique is grounded in product needs.

How do I tell if a UI looks generic or AI-generated?

Check whether the screen's choices are interchangeable with any other product: equal-weight card grids, decorative gradients, fake density, and generic empty states are common signals. A product-specific UI names its first-read object and primary workflow in the first viewport.

Does this review work for mobile and responsive layouts?

Yes, the finish gate requires review at both desktop and narrow mobile sizes. The responsive check verifies that the narrow layout preserves the user's job rather than merely stacking desktop cards, including touch targets, focus, and long-label behavior.

When should a UI review return HOLD instead of PASS?

Return HOLD when critical findings remain, such as the first-read object being buried, forbidden generic defaults without a product reason, or unverified states and viewports. A HOLD must list concrete required changes with specific verification conditions, not vague nice-to-haves.