I have been um'ing and ar'ing about what to write as my first community post and have landed on sharing a recent experience working with Claude Code and one of my projects. I started the way I always have. A CLAUDE.md, a Project Blueprint and the foundational code I have already written. This project was started before I joined this community, but the foundation of these documents align closely with the CLAUDE.md, CONTEXT.md and REFERENCES.md Jake advises in the foundations class. Two weeks in and my CLAUDE.md has drifted into a "what-not-to-do". Fourteen days, one project, ninety two files of code and scripts, and the file is now something else entirely. The identity block is still in there, the first three sentences, but that's about it. Everything underneath is a list of things that went wrong once. Not best practices. Things that went wrong, with the damage still attached. One entry says never to add a certain kind of field to the messages my tool sends, because the first time I tried it the program on the other end quietly gave up mid-conversation and left the whole thing hanging. Another says to check which folder I'm in before saving anything, because one of my tools forgets between commands, and I wiped a working file twice before I bothered writing it down. The code already says what the thing does. The file says what has already bitten me. Which brings me to the bit I actually wanted to post about, because it's the part I got wrong repeatedly. I had that file. It was good. Rules about testing properly, about not guessing, about verifying claims instead of assuming them. And I still shipped four bugs in a row that were the same bug wearing different clothes, and I didn't see it until the fourth one. They were all in the gap between two things that were each working perfectly. My site once showed six software packages as needing attention for a week after I'd already dealt with all of them. One part of the system keeps a history of alerts. Another keeps the current status. The page was reading the history and reporting it as the status. Both parts were doing exactly what they were built to do. But nothing and nobody owned the handover between them.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ ($4,750 Seat) Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE This is a weird one, and you may feel lost at first. But it's up to you to make a map for those who come after and if there is no map, you must get lost to make one. Build a folder-based cartographer that can walk a body of work and leave a map a later reader can wander and show what that map is. The later reader is often an AI. Sometimes it is a new person. Same map. Same job. Not why it failed. Not how to fix it. Not a tour of how the week goes. What the nouns are. How they move. What else moves if you touch one. What is live, what is leftover, and what is a ghost with a name and no wiring. This week's deliverable is one cartographer folder someone can drop into a Claude project, point at a real body of work, and get back a map a cold reader can enter without reading the whole thing. 🎯 PICK YOUR TERRITORY Pick a body of work you have actually been inside. Something a new person or a cold model would get lost in. Something someone will change, not something you will only describe. A few sparks: 💻 A repo you own. Even a small one. The map is for the next developer, or the next session, that has never seen it. 📂 A client delivery folder a VA or a contractor has to inherit next month. 🧩 A Make, GHL, or n8n pack someone else will edit without you on the call. 📒 An Obsidian or Notion vault a collaborator has to add to without breaking the spine. 🧾 The live records behind how a job gets quoted, approved, and invoiced in your shop. The files. The objects. Not the story of a bad month. 🎓 A course or L&D library someone will update after you. 🏭 The asset and work-order objects in a plant system you actually touch. The more specific, the better. Maps how our business works is too broad. Maps the five objects a new hire has to understand before they touch the invoicing folder is right. 🧠 WHAT YOU ARE ACTUALLY LEARNING ICM has six forms. You have been living in the first ones. Pipeline. Coach. Editor. Diagnostician.

You all mean a lot to me. I truly enjoy this community. Everyone is so excited about using AI and building things that matter. I love how people show up here to help each other and celebrate the wins. Goodness knows, I have learned so much from each of you and I thank you. That said, some of what I am reading, both posts and responses, is mostly generated by AI (if not entirely) and it makes it harder for me to connect with them. I’ve used AI in my own responses too, so I’m not throwing stones. But I do try to make sure it still sounds like me. I’d love to see more of people’s real voice, even if it’s less polished. Yes, ChatGPT assisted me in creating this post - but it's MY voice. ;) You're all amazing!

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

Since I'm starting to use Claude Code to build and Cowork/Chat to think and do smaller tasks, what should i do with my global instructions and Instructions for Claude?