nextlevelbuilder / nextlevelbuilder/ui-ux-pro-max-skill

Built an AI slop detector using your anti-pattern database

Open
#219 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agent:github-maintain maintain:accepted maintain:triaged
Dominant language
Python
Stars
129k
Forks
13.7k
Avg merge
23h 27m
Merged PRs (30d)
23

Description

Hey — built vibecheck-slop-stopper, a tool that detects AI-generated code in PRs (GitHub Action + CLI + Claude Code skill).

Your ui-reasoning.csv anti-pattern data was one of the sources for our visual slop detection patterns (P11) — specifically the AI purple/pink gradient flagging across product categories and the product-type-specific anti-pattern severity ratings.

We also pulled from gstack's design-checklist to build a 10-item AI visual slop blacklist that maps to grep-able CSS/Tailwind patterns:

  • Purple/violet/indigo gradient detection (#6366f1–#8b5cf6 range)
  • Centered text density (>60% = flag)
  • Uniform bubbly border-radius
  • Generic hero copy ("Unlock the power of...")
  • Glassmorphism blur, default AI box-shadow
  • Emoji as design elements

These compile from human-readable TOML stanzas to ripgrep regex at scan time, so the detection is automated.

You're credited in our README. MIT licensed, 72 rules across 11 categories.

Just wanted to share since your data made the visual slop detection possible. Happy to answer any questions about how we used it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue only shares the external vibecheck-slop-stopper project and explains how it used ui-reasoning.csv and gstack's design-checklist. Review the linked repository and this project's referenced data to determine whether any documentation or attribution change is requested; no files, tests, entry points, or definition of done are provided.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, tailwindcss
Domain
tooling
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.