At work we have strict rules around AI and for a long time I thought it would never be possible to get access to tools like Claude. In my personal life I've been using AI for a while now mainly to help me build Power Automate flows. I'm not technical but I know what I want and I've built a lot in SharePoint that helps me do my job. A few months ago I hit a wall. I kept having to explain to AI who I was and what I wanted every single time. I was done with it. Online there was so much going on that it felt like I was missing everything. Then a video from Jake showed up on Instagram. I scrolled past it twice. The third time I watched it. It was about the folder structure he used. I could see what he was building but I had no idea if it would actually work for me. After one week the results were way better than I expected. And it keeps getting better. Back to work. I wanted to find out what AI options were actually available within our company. So I showed my work to a few people. Turns out the company has a dedicated AI team already working with Claude. I didn't even know that. They told me I was further ahead than most people and that they loved seeing that I had picked up the folder structure the way I did. That is what convinced them. Only a few people in our entire organization have access to that environment. And now I'm one of them. Really happy about this 🚀🏆

I'm curious what everyone here likes to do for fun (of course building stuff with Claude is fun too lol), and if you've applied any AI to your hobby. For me it's been super useful for DND planning and I find I get to stay in creative flow more. Curious what other people are doing

So I haven't had the chance to dig into the classroom yet so I'm not sure if this is covered anywhere.. but this is my set of general vibe coding rules that I have been working on to use across all projects. This way I have a single "source of truth" for best practices to include on all builds and try to keep things clean. So far it has been working pretty well (from an amateurs perspective haha) and looking forward to stress testing it more. Please take it and use it for yourself if you don't have anything similar yet. Also, I would really appreciate any feedback from the more experienced devs/engineers in the group. 🙏 Edit for clarity: this doc is something I have been applying to all vibe coding projects. Not all projects in general. Another edit for clarity: I am just getting through Jake‘s ICM paper now along with the classroom material. I was not aware that he also refers to the claude.md as a global file to be handed off to the highest level orchestrating agent. This global.md would be better named something more specific and placed around layer 3 of the workflow (someone please correct me if I’m wrong). Anyways, hope this clears up any confusion there may be. Decided to change the name to vibe-code-rules.md for clarity =)