@Daniel Petro shared this with me the other day and I find it to be one of the most useful tools I have come across in a while for AI powered development: https://agentation.dev/ The core idea: instead of describing a bug or design issue to your AI agent ("the blue button in the top right looks off"), you literally point at it — and the tool gives your agent the exact information to find it directly in your codebase. Overview of how it works: 1. Click any element → write your note → done 2. Select text → annotate a typo or copy issue 3. Drag a box → annotate an entire area at once 4. Hit copy → paste structured markdown directly into Claude Code, Cursor, or any AI tool The output is structured: element path, React component hierarchy, classes, position, computed CSS, so your agent can search for it with accuracy. You can also connect it to an MCP server they built, so your agent sees annotations in real time. No copy-paste at all. Just annotate in the browser and your Claude Code session already has full context. There's also a "watch mode" where the agent loops continuously, picking up new annotations as you create them and resolving them after fixing. You annotate, it fixes, in real time. If you're building with Claude Code or Cursor and doing any kind of UI work, this fits right into that workflow. Worth 10 minutes to try. Thanks @Daniel Petro for the recommendation! 🙌

I used to restart Claude sessions all the time because I'd hit context limits or need to switch tasks. Every restart meant re-explaining my setup, tech stack, and what I was building. Then I started treating MCP servers like my 'external brain'. Instead of cramming everything into chat context, I built a simple MCP that reads my project docs, database schemas, and recent decisions from files. Now Claude just asks the MCP when it needs context. Now I can work on the same project across 10+ sessions without losing continuity. Claude remembers everything because the MCP remembers everything. Anyone else structuring their MCP servers this way? Would love to hear other patterns people are using.

Been building lots of internal tools and decided to build a React template derived from a production project. React is a ecosystem that requires a lot of picking an choosing to land on the right tools. This template skips the decision fatigue by combining battle-tested libraries with patterns proven in production. It’s designed for internal tools, admin dashboards, and B2B applications where: - 🛡 Reliability matters — Error handling, TypeScript, and predictable patterns - 🏎️ Speed matters — Pre-built auth, API integration, and UI scaffolding - 🔗 Xano is your backend — First-class auth and API integration - 🧩 Flexibility matters — Tailwind v4 + shadcn/ui give you fully ownable components - 🎨 UX matters — Optimistic updates, cache control, polished loading states, and smooth transitions https://github.com/ThinlySlicedShortRib/react-spa-for-xano I've already used it to migrate another project from Weweb and saw tremendous improvement in speed and quality. I'd be happy to showcase the template's capabilities. Just hit me up.

This week taught me one important lesson: progress doesn’t come from feeling ready; it comes from showing up anyway. 🚀 I’ve been developing a tool that I keep referred to in the video as an “automation” tool. However, I know better it’s a custom quote generator. 🧾 This tool features reusable templates, allowing companies to avoid the tedious process of rebuilding quotes from scratch. They won’t have to jump into Canva, place images, format text, and repeat that entire process each time. Or constantly looking for files to copy paste The contents to not have to write it down every time The real value lies not in buzzwords, but in the time saved. ⏱️ I’m new to this, and things break; some features only work halfway. My laptop moves as if it's on vacation! 💻🐢 However, I still committed. 🔁 Here’s what I learned: - Consistency beats talent when talent gets tired. 💪 - Confidence comes after taking action. 💼 - Broken things are feedback, not failure. 🧠 Nothing is perfect yet. The user interface still needs improvement, and the templates aren’t finished. But I’m not the same person I was two weeks ago Heck! I’m not even the same person I was a year ago. 🌟 This journey isn’t just about building one app; it’s about developing discipline. 📈 If I occasionally use the wrong words, understand that my intentions are right. I might call it “automation,” but what I really mean is saving people time and reducing stress. 😊 And if my Accent sounds different, that’s just the Caribbean in me! 🌴 I’m focused on fixing code, not my accent. So for those that might have an accent remember what matters most is your hard work and dedication 😂🫡👊🏾 Week two is complete, and week three is on the way. I’m not stopping! 🚀