Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
212 contributions to Clief Notes
As A Small Business Owner, It Took 5 Months For ICM To "Click"
After 5 months of being in this community, I finally caught the ICM flu... I didn't catch it the first month--we were just having a good time back then. I didn't catch it the second month, either. Those were the "lego" days, and still long before it would really click. I didn't even catch it when I started a second company 6 weeks ago, that I built after being inspired right here in this community. For 5 months, I was vibe coding. Up late, up early, like a middle schooler with a new video game, like the internet just became a thing for the first time... I thought that was the thick of it. No. Oh no.. No, no, no, no, no, no. There are levels, boys, there are levels... I caught the ICM flu once I made a widget that an actual client used. And then it finally clicked. Software. Agents. Human. You can just build a whole foundation for any company using this method. Which, sure, yes, we know that. But, realizing that once you got it... once you've built that first widget, that first workflow tied to a piece of software you coded and an agent you made, you realize... that's the whole thing. Do it once, do it a thousand times. Recycle, reuse. We're all software developers now, baby! About 2 weeks after it finally clicked, I joined the Lyceum because I understood the value of this finally. It does not matter what you plan to do--these skills transfer to ALL SORTS of things. Software, Agents, Human... just apply it to.... anything! As a side note, I have already received value after the first Lyceum session. I finally can see how I can transform my little house cleaning company into a mega machine and create the dream vision I have for this company. FOR ANYONE THAT SAW MY ANNOUNCEMENT ABOUT STARTING A COMPANY... This is going to sound nuts, I know, but Im shutting down the company I just made despite the fact that it's working. I can now see that the greatest play, and most value I can create, is going to come from the company that I have so much experience in already, and not the one that I have limited experience with. My judgements and tastes are strong where I've spent a ton of time already. Really, I have 3 lanes I've spent the majority of my life in, and I've decided I need to see those through at this point because I have way too much specialized knowledge to not do something with it. *And that's the secret sauce.*
5 likes • 4d
@Ruby Sparks cleaning is a killer niche for automation done right. Solid choice. [FOCUS]
Getting AI to nail voice
I'm struggling to get AI to nail my voice and the voice of my clients (getting AI to write in my and my clients' tone/style for IP/positioning work/website, content, etc.). I'm wondering if anyone has any tips. There's so much out there and I'm getting a bit overwhelmed trying to figure out where to start. Would love if anyone could point me in a specific direction. As context, I am an IP advisor and architect bodies of work for my client. I can do it intuitively on my own (not an official copywriter) , but it takes FOREVER, and I know AI can do it faster, but I just keep going in loops when I try to nail mine or client's voices. I also know that spending this much time on nailing someone's voice in their content is NOT the best use of my time. Would love any tips or leads.
1 like • 5d
@Mary Julia Cordero there are multiple conversations on this if you search “voice” in the community. @Carla Bosteder built a few templates and docs as well.
Room for improvement?
I've been building with Claude Chat (I call Claude) and Claude Code (I call CC) everyday. I've been providing trade knowledge and design decisions with Claude and just copying and pasting over to CC to build it, then I test in browser, take back any additions, critiques, alterations, etc. to Claude and we revise. Rinse and repeat. I've thrown a few ideas at Claude to propose additional work that can be done while I'm not available that we could use CoWork (I call CW) to build. So far it's only been prototypes of what the future model would look like on a grander scale, but nothing has gotten that far yet. My process with Claude and CC feels like it can drag on sometimes... I want to build this thing properly right from the start, so I've come to terms with the speed of it all, but I thought I'd check in with the masters and see if you can think of any holes or gaps I can fill. We'll start with a diagnosis of whatever it is we're going to add or improve to see what kinds of other things might be affected by it's addition. Then we write a spec that goes into our CONTEXT bible. Then we do a build prompt that I hand to CC, who then builds it. Now we've also built a harness for the whole thing, so before each build we also add in a layer of building on to the harness, which comes with it's own checks, both surgical checks and full run sweeps. A full run is starting to take over an hour to get through now, so needless to say some of the progress that I made early on before it got this big felt a lot better than the speed that the whole project is moving at now. After both harness and build have happened I'll do a screen test depending on what was changed. We'll commit after a full green pass, and then move on to the next step up the mountain of steps that this has shaped out to be. Without having to go into too much detail about what the project is about (I've been working full time and just trying to grind this out on evenings for a few hours a night and weekends where I spend usually >12h trying to get through this thing) what do you guys think might make this process run a little more smoothly?
0 likes • 6d
@Tom Clavel what are you trying to build? have you gone through all of the foundation lessons? Honestly, $20 on Codex to analyze and review your plans will save you a TON of time and rework. Claude is not my favorite for architecture and development. It's great for UI/UX, web design etc.
0 likes • 5d
@Tom Clavel now that you’ve described the product, I think the drag makes more sense. Codex/ChatGpt works like Claude, you download the desktop app and chat with it. I find it to be more focused and deterministic, especially for development. You’re building a trade-specific material calculator connected to client and project cards moving through a pipeline. The dvelopment harness has gradually become a second product that needs its own features, checks, and maintenance. I’d preserve the current folder as a reference, open a fresh conversation, and define the smallest working version before carrying any more architecture forward. These are the questions I’d answer first: - Who is the first real operator? - What is the first material calculation they need? - What real completed jobs can prove the calculation is correct? - What stages does a project actually move through? - What information is required before moving to each stage? - What would make the first version useful even if nothing else gets built? Then I’d start a clean repo with something like: trade-tool/ ├── AGENTS.md ├── CONTEXT.md ├── docs/ │ ├── product-spec.md │ ├── domain-model.md │ ├── decisions/ │ └── sources/ ├── work/ │ ├── active.md │ └── handoff.md ├── stages/ ├── app/ └── tests/ ├── calculation-fixtures/ └── critical-workflows/ The calculation fixtures are the important part. Put in real trade inputs with expected outputs reviewed by someone who knows the work. Those tests prtect the product. Harness tests only need to run when the harness itself changes. A local app with SQLite makes sense once clients, projects, calculations, and pipeline stages need to survive restarts and relate to each other. I’d wait on server infrastructure and authentication until a second operator needs the same live data from another device, concurrent access, separate permissions, or an audit trail. For the fresh, new Claude conversation, I’d start with: --- Read my existing project as reference only. Do not modify it or write code yet. Help me perform a clean-slate analysis and new plan.
New here: how do you hand off an AI workflow so it works without you?
Hey, I’m Eddy. Product and tool design engineer at an injection molding company in the Allgäu, Germany — automotive components, mostly CATIA V5. Right now I’m turning raw meeting recordings into a real company knowledge base before a colleague retires, and building a tool-agnostic AI workspace system around it. Two years of daily AI use. Clief’s videos pushed me from Cowork into Claude Code, and that opened a lot of doors. My question: how do I hand this off so it works without me?
2 likes • 6d
@Edmund Veser Welcome to the team, Eddy! I'm going to second Leo here, with a little more architecture. That’s a real handoff problem, especially when the source knowledge is leaving with the colleague. I’d define the workflow around its inputs, expected output, owner, failure conditions, and verification, then keep the Claude or CATIA-specific steps in a replaceable layer. Keep recordings and source material separate from maintained procedures, decisions, and current knowledge so the transcripts do not quietly become the process. Small, composable and reusable files are best. Names don't matter, routing is key. Example architecture: company-os/ ├── AGENTS.md / CLAUDE.md │ # How an agent starts, what it may load, and what it may change │ ├── CONTEXT.md │ # Purpose, accountable owner, boundaries, and routes │ ├── governance/ │ ├── authority.md │ ├── evidence.md │ ├── effects.md │ ├── handling.md │ └── change.md │ ├── memory/ │ ├── sources/ │ │ ├── recordings/ │ │ ├── interviews/ │ │ └── documents/ │ ├── decisions/ │ ├── knowledge/ │ ├── questions/ │ └── index.md │ ├── projects/ │ ├── plans/ │ ├── work/ │ └── handoffs/ │ └── operations/ └── example-workflow/ ├── CONTEXT.md ├── procedure.md ├── checklist.md ├── examples/ ├── adapters/ │ ├── claude-code.md │ └── catia.md └── acceptance-test.md Then give a colleague one normal task, the workspace, and no help from you while they run it end to end. Every place they have to ask what you meant is part of the workspace that still needs tightening.
LifeOS
I have started using Daniel Miessler's LifeOS; and found it to be very much aligned with the ICM methodology. But the system got so big and complex I find myself kind of lost. Does anyone here uses it? so we can talk about it?
0 likes • 6d
@Paulo Bernardy I looked through it, and there are some very smart ideas in there, but I personally wouldn’t adopt the system. No offense, ICM is much more streamlined and intentional - LifeOS seems like a tangled ball of Claude trying to patch issues it never should have created in the first place. It bundles memory, identity, goals, project tracking, dashboards, hooks, agents, skills, voice, security, and self-improvement before most people have proved they need that much machinery. There is also a lot of previous iteration language, with outdated or superseded explanations that will only confuse Claude (and the user). A lot of the complexity feels downstream of early assumptions about how much scaffolding Claude needed, and those assumptions gradually became architecture, mixed with Daniels personal opinions that don't belong in your own OS. I’d step back and ask what job you originally wanted LifeOS to do for you. If the goal is better contnuity, start with one current-state file, one ideal-state file, a small decision log, and a regular review. Add another layer only after a real failure shows that the simpler method cannot handle it. What would LifeOS need to do for you three months from now to earn the maintenance it creates?
1-10 of 212
Aaron Kruger
6
1,131 points to level up
@aaron-kruger-1837
tokenmaxxing

Online now
Joined Jul 5, 2026
Powered by