An excerpt from last week's VIP that I felt was important to share with everyone! How to get your first check/increase customers and bring in cash from the FOUNDATION of business.

I'm building a 48-second Christmas ad. Not in an app: the whole thing is an ICM folder, Claude Code reads it, and Higgsfield is just the tool on the end of the pipe that renders what the folder asks for. The ad ends on the house a girl wished for, and late in the build I changed that house: out with the generated storybook cottage, in with a real home we actually build. A late change to a foundational element usually means a rebuild. This one didn't, and three ICM principles are why. christmas-wish-short-ad/ ├── CLAUDE.md routing only, no content ├── CONTEXT.md the pipeline + status on one screen ├── _shared/ │ └── inherited.md pointers into the reference workspace. Nothing copied. ├── _templates/ └── stages/ ├── 01_brief/ script + which existing asset each beat reuses ├── 02_shotplan/ every shot bound to a specific still ├── 03_boards/ the house-swap candidates, grades, and decision ├── 04_scenes/ generate the gaps, then the motion pass └── 05_assembly/ edit, composite, watermark, submit Configure the factory, not the product. The reference material lives in its own workspace. The ad is one product coming off it, not a copy of it. One home per fact. The house is a single row in a single element registry. Every shot points at that row. Nothing holds a second copy that can drift. Every output is an edit surface. The candidates, the grades, and the decision itself are plain files sitting in an output folder. Anyone can open it and see where the build stands. The swap still cost me three shots to regenerate. The win isn't that changes are free. It's that I could price the change in about a minute, before committing, because the structure already knew which shots depend on the house. That's the part worth stealing. The generator is swappable. The structure is the thing you own. Let me know if there are any improvements...

A pad of scrap paper beside the keyboard has done more for my throughput than most of the tooling I changed this year. The minutes a model spends building are the minutes to spend deciding what happens after it lands. - The next sequence - the two or three work orders after this one, written while this one runs. - Notes on the output - what to keep and what to challenge, marked as you read rather than after. - Designs - page layouts, folder trees, flows. Faster to draw than to describe. The dead time in an agentic session is real. A job runs for a few minutes and there are three things you can do with that window: watch it, interrupt it, or think. Watching teaches you nothing and interrupting usually costs a rerun. Writing by hand does something a second chat window does not. The keyboard pulls you back into the work; paper keeps you above it, which is the seat you are supposed to be in while an agent is running. The reading half matters more than the planning half. Marking what to challenge as an output comes in, rather than reaching the end and reconstructing it, is the difference between a next instruction that corrects course and one that just says carry on. The bit I have not solved is getting any of it back into the system. Everything on that pad is orientation the workspace never sees. One of the synced writing tablets pointed at a folder would close that - handwriting arriving as context on the next prompt, and the notes logged as part of the record of how a build actually went. If anyone here has wired one up, I want to hear how. Genuinely think that is one of the more interesting unbuilt pieces sitting in plain sight...

Hey Clief Notes members! I'm John Martin and I'm excited to be here. 🙋 A little about me: AI & Emerging Tech Manager at Columbia University (AI literacy + institutional AI deployments), plus a solo AI implementation practice on the side. 🎯 My current goal: Building a one-person business around Claude Code, MCP, and real-time 3D (UE5 + Blender) — productized AI pipelines, no team required. 💪 What I'm currently building/working on: Claude Code MCP integrations with Unreal and Blender, a multi-tenant booking platform (MVP shipped), and two-agent Claude + Codex workflows. 🤔 My biggest struggle or question right now: Time. Full-time job, family, solo builds — my challenge is scoping everything to the fastest path to shipped, and marketing consistently while heads-down building.

This is interesting, and I need your help. What I've been doing recently is, when I'm brainstorming, I come up with some ideas, come up with a start of a plan, come up with what it should look like, and then all of a sudden Claude Code starts building it. I'd rather it stop and build an ICM structure first, IF one is warranted. So I put an instruction in CLAUDE.md. It watches what I'm brainstorming, asks whether this is worth an ICM structure, and offers to fire the icm-architect skill: > When Jeff describes a project, assignment, or body of work that fits the ICM > procedure, say so right away, don't wait to be asked, and offer to run the > icm-architect skill. The test is low-bar and affirmative: could this benefit from > a walkable production structure? If it might, flag it. Do not talk yourself out > of it because "it's just one deliverable." A single animation, essay, deck, or app > counts. When genuinely torn, flag it and let Jeff decline; under-firing is the > failure mode to avoid. Global. Every session, every project. Three separate hedges telling it not to chicken out. And now I'm not sure it belongs there at all. Is this even the system's job? There's a decent argument that knowing when to climb from chat to skill to folders is the human's call, and that an agent nagging "want me to build a workspace for this?" is exactly the kind of unhelpful helpfulness we're all trying to design out. Maybe the right answer is that I should have caught it, and the lesson is just that I didn't. Three things I'd like people to poke at: 1. Has anyone built a standing routing rule like this, and did it stay useful or did it turn into noise you learned to ignore? 2. My threshold is "anything past a trivial one-liner," which is deliberately low. Is that the right signal, or is size the wrong axis entirely? Handoff risk might matter more than size. Something I do once but three people touch needs a folder more than something I run weekly and nobody else ever sees.