Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
Clief Notes

45.2k members • Free

28 contributions to Clief Notes
ICM Methodology in Excel?
Context: My company is hell-bent in still making excel work for everything. 10-15 worksheets inside one file, THOUSANDS of rows and columns per sheet. Curious question, do agents follow the same ICM principles when you point them at an excel file? Ex. Routing logic in first worksheet so the agent knows where to go instead of searching the entire workbook for something.
0 likes • 2d
That's exactly what I do, call the excel file the readme only and your .md file the append clone. Weekly scan and work .MD file....much faster
ICM without Claude
Hi everyone, First-time poster here. I'm looking to understand how others in the community are using the Interpretable Context Methodology (ICM) without relying on Claude Code. I've been actively building personal projects on my home setup, and every day has been a great learning experience using this folder-and-markdown architecture. However, I've hit a roadblock at work. I develop data analytics and business intelligence workflows, and we have a strict constraint: we cannot use Claude. I'm curious how others integrate Jake's ICM framework when Claude Code isn't an option. Are you using tools like Aider, Cursor, or other terminal agents BR Paul Update - Some people are already using non-Claude setup. If you could kindly explain/illustrate how you do this, I would be very grateful.
1 like • 9d
They said you can't use claude, what about just running scripts in your folder?Claude can build script, instead of claude working the files. The folder are the folder especially when using for project stage cycles.
Been away for a while
Hi guys, it's been a while. I have been away for more than a month now, I hope I haven't missed much. 😄I know I did, hoping to catch soon.
0 likes • 9d
Welcome back, i know how it feels....I just got caught up i been missing. Quick recap....Jake just rolled out a school(12 weeks) start date and an app(VIP only). Stay tuned
🏆 WEEKLY COMP #10: THE DIAGNOSTICIAN 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE Build a folder-based AI diagnostician that reads something broken and tells you WHY it's broken. Not how to fix it. Why it failed. This week's deliverable is one diagnostician folder that someone could drop into a Claude project and use to figure out why something in their world isn't working. 🎯PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick a failure you've actually seen happen. A few sparks to get you thinking: - 📉 Why a landing page isn't converting - 📧 Why cold emails to a specific buyer aren't getting replies - 📋 Why a product spec keeps getting pushed back by engineering - 📄 Why a resume isn't getting callbacks in a specific industry - 🚪 Why users drop off at one step of an onboarding flow - 💸 Why a pricing page isn't converting trials - 🎥 Why a YouTube video underperformed the channel average - 🤝 Why a sales deal stalled after the demo - 📱 Why an app's retention craters in week two The more specific, the better. "Diagnoses marketing problems" is too broad. "Diagnoses why cold emails to enterprise IT buyers get opened but never answered" is right. 🗂️THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your diagnostician is a folder with five things: - 📄 identity.md (who the diagnostician is, what they diagnose) - 📐 rules.md (how they diagnose: what they look at, how they separate cause from symptom) - 💬 examples.md (2-3 example diagnoses showing the reasoning) - 📚 reference/ (common failure modes, diagnostic frameworks, benchmarks) - 📖 README.md (how to use it, what to feed it) Drop the folder into a Claude project. Claude becomes the diagnostician. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK A diagnostician is NOT an editor. Last comp was The Editor. That one critiques craft. It looks at a draft and says "this part is weak, go fix it."
2 likes • 9d
camera-sees-it-ha-doesnt Cohort: Technical repo: https://github.com/gitbuell/camera-sees-it-ha-doesnt — Diagnoses one specific, maddening failure: your IP camera clearly detects motion, but the event never reaches Home Assistant. Feed it your camera model and a bridge log and it names the single cause killing the signal — an ONVIF subscription faulting inside an HTTP 200, a class label dropped by branch ordering, a dead event path masked by a redundant fallback — shows how it knows, and stops without prescribing a fix. It's for anyone running OEM/IoT cameras (XiongMai, Dahua, Hikvision) into Home Assistant through an ONVIF/ISAPI→MQTT bridge.
Writing MD.files, What Do You Use?
What does everyone use to create markdown files with? I use LibreWolf as my text software and it doesn't. I know you can hand create in Notepad but I know there has to be a better option. I noticed that GPT seems to balk sometimes. I have it output the language for review, and then have it generate the md file. Last time I did, it mentioned that it doesn't exactly copy the review copy, just uses a summary of it. That didn't make much sense. Suggestions please.
2 likes • Jun 21
Note++ and it goes great with meld for comparison.
1-10 of 28
Derrick Avent
4
81 points to level up
@derrick-avent-5541
Champipple

Active 1d ago
Joined May 15, 2026
Powered by