@Joseph Fioramonti's report is finished! 467 of you placed 4,683 dots on Coca-Cola images, and the results are sharper than anyone expected. You can read the full thing here: Semiotic Analysis Report — Coca-Cola Visual Craving Study 📊 What it found: People want to see the drink. The cold liquid, the condensation, the ice, a real person taking a sip. They reject almost everything else Coca-Cola spends money on. Mascots, illustrations, logo art, campaigns. All of it landed in the resistance pile. That gap between what brands invest in and what people actually respond to is the whole point of what Joe is building. 🌌 He just opened his own Skool!! and its free to join! If you want to learn how Constellations works, what it measures, and how he's using it with real clients, this is where it lives now: 👉 https://www.skool.com/constellations-2153/about Worth a look if you care about the gap between what people say they want and what actually moves them, he is also a brilliant mind when it comes to branding and abstract data. Worth the join. If anyone has Skools they are making that think fit with this community message @Aaron Quiroz about Collaborating with us here! Clief notes isn't just about me! Its about you all too! Thankyou to everyone who commented on the first post ! @Aaron Quiroz @Shawn Pachet @Chris Hall @Justin Smith @Qayyum Khan @Alexander The Greatest @Graham Moore@Jacob Silver @Lucas Flint @Temnii Gray @Elizabeth Brooks @Lies Van den Steen @Kevin Stokes @Luis Arias @Mark Gubuan @Alex Bermudez @Ralph Miller @Richard Chover @Levon Petrosyan @P Patel @Carlos Santos @Sagar Bodhe @Alistair Mckenzie @Bryan Palmer @Ben Bruce @Roc Lee @Mark Benjamin @Brody Billings @Felix Weinzinger @Hayden Lee @Jannetje van Leeuwen @Charles Martin @Keenan Abrantes @Robertas Garalis @Eli Sayers @Arjen Stet @Mike Dixon @Paul Kouwen @Yan Costa @Pedro Costa @Adam Hollywood @Chip Wilson @Kevin Carrasco @Eduardo Salgado @Jerome Anasco

I am doing things I never thought I was capable of doing thanks to Jake ( and everyone else here). I'm a 60 year old grandma designing an app that has the potential to help a lot of people in times of grief. I'm vibe-coding - two words I didn't even understand a few months ago. I saw a pain point, identified what was needed and then started designing it. Me. Nana.

I'm drafting a very old sci-fi novel of mine with Claude Code. Four scenes in. More excited about a creative project than I've been in years — and the reason isn't the speed. It's that the workspace is built to refuse. Setup: a folder called `writing-room`. Eight stages, from premise to compilation, each one a markdown directory the AI loads only when it's relevant. Compass, world, characters, structure, voice, writing, revision, compilation. The first rule, hardcoded in `CLAUDE.md`: > Before generating prose, always load `voz.md` and `padroes-prosa.md`. Without these two, refuse the writing task and ask the author to do Stage 05 first. Translation: the AI cannot draft a scene until I've locked in the voice. And `voz.md` was reverse-engineered from scenes I wrote by hand. The voice is mine. The AI only gets to extend it. There's also a file called `padroes-prosa.md` — 9 anti-AI-slope techniques. Verbalized sampling. Fragmentation. Character voice. Rare vocabulary. Every generated scene must apply at least 3, and the reviser uses the same file as a checklist. What this changes in practice: - I don't fight AI prose. I gate it. - Each stage loads minimum context. The AI doesn't drown in 200k tokens of worldbuilding to draft one scene. - After every scene, a `cronista` skill updates a canon file. Continuity stays cheap. - I'm the bottleneck on voice. I'm fine with that. The transferable bit, if you build with AI: The most useful thing your workflow can do is sometimes say no. Refusing to act without the right inputs forces you to produce those inputs — and that's where your taste enters the system. Without that gate, the AI averages you out. Toward the median sentence. The median plot beat. The median version of you. A friend of mine said that "in order to have a second brain, you need to have a primary working brain". I laughed: true enough. I wanted to build the gate first. Then let it write. And I'm loving it.

I feel the FOMO when I dig into posts from different forums and come across something buried a few pages deep from a week or more ago which was the answer I needed earlier. I never used Skool.com prior-to Clief Notes. Is there a way to track conversations - list 'hot topics' regardless of forum... maybe a newsletter format (1x/week) which highlights discussion topics which are relevant? Short of building a bot or agent to run through the site for topics of interest (I considered it, but didn't want to burn the tokens), I feel there's a better way but frankly don't have the brain bandwidth to attack the issue at the moment - so I ask the great groupmind of awesome, how could we do this better?

There have been some good questions in my previous posts about my agents, so I want to clear up a few things. I call them agents because it helps me think and stay organized. But strip the jargon and here's what's actually happening: a folder with the right files in it tells an AI who it is, what it does, and what good looks like. Unix figured this out a long time ago. I remember working on mainframes in my early 20s. Files in folders. It wasn't powerful because it was complex. It was powerful because it wasn't. Unix came out in 1969; I was using it from 1998 to 2002. The "writing room" is a folder. Cash lives in it. His instructions, his guardrails, his examples, his voice reference — all files. The AI reads the folder and knows how to behave. The room gives it context. The files give it structure. I have 15 of these rooms. Duke orchestrates between them. The naming isn't the point. The structure is. Here's the part most people miss: almost every agent in my system has a human counterpart. A real expert whose domain knowledge shaped the instructions — and who can tell me when the agent gets it wrong. Cash's counterpart knows copywriting. Trace's counterpart knows data. That feedback loop is how the system actually improves. You're not building AI. You're building infrastructure. Build the foundation. Build the structure. The agents are just what you call it when the rooms start working together. My lesson: don't copy me, don't copy Jake, we all learn from each other, and then you make it your own. Stick to the fundamentals. Watch Jake's videos; it will rewire your brain and change how you think about AI. There are no shortcuts. You have to build a foundation first. Links to referenced posts: https://www.skool.com/quantum-quill-lyceum-1116/visualized-my-agent-team https://www.skool.com/quantum-quill-lyceum-1116/the-folder-system-became-my-agency