User
Write something
Pinned
🏆 HOW COMPETITIONS WORK FROM NOW ON 🏆
Quick update on the competition schedule so everyone knows what to expect. 📅 NEW CADENCE: TWICE A MONTH We're dropping comps on the 15th and the 30th of every month. Two chances to compete, every month, on a set schedule you can plan around. ✍️ WHY THIS SCHEDULE Spacing them out this way means we can give tailored feedback on every single submission. Not just the winners. Everyone who enters gets notes on what worked, where it's weak, and what to do next. 🎁 WHAT WINNERS GET Along with the prize, every winner gets a 15-minute one-on-one with Jake. Use it to talk through your build, ask questions, or bring whatever else is on your mind. Two comps a month. Feedback on every entry. Direct time with Jake for the winners. Mark your calendar for the 15th and let's get to work!
Pinned
🎆 GOOD NEWS: THE SALE STAYS OPEN. HAPPY 4TH 🎆
We're holding the last sale through the holiday weekend so nobody misses it. 🎉 Premium: $27 → $14/mo 🎉 VIP: $97 → $67/mo This is the cheapest it will ever be. Once it closes, the price is gone for good. ⏰ New deadline: July 5th, 10:00 AM EST. This is the last extension. If you've been on the fence, sign up now. You lock this rate in and keep it every month going forward. 🖥️ ONE MORE REASON TO JOIN The week of July 5th we're dropping the software we've been building for this community. It goes out for beta testing first, and only Premium and VIP members get access. Sign up before the sale closes and you're in from day one.
Trying the IDENTITY.md / CONTEXT.md pattern in a system with real retrieval guardrails
Been experimenting with something adjacent to the root-file orientation pattern from the ICM template, but in a system that works differently than a local folder setup. No folder hierarchy to lean on. Instead, everything routes through an orchestrator that gates every request through read-only guardrails before it touches any retrieval source. Multiple separate source types — filings, news, an internal knowledge base, a couple of specialized lookups — none of them organized in any kind of tree structure. Just distinct categories the router has to choose between intelligently. Write actions are completely disabled on a separate blocked path, so this is read-and-cite only, nothing gets modified. The question I was testing: could I still apply that root-file orientation thinking here, even without folders to organize? Turned out yes, but the implementation looks different. Instead of a file that sorts first and orients the AI at session start, it’s more about writing precise routing instructions so the orchestrator knows which source category to hit for which kind of question, and in what order to check them. Same underlying idea — give the system a map before it starts retrieving — just expressed through routing logic instead of a root file. Confirmed something for me: the folder structure was never really the magic. The instructions about how to navigate what’s available is the magic. Folders just make that easier when you have them. When you don’t, you have to be more deliberate about writing that logic explicitly somewhere else. Anyone else working in a system without folder hierarchy? Curious how you’ve approached this
Trying the IDENTITY.md / CONTEXT.md pattern in a system with real retrieval guardrails
How does everyone get Claude/AI to consistently follow ICM / Jake methodology on every build?
I've been working on this and have something that somewhat works, but I keep running into pieces that get messy and don't hold up well in practice. My current approach: the image I've attached lives in my AGENTS.md at the root of the project, so any time I build, the AI has the structure to reference. What I'm really after is the best way to implement the ICM system so that anything I build, Claude/AI already knows the way to build and stays inside that structure. Is anyone else doing this? Would love to hear how you've set it up.
How does everyone get Claude/AI to consistently follow ICM / Jake methodology on every build?
1-30 of 2,183
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by