User
Write something
Pinned
Welcome to Clief Notes. Here's where to start.
1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?
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.
Claude Code to Codex: Same Context, Zero Setup, One Asset I Own
The context was not in the model. It was not in the tool. It was an asset I owned. Today I ran a test that I consider a real benchmark for the ICM methodology. I built a folder structure for Curiositas: one set of files designed to hold state, routing, identity, organizational knowledge, operating context, and the way we work. First, I asked Claude Code to pick up the work. Correct response. Right context. Correct identity. Current state of the work recognized. Then I opened Codex. I had never used it before. Zero setup. Same exact question. It read the right files by itself, understood the routing, and returned the same context: identity, state, open tasks, and direction of the work. Different words. Same content. Everything is documented in the video. Then I asked Claude to evaluate the result. The screenshot says: “solid result... this is basically a clean pass on the portability test.” And that is the point. This is real portability. This is real persistence. It means building something that does not belong to the platform, the model, or the AI tool I happen to open that day. It belongs to the structure underneath. It belongs to the asset I am building. I had already tried to solve this problem before finding ICM. I saw AI tools as fragmented by nature: a new tool every day, context scattered everywhere, work spread across different places, and nothing that truly remained mine. My answer had been to build my own framework. It taught me a lot. But in the end, it was becoming as fragmented as the problem it was trying to solve. I was working a lot, but the result kept moving further away. ICM is the layer I was missing. You are no longer designing inside the tool or inside the model. You are designing the structure that survives both. Jake Van Clief describes this as the future of how we will build software: a new way of communicating with machines. After this test, I understand why. I worked on this Curiositas lobby for half a day. From now on, I will improve it every day. I will make it more efficient and more tailored to me, to my way of working, to my processes, and to my company.
Question for the community:
What's one goal you're working toward this week, and what's the next small step you'll take today?
1-30 of 2,230
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