User
Write something
High Tea is happening in 12 days
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). 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, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
6361 members have voted
Pinned
☕ June Tea Schedule
Sat, June 13 3pm: High Tea Sat, June 20 2pm: Afternoon Tea 3pm: High Tea Sat, June 27 2pm: Afternoon Tea 3pm: High Tea Mark your calendars and we'll see you there!
☕ June Tea Schedule
Pinned
🚨 You've been asking when the Lyceum opens. The waitlist is live. 🚨
The waitlist is up and seats are limited, so this is your nudge to go lock yours in. 👇 New here? Quick context. 👀 The Lyceum is Jake's live cohort program built on ICM, the methodology 35,000 people in this community are already using to get real results with AI. The short version: folders over agents. You learn the layer underneath the tools, the one that keeps working when the next model drops. Full breakdown is on the site. Here's what's inside: 🎯 Three cohorts, Technical, Business, and Creator. Same methodology, built around what you actually do. 🎥 Live sessions with Jake and a full team of instructors. ♾️ Lifetime recordings, written curriculum, and a private cohort Discord. 📜 An Eduba ICM certification you can put on your resume. And a guarantee no course makes: ✅ You leave with a working product, or the team finishes it with you. ⏳ Seats are limited and this community moves fast, so the math is not in your favor if you wait. 💡 Pricing and start dates aren't public yet. The waitlist sees them first, gives feedback on timing, and gets in before the program opens. Everything you want to know is on the page. If you already know this is for you, get on it. 🔥 👉 https://lyceum.eduba.io
Debugging a Production API Integration with Claude Code and ICM
I debugged a broken production API integration — code I didn't write, in a language I don't speak — without hiring a developer. The ICM is why that was possible. ______________________________________________________________________________________________________ We run a custom PHP middleware that keeps two platforms in sync. A developer built it. I am not a developer. It had been running degraded for months. Error logs hit 13 million lines in a 4-minute window. Inventory numbers were inflated. Customers added in one system never appeared in the other. A SQL injection vulnerability was sitting quietly in the order dashboard. Nobody touched it because nobody felt qualified to. ______________________________________________________________________________________________________ Before I did any debugging, I built the workspace. Not "open a chat and paste the error log." Build the folder first so the AI always has the right context for the right task. That's the ICM move. - CLAUDE.md at the root — one file mapping the entire project. What the system does, where every file lives, what each folder is for, what naming conventions to follow. Every session loads this first. - Source files pulled from the server and organized locally into subfolders by function. The server has everything flat. The local folder gives the AI structure to reason about. - A parsed log summary instead of the raw log. 13 million lines uploaded once, converted into a structured breakdown by file, line number, error type, and frequency. Every future session loads the analysis. The noise is already filtered. - A fixes folder and an archive folder. Every fix gets a doc. Every original file gets archived before it's touched. Messy work happens here without polluting the reference layer. - A routing table. A markdown table that answers "I want to do X — go here, load these." Every session goes straight to what's relevant. Once that structure was in place, the workflow was repeatable. Load context, describe the symptom, Claude reads the file and writes the fix, archive the original, deploy via the hosting file manager, update the fix doc. No terminal. No git. No local PHP environment.
0
0
Feeling Lost - But still winning in a way?
Gosh, feeling lost in this one. Problem would be that I started setting up my workspace, not as a clean state, but as everything that I have been doing that's saved on my desktop / Google Drive and just dumping them into folders, without actually putting in the time and effort to understand what each folder is for. It doesn't help that I am wearing 3 hats in the organisation, part of being in a family business you see? and the context is lost even within my own head. Essentially there was little thought behind it - and that is my own issue to get through. WIN: The automation project I am working on via n8n for work is going extremely well, I am happy with the AI Output that is being called, now working with our in-house dev to get the output into our own software and it is very exciting, because it will probably be saving around 2,500 minutes a month across the whole organisation, and more as we scale - so I am happy there. Things to Improve: What I am not happy about is that I've been using ChatGPT online, rather than codex and using the ICM Structure. So there's been a lot of back and forth, of context loss, and repushing. My own fault I know. Next Steps I tihnk the next step for me, after I review the Foundations again, is to actually start my workspace small, start it with the basics - speerate the folders into my roles, then within those roles, sperate the folders into businesses, then go into the layers from there. Or is that too much, again, lack of foundational knowledge - I see that. Anyway, just wanted to ramble, wil go back through foundations get my head on straight! Over Arching Goal: How do I deploy these automations that I am creating, for the business to run more efficiently, so that the whole team can use them? - That's where I get stuck (Because I am jumping ahead, that can be figured out eventuially). Thanks for the community for being awesome - appreciate you all.
1-30 of 1,503
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by