premium-ui

Design and audit web and mobile interfaces to remove AI-generated visual patterns.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/usmangurowa/sifter --skill premium-ui-usmangurowa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: premium-ui
Source: https://github.com/usmangurowa/sifter/tree/main/.agents/skills/premium-ui
Command: npx skills add https://github.com/usmangurowa/sifter --skill premium-ui-usmangurowa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces built quickly with AI assistance often accumulate generic visual patterns—gradient heroes, glassmorphism, nested cards, decorative badges—that make products feel template-generated rather than authored. This Skill provides a structured workflow and audit checklist to design, implement, and review interfaces that feel intentional and product-specific. ## Core Features & Use Cases - Slop Pattern Detection: Identifies common AI-generated design tells such as purple gradients, glow effects, fake dashboard mockups, and decorative eyebrow badges. - Implementation Rules: Enforces use of existing design system tokens, repo icon libraries (HugeIcons, @turbo/ui), accessible primitives, readable contrast, and stable responsive layouts. - Audit Checklist: Validates purpose, cohesion, specificity, density, contrast, mobile behavior, motion, and accessibility before finalizing UI changes. - Use Case: When polishing a landing page or dashboard in a Next.js/Expo monorepo, run this Skill to strip generic styling, apply the existing design system, and verify light/dark mode readability and mobile ergonomics. ## Quick Start Use the premium-ui skill to review this screen and remove any AI slop patterns while keeping the existing design system.

Frequently Asked Questions about premium-ui

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

FAQPage Schema
How do I make an AI-generated UI look less generic?

Audit the interface against common slop patterns like gradient heroes, glassmorphism, nested cards, and decorative badges, then replace them with one signature product-specific element, a cohesive neutral palette, and real content. Verify readability and layout stability in both themes and on mobile.

What are common AI slop design patterns to avoid?

Common tells include purple-blue gradients, glowy pill buttons, blurred orbs, cards inside cards, eyebrow badges above every hero, fake macOS window mockups, bouncy animations, and low-contrast gray text. These patterns signal template-generated design rather than authored product UI.

Does this work with Tailwind CSS and shadcn/ui components?

Yes, the workflow prefers existing design system primitives like shadcn/ui components and Tailwind tokens over hand-rolled controls. Art-direction happens through classes and variants while preserving accessible component behavior.

How do I audit a UI for accessibility and mobile issues?

Check text contrast independently in light and dark modes, ensure touch targets meet comfortable mobile sizes, verify no horizontal overflow or clipped labels, confirm heading levels do not skip, and validate that focus states are visible and controls have labels.

When should I not add animations to an interface?

Avoid animation when it gates content visibility, causes layout jank, or uses bouncy/elastic easing. Content must render visible without animation completing, and motion should only support state transitions or purposeful microinteractions.