I got tired of seeing it, so I built a fix. Ask Claude Code, Cursor, Codex, Gemini, whatever, to “build me a landing page.” You already know what comes back. Purple gradient. Inter. Centered hero. Three cards. Pill buttons. Maybe some glassmorphism if it is feeling fancy. That is not really the model being stupid. It is the model doing exactly what you asked it to do with no taste constraints. If you leave every design decision blank, the model fills those blanks with the average of the web. And the average of the web looks like slop. The thing I kept noticing is that there is not just one kind of AI slop. There are three: 1. The look Purple gradients, beige editorial templates, generic SaaS polish. 2. The structure Centered hero, three-card grid, equal sections, nothing with a real layout opinion. 3. The copy “Delve,” “in today’s fast-paced world,” “not just X, but Y.” You do not fix that by asking the model to “make it better.” That just gets you cleaner slop. You fix it by removing the blanks before the model starts guessing. So I built tastecheck. It is a free MIT skill pack for AI coding agents. The main skill does not just clean up bad UI after the fact. It interviews you before the build starts. It asks opinionated questions like: - What site would you actually be okay resembling? - Are we going warm or cool? - What is the one dominant color? - What should this feel like to use? - What are we absolutely not doing? Then it turns those answers into a real design direction: type, color, tokens, layout rules, interaction states, accessibility checks, and the rest of the system the agent should follow. The pack has 14 skills total: - typography - color - layout - responsive behavior - component states - forms - dark mode - motion - empty states - data visualization - accessibility - cognitive accessibility - design review - and the main taste interview The test I care about most: I took the same content and ran it through five different design systems.

Most people think they have an AI problem. What they actually have is a packaging problem. You don’t need to become a developer to use AI effectively. This guide breaks down the real “code” behind better results: prompts, skills, connectors, MCPs, hooks, scripts, and plugins — and shows you exactly when (and why) to use each one. Check it out in Davids Corner: https://www.skool.com/cliefnotes/classroom/c7f102c7?md=9a0d198e1c0140578f37f1c93873c2b6

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.