gmira-slop

Audit web interfaces for generic design patterns and AI-generated visual tells.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/OthmanAdi/gmira --skill gmira-slop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmira-slop
Source: https://github.com/OthmanAdi/gmira/tree/main/skills/gmira-slop
Command: npx skills add https://github.com/OthmanAdi/gmira --skill gmira-slop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill identifies the subtle, repetitive patterns that make web pages look generic, templated, or obviously AI-generated, helping you move beyond surface-level aesthetics to intentional design.

Core Features & Use Cases

  • Visual Audit: Detects uniform section rhythms, three-column reflexes, and decorative chrome that lacks data.
  • Specificity Testing: Provides a framework to test if your page sections are truly unique or just stock patterns.
  • Use Case: Use this before finalizing a landing page to ensure your design choices are deliberate and specific to your product rather than a byproduct of a component library's default settings.

Quick Start

Run the gmira-slop audit on the current page to identify generic design patterns and receive a specificity score.

Frequently Asked Questions about gmira-slop

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

FAQPage Schema
How do I audit my web design for AI-generated visual tells?

To audit web design for AI-generated visual tells, the skill analyzes browser-based DOM access and screenshots to measure visual rhythm, aspect ratios, and component uniformity, identifying generic patterns like uniform section rhythms and decorative chrome.

What makes a web page look generic or templated?

A web page looks generic or templated due to subtle repetitive patterns like uniform section rhythms, three-column reflexes, and decorative chrome lacking data, which are common byproducts of component library default settings rather than intentional product choices.

Can I test if my front-end layout sections are truly unique?

Yes, you can test layout specificity using a framework that checks if front-end sections are truly unique or just stock patterns, ensuring design choices are deliberate and specific to your product instead of relying on generic component defaults.

Does detecting generic design patterns require browser access?

Yes, detecting generic design patterns requires browser-based DOM access and screenshot capabilities to accurately measure visual rhythm, aspect ratios, and component uniformity across the web interface during the front-end review workflow.

When should I run an audit for AI-generated design tells?

You should run an audit for AI-generated design tells before finalizing a landing page, ensuring your design choices are deliberate and specific to your product rather than accidentally retaining generic patterns from component library defaults.