agency-reality-checker

Validates web implementations against specifications using Playwright screenshots and evidence-based quality assessment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents premature production approvals by requiring concrete visual and performance evidence before certifying a web implementation as ready, replacing inflated ratings with honest quality assessments. ## Core Features & Use Cases - Evidence-Based Validation: Runs reality-check commands and Playwright screenshot capture across desktop, tablet, and mobile viewports to verify what was actually built. - QA Cross-Validation: Compares prior QA findings against automated test-results.json data and before/after interaction screenshots to confirm or challenge assessments. - Specification Compliance Checks: Quotes original spec requirements and contrasts them with screenshot evidence to produce PASS/FAIL gap analyses. - Use Case: After a developer claims a landing page is "production ready", run this Skill to capture responsive screenshots, test navigation and form interactions, and receive a realistic C+/B- style rating with a list of required fixes. ## Quick Start Ask the agent to perform a reality-check integration assessment of the current web build and produce an evidence-based production readiness report.

Frequently Asked Questions about agency-reality-checker

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

FAQPage Schema
How do I verify a website is actually production ready?

Run reality-check commands to inspect built files, capture Playwright screenshots across desktop, tablet, and mobile viewports, and review test-results.json for load times and errors. Certify readiness only when visual and performance evidence supports it.

How to test responsive design with Playwright screenshots?

Use the qa-playwright-capture.sh script against the local server to generate responsive-desktop.png, responsive-tablet.png, and responsive-mobile.png. Compare these captures to detect layout breakage and cross-device inconsistencies.

What evidence is needed before approving a web deployment?

Approval requires full-page screenshots on multiple devices, before/after interaction captures for navigation and forms, performance metrics from test-results.json, and a specification compliance check mapping each requirement to visual proof.

Why do QA assessments often overrate website quality?

Assessments inflate ratings when they rely on claims instead of evidence, such as labeling basic dark themes as luxury designs. Defaulting to NEEDS WORK and demanding screenshot proof counters this pattern.

Can this validate Laravel Blade templates and static HTML?

Yes, the reality-check step inspects either resources/views/ for Laravel Blade templates or root-level HTML files for simple stacks, then greps for claimed premium features across HTML, CSS, and Blade files.