Lessons From 13 Claude Code Projects That Changed My Product Manager Role
It’s been just a few days since the one-year anniversary of the term “vibe coding” — coined by Andrej Karpathy on X. That surprised me. It feels like it’s been around for at least two or three years. The speed of change lately is fascinating. I was a Head of Product a year ago and I still am — but the role has changed so much I can barely recognize it anymore.
Where it used to be about influencing future and imminent changes through complex collaboration and orchestration of various people across domains, it now revolves a lot around influencing through building and creating, mostly with the aim to speed up change thanks to vivid prototypes or even delivery of working products.
I decided to look back and show you 13 Claude Code projects that made me a different PM and that might either spark imagination on your end or a discussion about your own transition experience. Both work.
👋🏻 My name’s Ondrej. I’m a Product guy. I used to be a UX designer. I’m not an engineer. This is my story of learning to build with AI.
Overview of the Claude Code Projects
Spanning websites, web apps, iOS apps, custom MCP, Machine-learning prediction model, data analysis, presentations and even a print project.
- 🧭 Little Explorer — Native iOS app for parents to find playgrounds and family-friendly places nearby
- ⚙️ Little Explorer Ecosystem — Web admin for remote app configuration and macOS tool for testing map data across continents
- 👋🏻 Ondrejmachart.com — Personal website built in minutes, styled over hours
- 🗺️ Product Portfolio Coach — Web app that mapped 30+ Livesport products and helped leadership make a tough consolidation call
- 📱 Flashscore iOS Prototype— A vibe-coded clone of Flashscore iOS app so colleagues can prototype on top of it
- 🤖 ProductHub— Custom MCP I built to learn how MCPs work — and then stopped using
- 🌳 Family Tree — Printed family tree that goes back to the 17th century, made for my dad for Christmas
- ⚽️ Football Predictions — An ML model that tried to predict football goals — and taught me more than the predictions did
- 💡 Vibe-Coding Workshops — Helping colleagues at Livesport start building with AI
- 🍼 Tinystakeholders.com — Lenny Rachitsky’s podcast transcripts turned into parenting hacks for tired PMs
- 🎨 Infographics Tool Prototype — Configurable sports infographics for editorial teams — scary close to production
- 📊 Data Analysis & Presentations — Using Claude to analyze data, create web presentations and Confluence pages
- ✅ Personal Task Tracker— Because no tool on the market serves my needs perfectly
Some are still running in production. Some helped our C-level make a major consolidation decision. One is just a family tree I made for my dad.
I’m not sharing this to sell you a course or convince you AI will save your job. I’m sharing because this transition has been equal parts exciting and terrifying, and I think we need more honest conversations about what it actually takes.
🏄 Mindset Shifts That Can Get You Further
Before we get into the projects, here are the mindset shifts that made the biggest difference along the way. I wish someone told me these before I started. The projects below will show you what they look like in practice.
🔧 It’s not magic, it’s work. AI gets you far but it’s not free, not effortless, not without risk. It’s still a lot of work, just different than coding.
🥚 Start by solving your own problem. Learn the basics on your own case before trying to solve someone else’s problems. You’ll get immediate feedback from your most devoted user and fan.
🪦 Your project can die and it may still be a win. Some of my projects served their purpose and didn’t need to live on. The outcome isn’t always the tool. It can be learning something or influencing a decision.
🏔️ Respect the challenge you’re tackling. Vibe-coding does not equal competence. The gap between prototype and production is real and humbling.
👀 Know your blind spots. A UX designer might vibe-code fantastic frontend experience with a backend that won’t scale or will be leaky. An Engineer might vibe-code a functional product that can scale but won’t because it’s unusable. Both can fail because the decide to tackle a problem nobody wants to pay for having solved. Know your blind spot and think about your options to remove it.
🛋️ Don’t protect your routine from new things. AI comes with something new every week or two. Be open to it. Don’t jump on anything and everything immediately, but also don’t close yourself off from new things entirely when the comfort zone gets established.
🤝 Let others take over and surpass you. You don’t always have to be the solo builder, even if that feels more natural to you. I strongly believe AI is not here to make us more individualistic, just more lean in terms of how many people are needed to build something. Partner up with someone who also loves building with AI and who has the skills you don’t. Choose someone you enjoy working with.
🎲 Embrace AI’s non-determinism. Stop fighting the randomness — sometimes it’s exactly the right tool for creative work.
And most importantly, have fun with it. Taking it too seriously too early may just kill the vibes.
1. Little Explorer — iOS App Published to the App Store
This was in September 2025. So just six months ago. Before this project, I used AI mostly to polish copy, improve emails, generate images, research markets. Optimization of outputs rather than creating complex things.
I had a mind full of ideas for my own little pet projects. So I obviously tried Replit, Lovable, and all the other vibe-coding tools and created a few prototypes. But none at the time offered a way to build an actual native mobile app (not true anymore). Then a colleague of mine suggested using Claude Code in the terminal, letting it basically work with an Xcode project and build the app. I fell in love with the idea and for two months I learned the ropes over evenings and nights. Motivated not by getting rich overnight but by building something people might actually use. Completely solo.
Nothing beats the stress of changing something that can break on people’s phones when it’s your name under it.
In November 2025, I finally published the app in the App Store. With a subscription built in, with several third-party API integrations, and with about a hundred users monthly — parents who need to find the nearest playground, toilet, or other family-friendly places nearby.
This was a kick-start for me because it wasn’t just a prototype. I had to deal with securing the app, lots of debugging, API provider implementation, App Store submission, legal document creation, etc. It was so much fun. And it just felt good to see the app in the store. Because in a world of a PM who can spend months pushing for changes, this felt like each day had an instant reward moment, or several of them. Something a creative mind craves.
👉 If there’s a takeaway for you here, I think it’s that AI can get you as far as publishing in the App Store — but it’s not for free, it’s not without effort, it’s not without a lot of learning, it’s not without the risk of failing, and it’s not worry-free in terms of the quality of the code if you’re not technical enough to keep an eye on the architecture. It takes a lot of iterations of how you approach the coding.
PS. Here’s an article about building Little Explorer.
2. Little Explorer Ecosystem — Remote Config and macOS Admin
As part of the Little Explorer project, I soon realized that optimizing the API configuration for finding the nearest playground, toilet, zoo, or picnic area requires unreasonably frequent app updates. So I decided to take this part of the app’s business logic and move it to a web application. There, I can remotely configure each of the nine categories in the app — which API provider to use, how to search, what radius to apply. All of this can be changed and the apps in people’s phones will pick it up on the next launch — not after updating the app.
This was tricky because it’s not just about creating a nice interface. This is a critical dependency for an app that is on the App Store and in people’s devices. I had to learn a lot about testing to make sure it’s bulletproof. I still wake up at night with ideas where it might be weak. Nothing beats the stress of changing something that can break on people’s phones when it’s your name under it. That stress is healthy — it makes me double down on testing and learning.
That stress is healthy — it makes me double down on testing and learning.
I also built a macOS admin app — partly because I was curious if I could, partly because I genuinely needed it. I wanted to test the API providers across locations — does MapKit work for toilets only in the US or in Europe too? Can Mapy.com find good playgrounds not just in Prague but also in Jakarta? The macOS app lets me configure the API, see results on an interactive map, and move between cities, villages, continents. It also lets me see all the places found by real users and check if the playgrounds it found are actual playgrounds or something completely different — like a junction of three highways in Singapore (happened) or a WWII monument (also happened). Because it’s a macOS app, it can test the MapKit API natively, which behaves completely differently on web.
👉 The takeaway from this whole ecosystem is that AI can get you surprisingly far beyond the prototype — into production dependencies, remote configuration, cross-platform testing. But the further you go, the more you need to respect what you’re building and who depends on it.
3. Ondrejmachart.com — Personal Website
Well, this one is easy. There’s probably no better and safer use of Claude Code or any coding AI model than building your own little static website. Hosted for free on Vercel, built within minutes. I needed a place to lead people from the App Store — about me, contact, app landing page, legal documents. Simple needs.
The fun realization was that while the vibe coding took minutes, it took hours to iterate the little details like font, style, colors, etc. Because this time I had absolutely no vision, just a need. But once the website appeared in front of me, I suddenly started to have opinions about how it looks — unstructured, chaotic, changing, unclear.
Frankly, during vibe coding of most projects I don’t mind this state of mind because the UI appears rough at first and I slowly but surely mold it through using the prototype and iterating it. But when it comes to a static personal website, it feels more like building a digital mirror — and that’s somehow harder to wing (or, well, vibe).
👉 So the surprising takeaway is that if you ever vibe code your personal website, maybe don’t start with nothing but the purpose and content (that should always come first, period) — spend a bit more time prepping about the style. You will want to feel good about it. And vibing your way to a style is exhausting.
4. Product Portfolio Coach — Web App for Livesport
This was the first “serious” tool I vibe coded at work. Our company has over 30 products in its portfolio. Some similar, some specialized, some larger, some smaller. What we always lacked was a space where you could look at all the products through various lenses: finding the most similar products ripe for consolidation, making decisions about differentiation of new products, etc. So I decided to make a tool that would give us this level of transparency and clarity, to help us make better decisions through seeing the forest, not just the trees.
It was fairly simple in terms of data — I didn’t connect it to any internal API, I just created an admin section where I could manage the product information. Where it got interesting was the frontend and interaction UX. I wanted to create a canvas where one could freely move the products on two selected axes, e.g. product size and primary audience. Achieving a FigJam-like experience wasn’t easy, but I got pretty close to it with optimistic change handling.
What made my day was that the tool eventually helped our C-level management make a tough decision about major brand consolidation
I also wanted to create a “similarity map” where one could see clusters of products that share a lot of traits — like the sports they focus on, the depth of sports data, the complexity or simplicity of the data visualizations, etc. It was both fun to create a complex UI and to uncover the insights about the portfolio. I also added an AI feature that allows us to pick any product(s) and let AI analyze them through all the data we gathered in the tool.
What made my day was that the tool eventually helped our C-level management make a tough decision about major brand consolidation that aims to help the company work more effectively towards its ambitious goals. With fewer products, this tool has a dim future — but that’s OK. It served its purpose, and not needing it is actually a great outcome.
👉 I would say this is one of the takeaways — if you see a problem worth tackling and dare to try vibe-coding your way out of it, give it a shot. You don’t know how far it will get you, but you will definitely spend quality time analyzing the problem, which is healthy — no matter whether the tool becomes the solution or just a vehicle to get you to it.
5. Flashscore iOS Prototype — A Shared Base for Prototyping
The next challenge I wanted to tackle was massive: to vibe-code a clone of the Flashscore iOS app so that me and my colleagues all have a great starting point when prototyping new features and ideas. The problem I wanted to solve was that whenever people tried to prototype using vibe-coding tools like Replit, Lovable, or others, they had to first spend a fair portion of time and effort cloning the UI. They provided AI with screenshots, Figma files, exported styles — but it got them mostly nowhere. That’s fine for quick exploration, but when you want to test with users or show stakeholders, you need to get closer to the real product.
This turned out to be a perfect challenge for my awesome colleague Petra, who is our DesignOps team lead — she started to create one screen after another, providing the team with a shared GitHub repo anyone could pull to start working on their prototype. Because Petra is more technical than I am, she completely took over and marched forward. We’ve already prototyped a couple of ideas like a top matches widget, and it works (almost) like magic thanks to the Figma MCP — you copy a prompt, it takes UI from Figma, and you have the prototype ready, sometimes on the first try. But it works great also when we don’t have any Figma design yet and just want to explore ideas.
👉 The takeaway here is that sometimes vibe-coding can be a tiny quick project, but sometimes it can become a multi-month challenge to enable others to prototype quickly — and that it’s great to have someone who’s more suited for that challenge and is up for it.
6. ProductHub — Custom MCP with Kanban Board
At this point I felt a bit weird. I had gotten quite comfortable with my setup: Claude Code in the terminal, directly building on my file system. I alternated types of projects and platforms, but it started to feel like a routine. Then MCPs became a thing. I heard about them on podcasts, read about them in newsletters. And somehow I couldn’t wrap my head around them. They felt new and kind of threatening to my routine.
If AI is coming for our jobs, we should at least also have some fun with it while we can.
When I finally decided I was open to learning about MCPs, I asked Claude what’s the best way to do so. Claude suggested building my own MCP. That sounded pretty cool — I love learning by doing. I decided to build a hub for vibe-coding projects — a Jira-like kanban board where I could create tickets, and a custom MCP that would enable Claude to connect to the hub, to the respective project, and to the tickets.
I decided to build an MCP for vibe-coding projects — a Jira-like kanban board.
And it worked! I could tell Claude to work on five of the tickets in the backlog, moving them to “for review” when done, committing to git separately. I went to lunch and when I returned, the tickets were all waiting for me. So I added another tool — to save important context about the project so that next time I start a session, Claude can pull all the important info via the MCP. That worked too, albeit it uncovered a new layer of complexity. Maintaining the context and avoiding confusion wasn’t easy.
Eventually I realized I actually prefer not to use my own tool. Creating tickets felt unnatural to the vibe-coding routine.
Eventually I realized I actually prefer not to use my own tool. Creating tickets felt unnatural to the vibe-coding routine. It added steps to what benefits from a lack of process when exploring ideas. I decided the purpose of this project was served — I learned how MCPs work. A few months later I discovered Serena MCP — context management that works without my inputs and extra steps. Plus, most task management tools published their own MCPs, so if I ever decide I need a bit more organization to my flow, the solution is out there.
👉 The takeaway here is simple: there’s something new in the realm of AI every week or two. The best way to learn the new tricks is not to read about them but to use them.
7. Family Tree — Printed Family Tree Going Back to the 17th Century
My father had a firm belief that our family comes from a French soldier from Napoleon’s army who fled and knocked up a Bohemian girl. I’m not sure how he arrived at this, but he was dedicated enough to prove it that he hired a genealogist to track our true roots. She made it to the 17th century. No French soldiers, just poor tailors of questionable morale. This was a bit of a flop for him.
To cheer him up, I decided to turn the genealogist’s notes into a proper family tree — with a family coat of arms, a map of places where our ancestors lived, their stories woven into the historical context, a tree design, and AI-generated portraits of our ancestors based on photos of our family members. All generated with AI. Images made by ChatGPT, text by Claude. I let Claude read the notes, do online research on the history of the villages where my great-great-great-grandpas lived, and then I put it all together in Figma (which was surprisingly OK for print).
I had it printed on A0. My father loved it so much he decided to print it on an even larger format and started giving it to his cousins and distant relatives — even those who aren’t captured on the family tree. It truly made his day to see little details related to his professions and passions, and his dad’s. And for me it was a nice pet project after all the work stuff.
👉 The takeaway wasn’t the print. What I realized is that I often get frustrated when building with AI when it doesn’t behave somewhat logically. But AI is in its nature non-deterministic. It is made to be creative, to act somewhat unexpectedly. This was a perfect fit for its capabilities.
8. Football Predictions — ML Model for Major European Leagues
Our company has always been fanatic about sports data. Then we got obsessed with insights. And lately, we’re falling in love with the idea of predictions. Not subjective ones, but data-powered. Predicting goals is like the ultimate pinnacle of drawing insights from the wealth of stats and data.
That got me thinking about two things. First, how would predictions look and feel in the product? And second: hell, can I build a machine-learning model predicting goals? Never mind that I wouldn’t be the first or last one to attempt it. The fun element of giving it a shot was just too strong to resist. So I had Claude research the methods of predicting football, then I had a discussion with it to help me understand it a bit more. And then, as usual, we got to work.
I did not make a model that beats bookmakers. But I explored tons of ways to work with the data in the UI that helped me as a PM to have fruitful sessions with the UX designer, AB tester, and engineers.
After a couple of iterations, I had some interesting predictions for the Premier League to test against reality. And I also learned about feature engineering, time decay, MAE, LightGBM, hyperparameter tuning, walk-forward validation, and XGBoost. Things that probably won’t make me a fun person to chat with at a party (unless it’s a nerd one) but that excited me and made me appreciate the complexity of the ML domain.
Did the predictions work? Well, let’s just say that football is beautiful because even bookmakers who have the most advanced ways of predicting match outcomes are only slightly better than a flip of a coin. I did not make a model that beats them. But I explored tons of ways to work with the data in the UI that helped me as a PM to have fruitful sessions with the UX designer, AB tester, and engineers. That’s more than I predicted.
9. Vibe-Coding Workshops — For Colleagues at Livesport
This AI era is pretty stressful for PMs (and not just for them), to be honest. We have a lot on our plates any day of the week. A lot of operational work that won’t wait, a lot of conversations that should have happened yesterday, a lot of stuff to ship. To allow yourself to slow down or even stop for a while to catch up with everything that’s been happening with AI feels impossible most of the time. To adopt the tools and new ways of working may feel out of your comfort zone, slowing you down at first, risking the quality of output people expect or depend on.
I found myself learning a lot only thanks to spending time vibe-coding and playing with AI in late hours, when my wife and kiddo sleep. It’s not healthy and sustainable. But somehow it felt impossible not to do it this way. It felt stressful to fall behind. But perhaps more importantly, it also felt the most exciting thing since my discovery of Lego as a kid. Those bricks gave my imagination an endless space for creativity (well, limited by my parents’ Lego budget). AI feels the same way.
There was never a lack of ideas to build, just the barrier to start building.
Thanks to this — and thanks to a more healthy attitude towards sleep time on my colleagues’ part — I got a bit ahead in the use of AI. So I soon began organizing workshops for those interested in how I build with Claude Code.
Most colleagues who joined used AI, just not for building stuff. Turned out it was mostly just because they didn’t know how to set it all up — Claude Code in the terminal, the packages, etc. There was never a lack of ideas to build, just the barrier to start building. Most colleagues left with a prototype of their idea. Some came to me later with something real:
- A morning quiz game app in the App Store by Jirka.
- A personal planner app for a big Japan trip.
- A website with gourmet restaurant tips by Martin.
- An internal tool for UX team capacity allocation management.
- An internal tool for design system implementation monitoring by Petra.
- A website for dad’s plumbing business by Kristyna.
- A Pacman game where Pacman is a cat trying to make its way through rooms where roomba, angry kid and other enemies get in the way
So many great ideas. It felt awesome to see people giving shape to the solutions they craved.
👉 This eventually sparked a change in my role. Where I used to be a bit drowned in operational delivery details, I see my role becoming more focused on tackling complex challenges through rapid prototyping to shine a light on the ways forward. And what makes me truly happy is to see my colleagues picking up the tricks, oftentimes soon surpassing my own skills in their own ways.
10. Tinystakeholders.com — Product Wisdom Meets Parenting Hacks
Early in 2026, my favorite podcast author Lenny Rachitsky made all his 300 episode transcripts available for the public to play with. What a nice move from him. Immediately, people started to share amazing projects, mostly revolving around using the sheer power of insights Lenny’s guests have shared throughout the years to answer product people’s burning questions.
My burning questions lately have been “why is my 2-year-old son running around naked refusing to dress up,” “when will he stop licking things,” and “what’s this weird thing on the wall.” I thought it might be fun to try to use Lenny’s transcripts to draw parenting wisdom (or at least some cheap tricks) rooted in PM concepts, frameworks, and tactics. To my surprise, it worked pretty well. It felt weirdly scientific, so I let Claude learn the humor of some famous standup comedians and rewrite the parenting tips to make the tired PM parent laugh-cry into their glass of wine at 2 AM.
I sent TinyStakeholders.com to Lenny, he posted it on X and LinkedIn. I wrote a Medium article, he loved that too. That genuinely made my day. Over 5,000 people read the article and saw the website, some sent me nice messages about how it motivated them to build something too.
I have zero dollars from this project. It has nothing to do with my job. Lenny did not invite me to his podcast. Most of the parenting tips did not help to get my son to enjoy dressing up. But I had a hell of a lot of fun learning how to work with a large dataset (300 episodes, each roughly 90 minutes — that’s a lot of words!) and adding that baby with a toilet paper roll to the homepage.
👉 The takeaway is that if AI is coming for our jobs, we should at least also have some fun with it while we can.
11. Infographics Tool Prototype — Scary Close to Becoming an Internal Tool
Things can get awkward with vibe-coding. When done wrong, it fails spectacularly. By done wrong I mean treating vibe-coding as magic — building things you don’t understand, not learning how they work, and assuming that a functioning prototype makes you a competent builder. This is the case with most projects people build — not because they’re stupid or lazy, but because curiosity alone doesn’t always carry you through the extra mile. And even if you try hard, without technical knowledge there will always be the gap and the risk that comes with it.
Things can get awkward with vibe-coding. When done wrong, it fails spectacularly.
This is a long prologue to this project. Because it’s the first project that seems to be evolving from a vibe-coded prototype into a production internal tool. It raised questions, eyebrows. It made me feel like an idiot when pitching the idea to skilled developers and TPOs. It’s too soon to say if we made the right call because we’re still building it, not sure if it’s the way forward. But at least I feel better now because a great colleague, a senior engineer, joined forces and took the leap of faith with me to orchestrate the architecture and data plumbing while me and my PM colleague vibe-code the frontend.
The tool offers configurable infographics for our editorial teams to enrich their sports articles. It auto-translates, exports images, works in three different aspect ratios, and supports multi-brand usage. It’s scary. That’s good. It’s not a production tool yet and we’re not sure if it will be. But we are exploring the path. And that’s perhaps more important than whether this will become the official tool or not.
👉 Vibe-coding needs more respect — not more respect for vibe-coding from people, but more respect from vibe-coders towards the challenges they dare to tackle. Take that as a takeaway.
12. Data Presentations — Web Presentations and Confluence Pages
The first data analysis Claude Code did for me had great output content-wise, but design-wise it was just an ugly standard terminal message. I pasted it into the slides, but I knew there’s more Claude Code could do with the data and insights. So next time I asked Claude to take the data and insights and turn them into a web presentation — literally coded slides, with keyboard controls, no scrolling, Livesport brand applied.
I asked Claude if we could turn the web presentation into a Confluence page. It suggested using a community MCP. It worked just fine
It was great. We had a decision to make about sunsetting the support for Huawei devices and we managed the internal communication smoothly thanks to the presentation Claude created. A chart that showed less than 1 percent share of our audience made everyone relaxed. Except my boss Tomas, who prefers to have these things either in Slides or on Confluence. So I asked Claude if we could turn the web presentation into a Confluence page. It suggested using a community MCP. It worked just fine — the decision is now documented on our Confluence space with all the charts exported and insights captured.
When my documentation-obsessed colleague saw this, he almost fell off his chair. He loves having things documented but hates documenting them. He’s a free man now.
👉 Take that away — explore the MCPs of your favorite tools. Chances are Claude can do so much more for you than you think.
13. Personal Task Tracker — Because No Tool Serves My Needs Perfectly
Phew, last project. I can’t believe you made it here — it’s a pretty long article. Which probably means you have ideas bursting to get out — and notes everywhere. Physical post-its. Phone notes. Jira. Trello. Handwritten notes on your arm. Chances are none of the existing tools work for you — they may be too expensive, too complicated, missing a critical feature you’d love to have there. Well, that’s my case too.
I don’t have the ambition to make this a product. This is a product tailored to my needs, my flow, my habits, my preferences.
So perhaps unsurprisingly, I ended up trying to fix myself with a custom task management tool. I realized how much I miss the good old Wunderlist. It had just the right amount of features. No complex flows, no kanban boards, just a list, tags, nice UI. There’s no better time than today to build the long-lost products that got acquired and destroyed by soulless corporates. I told Claude to give me back the amazing UX of Wunderlist. The micro-interactions, the smooth animations — it’s all there. The best part is that I can add, remove, or adjust features based on my own usage.
I don’t have the ambition to make this a product. This is a product tailored to my needs, my flow, my habits, my preferences. With nothing extra that gets in the way. Perhaps one of the best use cases for vibe-coding there is.
👉 The takeaway? Perhaps the best product is one built for exactly one person. No compromises, no feature requests, no backlog. Just your own needs, your own flow, your own taste. If you’re new to vibe-coding, this might be the best place to start — the only user that can suffer from your creation is you.
⚒️ Tools I Use the Most
Over time, I got comfortable with using specific tools for achieving specific outcomes. Here’s a list that may be useful to you. In terms of cost, I pay $100/month for the Claude Code Max plan and $20/month for ChatGPT Plus. I use free tiers for Vercel, Supabase, and Railway. The only other expense is a couple of domains on GoDaddy, each under $20/year. That’s it.
- Claude Code in the terminal — I prefer this over any tool that has the AI models baked in and adjusted for specific use. Having Claude Code’s raw power somehow feels a bit more flexible.
- VS Code— I don’t use the agent panel, I just open a tab with the terminal. I like the tool simply because I can have multiple tabs and see the project structure, files, and read the documents.
- GitHub and GitHub CLI — For versioning and auto-deployment.
- Vercel + CLI— For production. Sometimes just front-end, sometimes even backend and databases.
- Supabase + CLI— For databases.
- Railway + CLI — Handy when the tech stack includes a Postgres database.
- ChatGPT — For image generation. But that’s just habit. There may be better options.
- Serena MCP — For context memorization. Awesome as it speeds up development, reduces AI confusion in the codebase, and saves tokens.
- Figma MCP — When you have designs in Figma and want to achieve pixel-perfect implementation.
- Chrome DevTools MCP— Allows Claude to “see” the web project, debug, and analyze performance.
- Google Search Console API — Allows Claude to check your site’s SEO performance and suggest improvements.
🤙 Share Your AI Projects
I’m genuinely curious what other people are building with AI. What they learned. What they struggle with. It’s one of the most fascinating times to live in for people who are builders at heart. If you’re one of them, I hope this article was helpful. I’ll be grateful if you share it with your creative friends who could benefit from it too. And I’d be excited if you drop your projects (links welcomed) in the comments. Let’s inspire each other.
