I found 3 interesting GitHub repos for Claude / Claude Code that might be useful if you’re building websites, UI, or frontend projects with AI. The idea is pretty simple: Instead of just telling Claude “make this better”, you give it a proper skill — basically a small set of rules, taste, and guidance for how to think about layout, spacing, typography, animations, and UI polish. Here are the 3 repos: 1. Impeccable https://github.com/pbakaus/impeccable This one feels like the most complete of the three. It helps Claude review and improve frontend work — things like layout, typography, spacing, colors, responsive issues, UX details, and overall polish. I think this is especially useful when you already have a page or component built, but it still feels a bit unfinished or “AI-generated”. 2. Taste Skill https://github.com/leonxlnx/taste-skill This one is more about helping AI stop making generic SaaS-looking designs. It pushes Claude toward better visual taste: better composition, better spacing, better motion, better style, and stronger design direction. I like this one because it’s not just technical. It tries to help the AI make better design decisions. 3. Emil Kowalski Skill https://github.com/emilkowalski/skill This one is more focused on design engineering and the small UI details that make a product feel polished. Think animations, micro-interactions, transitions, smooth UI behavior, and that “premium” feeling. In my opinion, this is best when the design is already decent, but you want to make it feel more refined. My takeaway: I wouldn’t install everything at once. I’d start with Taste Skill or Impeccable, test it on a real project, and only keep what actually improves your workflow. AI coding tools get much better when we don’t just give them prompts, but also give them structure, examples, and clear design rules.

Greettings everyone. Pepe here from Santiago, Chile. I've followed the basics of folder structure and it really makes sense. But i've got some issues. How the system records what i do? Could i do something in order to get memory? I've watched some advanced videos about making an OS System and i get that that woould be overkill on my current state: i'm just becoming an AI Freelancer that wants to make it. In order to do that, i would like to have a content lab and maybe some way in with the whole system records my actions. My first impression is that every folder should record his own, like in order to make content, the draft folder maybe resolves this issue. Is a memory layer to get what we do everyday overkill? Does anyone uses something like this? How can this be done respecting the folder structure? If you have an idea how to make this. I'd really apreciate some advice. Thanks a lot!

Still, I'm new here. So hopefully in a month or so I will get to 10% Anyone else feeling the same?

🎉 Meet your new admin: @David Vogel Some of you have been watching this happen in real time. David has been quietly turning his "Show Your Work" posts into one of the most useful threads in this community for months. Resource roundups, deep-dives, honest takes on what's actually working in production. No fluff. No hype. 🛠️ So I gave him the keys. 🔑 David is now an admin of Clief Notes, and he has his own classroom: 🏛️ David's Corner. Go check it out. AI Acronym Overload? Here's the Cheat Sheet - Davids Corner 📂 What's in David's Corner He started with the resource post a lot of you bookmarked last week and has been steadily expanding it. As of right now you'll find: 🔥 Must Have Resources - 🎨 Looking for design inspiration? - 🧠 AI Acronym Overload? Here's the Cheat Sheet - ⭐ Some of My Favorite Resources 📚 Learning for Everyone - 🥊 Obsidian is BLOAT! Batter Up - 💰 Flip the Script — It's all about the $$$ - 👻 Do You Have a Soul? - 🔄 My AI Workflow Evolution 👨‍💻 Developer Resources - 🕵️ LEAKED: Ten Prompts from Experts - ⚡ Introducing the Hermes Stack 🎯 David and Jakes Picks (this one's going to grow) Plus he's curating trusted YouTube channels and a running list of favorite community posts on resources inside the corner. So if you wrote something good about a tool, a stack, or a workflow, that's where it might end up. 👀 He's adding more weekly. If something stops delivering, he wants to hear about it. That's how the corner stays sharp. 🔪 💡 Why this matters The Vault and The Drawing Room give you my methodology. David's Corner gives you a second lens. Same standards (battle-tested, no theory, no marketing slides), different angle. He's been in the trenches with tools and stacks, and he writes about them honestly. ✅ What you can do 1. 🔖 Go bookmark David's Corner in the classroom 2. 💬 Drop a comment under his posts when something works (or doesn't) 3. 📨 Got a resource that should be in there? Tag him. He's curating.

Hey everyone, I’m currently building out the infrastructure for my bookkeeping firm, and I’ve hit specific roadblock where I’d love to hear how you handle things: The "Perfectionist" Loop (Idea Paralysis) I’m struggling to find the line between "planning for success" and "just getting started." I find myself endlessly refining workflows and systems before I actually pull the trigger on using them. • How do you decide when a system is "good enough" to launch? • What’s your approach to transitioning from building to operating?