frontend-design-anti-slop
Skill6 starsChanged 49 days agoMITView on GitHub
Design distinctive frontend interfaces that don't look AI-generated. Use when building web pages, landing pages, dashboards, or any UI — especially when you want to avoid the generic "AI slop" aesthetic that plagues LLM-generated designs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vekzz-dev/opencode-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vekzz-dev/opencode-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- campaign-reportSkill
- competitor-intelSkill
- content-auditSkill
- content-strategySkill
- croSkill
- customer-researchSkill
- lead-magnetsSkill
- linkedin-adsSkill
- marketing-councilSkill
- marketing-monthlySkill
- pipeline-analysisSkill
- product-launchSkill
- internal-linkingSkill
- seo-reportSkill
- beautify-github-readmeSkill
- cinemagraphSkill
- copy-deslopSkill
- copy-longformSkill
- writing-assistantSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
This is an interactive process: Ask the user what they're building before designing anything.
- Distinctive: line 25
Wait for answers before proceeding.
- Distinctive: line 41
Rounded-lg maximum: No rounded-xl, no rounded-2xl, no pill shapes on cards.
- Distinctive: line 62
When the user doesn't have existing brand colors:
- Distinctive: line 92
Typography scale: Don't use more than 4 font sizes on a page.
- Distinctive: line 106
If the user asks you to review or improve an existing page:
- Distinctive: line 108
Check it against the anti-patterns list first
- Distinctive: line 111
Don't redesign everything — targeted improvements beat rewrites
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend Design — Anti-Slop Edition
Build frontend interfaces with genuine design taste. This skill exists because most AI-generated UIs look identical: purple-to-blue gradients, bento grids, rounded-xl everything, "Transform your X" hero text. This skill does the opposite.
This is an interactive process. Ask the user what they're building before designing anything.
Intake
Start by asking:
What are you building? (Landing page, dashboard, app UI, marketing page, etc.) Who is it for? What's the vibe — professional, playful, warm, minimal, bold? Any existing brand elements (colors, fonts, logo) I should work with?
Wait for answers before proceeding.
Design Principles
Apply these in every decision:
- Warm over corporate. Dark backgrounds should feel like a room at night, not a SaaS dashboard. Use brown-blacks (#12110f) over pure blacks (#000). Warm grays over cool grays.
- Monospace for character, display for hierarchy. Use monospace fonts (JetBrains Mono, IBM Plex Mono, Fira Code) for UI chrome — labels, badges, buttons, metadata. Use a display or heading font (Space Grotesk, Inter Tight, Satoshi) for titles and emphasis. Never use monospace for everything. Never use a generic sans-serif for everything either.
- One accent color, used sparingly. Pick one strong accent (mint green, amber, coral) and use it only for primary actions and active states. Everything else lives in the neutral palette. Two accent colors maximum. If you reach for a third, you've lost the thread.
- Borders > shadows. Subtle 1px borders (#33302a on dark, #e5e5e5 on light) create structure without the floaty feeling of box-shadows. Reserve shadows for elevated elements (modals, dropdowns, toasts).
- Content density over whitespace theater. Let content breathe with natural spacing (4/8/12/16px increments), not massive gaps that make users scroll past nothing. Information-rich is not the same as cluttered.
- Rounded-lg maximum. No rounded-xl, no rounded-2xl, no pill shapes on cards. Subtle rounding (8px) feels intentional. Excessive rounding feels like a template.
Anti-Patterns — Never Do These
These are the hallmarks of AI-generated design slop. Avoid every single one:
| Pattern | Why it's bad | What to do instead |
| Purple-to-blue gradients | Every AI UI has them. Instant "this was generated" signal. | Solid colors. If you need a gradient, use warm tones or monochrome. |
rounded-xl or rounded-2xl on cards | Looks like every Tailwind template. | rounded-lg (8px) maximum. rounded (4px) for small elements. |
| Centered hero with gradient text saying "Transform your X" | The #1 AI slop pattern. | Start with the product, not a tagline. Show, don't tell. |
| Bento grids with rounded corners on everything | Looks like Apple keynote cosplay without the product to back it up. | Standard grid layouts. Asymmetry is fine. Not everything needs equal weight. |
| Excessive whitespace | Mistaken for "clean design." Actually just empty. | Content-first. Space serves the content, not the other way around. |
animate-pulse skeleton loaders | Draws attention to loading, makes the page feel broken. | Subtle opacity fade or no animation. Skeleton should be invisible, not a feature. |
| Emojis as icons | Looks like a Discord bot. | Use an icon library (Lucide, Heroicons, Phosphor). Consistent weight and style. |
system-ui, Inter, Roboto, Arial everywhere | Default fonts signal "I didn't make a design decision." | Choose fonts with intention. Even Google Fonts has distinctive options. |
| Colored top-bar stripes on cards | Early Trello/Asana pattern, now a cliché. | Border colors, subtle background tints, or icon-based categorization. |
| Floating/bobbing hover animations | Distracting, gimmicky, adds no information. | Subtle border/shadow transitions (200-300ms). Hover should clarify, not entertain. |
Color Palette Guidance
When the user doesn't have existing brand colors:
Dark themes:
Background: #12110f (warm dark brown, not pure black)
Surface: #1e1c18 (cards, panels)
Border: #33302a (subtle divider)
Text: #e8e4dc (off-white, not pure white)
Muted: #8a8578 (secondary text)
Accent: Pick ONE from: #4ade80 (mint), #f59e0b (amber), #f87171 (coral), #60a5fa (sky)Light themes:
Background: #faf9f7 (warm off-white)
Surface: #ffffff
Border: #e8e4dc
Text: #1e1c18
Muted: #8a8578
Accent: Same options, slightly deeper for contrastComponent Patterns
Cards: rounded-lg, 1px border, bg-surface, hover changes border color or adds subtle glow. No drop shadows. No float animation.
Buttons: Outlined style for secondary (border + text color). Filled style for primary (accent bg + dark text). No gradient fills. No rounded-full unless it's an icon button.
Forms: bg-surface, border-border, focus:border-accent. No ring utilities. Clean, no decoration.
Typography scale: Don't use more than 4 font sizes on a page. Heading (xl-2xl), subheading (lg), body (sm-base), caption (xs). Enforce hierarchy through weight and font family, not just size.
Process
- Confirm the build target and vibe with the user
- Choose a color palette (or use their existing one)
- Choose fonts (heading + body/mono, Google Fonts is fine)
- Build the layout structure first (HTML skeleton with Tailwind)
- Apply the design system: colors, typography, spacing
- Review against the anti-patterns list — fix any violations
- Show the user and iterate
When Reviewing Existing UI
If the user asks you to review or improve an existing page:
- Check it against the anti-patterns list first
- Identify the top 3 offenders
- Propose specific fixes with before/after reasoning
- Don't redesign everything — targeted improvements beat rewrites
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

