Hey everyone 👋 I’ve been learning a lot here around AI workflows, systems, memory, and modular design. Instead of just consuming, I want to start building more seriously. So here’s a challenge: Give me a real problem or use case, and I’ll try to build an AI system for it. It can be anything: - automation - agent-based workflow - memory system - business use case I’ll build it, test it, and share what works (and what doesn’t). Trying to move from learning → building. Let’s see what we can create 🚀

Hi all, So I'm working on building out my content creator architecture, and one thing that keeps popping up in my mind is the notion of a 'change log'. "Why would you need this?" you might be asking? Here's my initial theory here. I want to ensure that I am keeping this clean and tidy, up-to-date. But within my structure, there are going to be at least 3 context files that store base context. Now, instead of going into each file, I can give specific instructions within VSCode to adjust the context based on the ever-changing landscape. There would also be direction within my CLAUDE file to document said changes so, in case I see a bug or a consistent flaw in my flow, I can go track it down easily by simply uploading the changelog to a claude chat, describing the issue I'm seeing, provide an example or 2, and continuously iterate. My question to the community is more to gain thoughts around the notion of a change log, and what other use-cases could this have to be a pseudo 'undo' redundancy tool in the workflow?

Is everyone caught up with all the new claude code features? so many new features i don't know what new capabilities i should start learning 🥲

What are your thoughts on cross prompting? I use free GPT for cleaning my initial prompt. I inject the output to Copilot, and this is my Claude prompt.

NOTE: You will need a paid subsrciption to Blotato.com for this to work. Sabrina Ramonov, the creator of Blotato, has a video here called Claude Code Full Course https://www.youtube.com/watch?v=fYX6hHC9FhQ&t=3374s. I think it's poorly named as it actually teaches you how to create a workflow in Claude Code to control her Blotato system via the API. Her approach was to get everything connected and working THEN she create the CLAUDE.md at the end taking advantage of the working system as a "guide for the guide." I took a different approach. I took Jake's folder-organization-guide.md and the most of the text from Sabrina Ramonov's note that accompany the video here https://www.sabrina.dev/p/claude-code-full-course-for-beginners and fed them both the Claude Cowork (I modified the text by taking out anything I knew would be contrary to the folder organization guide). Then I prompted Cowork to develop a folder structure for this project using the folder organization guide as the way to do it. It created a great folder system recommendation for me. It also created the CLAUDE.md for me. I then created that folder system and loaded it into VS Code /Claude Code. From there, I simply followed steps 1 through 6 of Sabrina's video and text guide. It worked like a champ! AND it was much easier to follow as I had a system based on each social media channel I wanted to communicate with. My file structure changed a bit during my development as I learned things, but this gets you a good idea of the structure and why: blotato-social/ ├── CLAUDE.md ← Layer 1: The Map. Routing table, naming rules, API ref │ ├── shared/ ← Cross-platform workspace │ ├── CONTEXT.md ← What "shared" is: log format, plan format, conventions │ ├── posts-log_current.md ← Running log of all published posts + live URLs