ui-design-specialist

Critique UI designs to identify and counter AI slop patterns.

3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/gwpjp/Web3-Claude --skill ui-design-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-design-specialist
Source: https://github.com/gwpjp/Web3-Claude/tree/main/.claude/skills/ui-design-specialist
Command: npx skills add https://github.com/gwpjp/Web3-Claude --skill ui-design-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a design critic to identify and prevent AI slop in frontend work, ensuring UIs are distinctive and engaging rather than bland and homogeneous.

Core Features & Use Cases

  • Structured critique that identifies convergence toward timid colors, uniform spacing, and predictable layouts.
  • Creative alternatives that propose palette, typography, and layout adjustments aligned with the project's theme.
  • Audit use cases across dashboards, forms, and components to raise visual identity without writing code.

Quick Start

Read the anti-slop-patterns catalog at .claude/skills/ui-design-specialist/anti-slop-patterns.md and the theme and component references in .claude/docs. When reviewing a UI task, return a structured critique following the six anti-slop dimensions and provide concrete alternatives.

Frequently Asked Questions about ui-design-specialist

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

FAQPage Schema
How do I run a design critique to identify AI slop in my UI?

Run a UI design critique using a structured process to identify AI slop by evaluating visual hierarchy across six anti-slop dimensions, pinpointing timid colors, uniform spacing, and predictable layouts in your frontend components.

What is AI slop in frontend design and how does it affect interfaces?

AI slop in frontend design is the convergence toward bland, homogeneous interfaces with timid colors and predictable layouts, which undermines visual identity and results in a uniform lack of distinctiveness across dashboards and forms.

How do I audit component libraries for visual hierarchy and distinctive design?

Audit component libraries by applying an anti-slop pattern catalog to evaluate visual hierarchy, identifying convergence toward uniform spacing and timid colors, then proposing palette, typography, and layout alternatives aligned with your project theme.

Does the design critique generate frontend code for my dashboard components?

No, the design critique does not generate frontend code for dashboards or forms, but instead returns actionable recommendations and concrete creative alternatives to improve visual identity and counter bland UI patterns.

Can I use this design audit for forms and component libraries?

Yes, you can use this design audit for forms, dashboards, and component libraries to evaluate visual hierarchy, identify anti-slop patterns, and propose theme-consistent palette, typography, and layout adjustments for distinctive interfaces.

What's the best way to fix predictable layouts and timid colors in UI design?

The best way to fix predictable layouts and timid colors is to apply a structured design critique that proposes creative alternatives for palette, typography, and layout adjustments aligned with your project theme to ensure engaging interfaces.