Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More
13 contributions to Clief Notes
Sunday is Audit Day [For Me]
Every Sunday I ask Fred (My AI): "Am I crazy?" Sometimes I do it before Sunday (if I feel "drift). Your ICMs will take care of you but you have to take care of your ICM too. Change it's oil, rotate the tires, make sure it's not crazy... You can check it out on Git if you'd like to ask your AI if you should use it: https://github.com/oathdriven/rymac-4r-icm-audit *I updated this earlier today for anyone who may have already grabbed this last Sunday* If you use it, all you have to do to kick it off is ask your AI "Am I crazy?" and it gets to rockin' for ya Any questions or comments?
Sunday is Audit Day [For Me]
1 like • 20h
Having a weekly routine or prompt just to audit context drift and retired rules is brilliant. It’s crazy how quickly stale tasks or outdated instructions sneak into loaded files when you’re building fast during the week. Checking out the repo now thanks for sharing the setup Ry!
Extremely confused
I really want to love this course, but every time I sit down to work through lessons, I don't know what to do. The instructions don't seem clear to me and the more I watch the more confused I get.
1 like • 1d
Getting stuck watching lesson after lesson without knowing what to click first is the easiest way to burn out on a course. What helped me was ignoring the whole backlog and just setting up one tiny exercise in Notion to follow along with a single 5-minute video. I track the to dos for each lesson in Flomen AI so I actually finish the practice before watching the next module. It still takes patience, but having one clear task stops the tabs from piling up.
One habit I'm trying to break is treating my AI chat history like some kind of knowledge base 😂
My setup now is pretty simple: claude.ai for working through problems, drive.google.com for files I actually want to keep, and floment.ai for the projects and tasks I'm actively executing. Models will change, prompts will change, probably half my current tools will change too. But having a clear place for knowledge vs actual work feels way more durable. Where does your useful AI output go after the chat is over?
0 likes • 6d
@Liam Rourke Mostly standard web chats! I use Projects occasionally if there’s a big pile of reference docs or a style guide, but for day-to-day problem-solving, it’s usually just regular conversations.
0 likes • 6d
@Liam Rourke That QA check on the handover file is a great tip, I hadn't thought about having it self-audit before spinning up the next chat.
Awesome Resources
Hey Clief Notes fam! 👋 I'm Amy Johnson and I'm happy to be here. 🙋 A little about me: I am a franchisor of a donut business. I have over 50 franchisees and am working on building AI systems for all of us to make business easier. 🎯 My current goal: Building an AI Franchise Kit Biggest Struggle right networking and finding people who can talk ICM with.
1 like • 8d
Rolling out standard playbooks across multiple operators gets messy fast if documentation lives in isolated silos. When creating repeatable operating systems, keeping structured notes and task tracking organized inside Floment AI helps operators follow the exact same rhythm without extra back and forth. Pairing shared notes with a quick Loom walk through has saved our team countless repetitive questions.
Show me what you're building 🧱
I don't want a progress percentage today. I want to know what's actually changing. If you've been working through Building Your Stack, what is one decision you've made because of it? - Maybe you added something. - Maybe you removed something. - Maybe you realized part of your current stack makes absolutely no sense. 😂 Whatever it is, post it below. What did Building Your Stack make you rethink? And if you've been flying through the lessons but skipping the quizzes or accountability posts... Go back. Those are there to make sure you can actually explain and apply what you're learning rather than just consuming it. Drop your biggest realization below. 👇 And keep going. New roadmap next Friday, September 25th.
0 likes • 15d
Simplifying the tool stack made a massive difference once I realized how much time was being lost context switching between separate apps. I stripped my setup down to VS Code for core building and Floment AI project cards to track active builds and progress updates. Getting rid of the extra middle layers kept the daily workflow focused on actual shipping instead of app management.
0 likes • 12d
@Lily White yeahh. It’s so tempting to build this elaborate dashboard or juggle five specialized tools, but you end up spending more time updating the system than doing the actual work. Keeping it low-friction makes it way easier to just sit down and build.
1-10 of 13
Tony Iverson
3
44 points to level up
@tony-iverson-7089
Building things online and trying to optimize my daily workflow. Here to learn from founders who are a few steps ahead.

Online now
Joined Jul 17, 2026
Powered by