Scoville Ui Anti Ai Slop

Scoville UI Anti-AI-Slop

A polished interface can still lose the user's task. Scoville UI keeps that task visible while the pixels negotiate among themselves.

It usually looks harmless:

• A product with an established design system receives a fresh local language of rounded cards, gradients, and pills because this screen wanted a journey.
• Primary, secondary, and destructive actions all receive equal emphasis. The hierarchy is now democratic and therefore useless.
• The happy path looks polished. Loading, empty, error, focus, keyboard, and long-content states have quietly missed the launch.
• The desktop screenshot is excellent. On mobile, the primary action lives beyond a horizontal scroll that users can discover through archaeology.

That is UI slop: familiar polish substitutes for the task, the product's visual owner, and rendered evidence. The gradient survived. The task did not.

Scoville UI is a framework-aware Agent Skill for implementing and auditing interfaces through the product framework and incumbent design system. It owns supported components, states, semantics, focus and input behavior, announcements, responsive mechanics, and rendered evidence. When Scoville Design is active and applicable, UI consumes its design decisions without re-deciding them. Otherwise UI retains a bounded standalone Greenfield fallback. It does not activate for backend-only work or wording alone.

Why "Scoville"?

The family is named for useful signal that remains detectable after dilution. In UI work, the heat is the user's task - primary action, state, reading order, and error recovery - not making every button look ready for a chili-eating contest.

How to use

Name Scoville UI for interface design, implementation, or audit work:

Use Scoville UI to implement this settled settings-screen design through the product's existing component system. Cover loading, empty, error, and success states, then verify the rendered result responsively.