#Human reading layer
#The idea in plain language
An interface should explain itself through structure before it asks copy to explain the structure. Its visual choices should come from the product, the brand, the task, or a known usability requirement. Decorative choices should have a deliberate aesthetic purpose. Repeated patterns should form a coherent system.
When a generated interface feels generic, the problem is often visible in the gaps between these decisions. The page has cards because cards are common. The hero has a gradient because gradients look modern. The icon sits in a rounded square because component libraries do that. The description repeats the heading because empty space felt unfinished. Every section animates upward because the motion library made it easy. None of those choices is inherently wrong. Their accumulation without a product-specific reason creates sameness.
The same problem appears in writing. A heading already communicates the purpose of a section, then a paragraph restates the heading. A button already says Invite member, then nearby copy explains that the button lets you invite a member. A simple product fact gets wrapped in promotional language. A short explanation turns into several paragraphs because the writer is trying to sound complete. The useful goal is helping the reader act.
The Intentionality Law asks one question repeatedly:
Why is this here?
A strong answer can be functional, semantic, aesthetic, editorial, brand-specific, or accessibility-related. The answer simply needs to be real.
#Why this law exists
Modern coding agents can produce competent UI quickly. They have also learned the same large body of public design systems, component libraries, landing pages, templates, tutorials, and product screenshots. When a prompt leaves visual decisions open, the model tends to select highly probable patterns.
That behavior creates convergence. Different products end up with similar colors, similar cards, similar hero structures, similar motion, similar typography, and similar copy rhythm.
A 2026 open-source analysis of Reddit discussion about vibe-coded sites scanned 3,214,533 posts across 47 subreddits, then analyzed 46,971 on-topic posts and 3,033 comments from 125 threads focused on recognizable AI-built websites. The largest umbrella complaint was sameness. The most frequently named concrete signals included untouched shadcn/Tailwind styling, purple or violet as the default primary color, gradients, excessive animation, broad corner rounding, neon glow on dark interfaces, emoji used as icons, generic typography, and the centered hero followed by three feature cards and a CTA. The authors describe the dataset as community evidence with clear limits. Layr uses it as one input and keeps style prohibitions out of the rule.
The same dataset also exposes an important failure mode in anti-slop advice. Once people began avoiding the older purple-gradient aesthetic, another recognizable default appeared: warm cream backgrounds, editorial serif headings, and sage or forest-green accents. A design can therefore become generic while trying very hard to look tasteful.
This matters because a static blacklist becomes obsolete. Layr needs a rule that survives trend changes, and the rule that survives is intentionality: a list of banned styles expires with the trend that produced it, while the question of whether a choice was made stays answerable in any aesthetic.
#A stronger definition of AI slop
For Layr, AI slop means:
An accumulation of unchosen defaults, generic visual recipes, redundant language, or decorative behavior that weakens product specificity, information value, or interaction clarity.
This definition evaluates the artifact itself.
Layr should never claim that a page was generated by AI because it contains a gradient, uses shadcn, or resembles a common landing page. Humans use those patterns too. AI-assisted products can also be designed with extreme care.
The review target is the slop characteristic, not provenance.
A valid Layr finding should sound like this:
This surface combines an untouched card variant, a default violet primary, repeated icon-in-square feature cards, and generic explanatory copy. The cluster is visually interchangeable with unrelated SaaS templates and does not reflect the project's documented design system.
It should avoid claims like:
This was clearly made by AI.
#The four layers of slop
Layr should treat AI slop as several related failure modes that can appear across many aesthetics.
#1. Default slop
A default is shipped as if it were a design decision.
Typical examples include:
- an untouched component-library theme;
- the default neutral ramp from a starter kit;
- default radius values used everywhere;
- the first common font suggested by the framework;
- a common violet or indigo primary chosen because no brand color was supplied;
- a stock hero layout produced by a template;
- standard animation wrappers added to every section;
- generic placeholder illustrations promoted into final production UI.
The problem is the absence of a project-specific choice.
#2. Pseudo-slop
The interface tries to escape one recognizable default and lands on another recognizable default.
Examples include:
- replacing purple gradients with cream, serif typography, and sage green because that combination currently reads as tasteful;
- replacing Inter with the current fashionable editorial serif without considering the product voice;
- removing rounded cards everywhere and forcing sharp brutalist geometry because anti-AI discourse currently favors it;
- converting a generic SaaS page into a generic editorial page while preserving the same underlying structure and content.
Pseudo-slop is especially useful for Layr to detect because anti-slop rules can create it accidentally.
#3. Content slop
The interface contains words that do not earn the space or attention they consume.
Common forms include:
- headings restated in the first sentence;
- helper text that repeats a label;
- identity or page-type labels that repeat a nearby logo, title, or navigation cue;
- descriptions that explain an obvious control;
- generic marketing claims with no product-specific information;
- filler sections added to make a page feel substantial;
- AI-style staging before a simple point;
- formulaic conclusions that repeat what the section already said;
- overuse of bold labels, decorative headings, or prose patterns that make every section sound generated from the same template.
#4. Interaction slop
The visual surface looks complete while behavior, states, and edge cases remain generic or unfinished.
Examples include:
- buttons that exist because the template expects a button but lead nowhere;
- repeated confirmations for harmless actions;
- missing loading, empty, error, or partial-success states;
- motion attached to every element without conveying state;
- decorative status colors that have no consistent semantic mapping;
- fake progress indicators that are disconnected from real system progress;
- a polished happy path paired with raw or inconsistent failure states.
Interaction slop matters because a visually convincing first draft can hide an incomplete product model.
#The intentionality tests
Layr can apply these tests to any visual, textual, or interactive decision.
#Purpose test
Ask what job the element performs.
Valid jobs include:
- communicating information;
- establishing hierarchy;
- grouping related content;
- exposing state;
- providing an affordance;
- giving feedback;
- supporting navigation;
- improving accessibility;
- expressing a deliberate brand identity;
- creating a specific emotional quality that supports the product experience.
If the agent cannot identify a job, the element becomes a candidate for removal or redesign.
#Product-specificity test
Ask whether the same element could appear unchanged in dozens of unrelated products.
Generic reuse is expected for ordinary controls. A checkbox should remain recognizable. Product specificity becomes important when the element claims to carry brand, hierarchy, editorial voice, or marketing meaning.
A login input can look conventional. A product-defining hero, pricing page, onboarding experience, or empty state should carry more product-specific decisions.
#Subtraction test
Temporarily remove the element.
Then ask whether the interface loses:
- meaning;
- interaction capability;
- hierarchy;
- necessary context;
- accessibility information;
- feedback;
- brand identity;
- useful emotional tone.
If none of those changes, the element needs a stronger reason to remain.
The subtraction test is especially effective for decorative badges, filler descriptions, extra card containers, decorative icons, repeated separators, excessive motion, and generic metadata.
#Semantic test
If a visual treatment looks meaningful, verify that it represents something real.
A colored left edge may imply category, state, severity, selection, or ownership. If it represents none of those, it may be decorative convention masquerading as information.
A monospace version label may imply a real document version. If Foundation / 0.1 never changes, is not navigable, and tells the reader nothing useful, the treatment is functioning as aesthetic metadata.
#Replacement test
A correction fails when it swaps one unspecified default for another.
Examples:
- violet to emerald with no brand rationale;
- Inter to Instrument Serif because serif currently feels more premium;
- glass cards to sharp bordered cards because brutalism is trending;
rounded-xltorounded-noneacross the entire application without examining component semantics;- generic marketing copy rewritten into generic minimalist copy.
A correction should connect to the product's real design system, brand, content, or task.
#Explanation test
Compare the copy with what the interface already communicates.
Copy earns its place when it adds information about:
- consequence;
- risk;
- constraints;
- unfamiliar behavior;
- required input;
- uncertainty;
- recovery;
- differentiation;
- policy;
- context the interface cannot communicate safely through structure alone.
Copy that simply names what a nearby label, button, table, or visual structure already makes clear should be shortened or removed.