One of my first goals in using all I’m learning here was to automate the monthly income statement for my (small) organic granola company. For many years my husband and I just winged much of the accounting and financial details of our business. Waiting till tax time or the end of the year to cobble together what we needed. The reports from Shopify and square worked fine. But over the past few years, we’ve put more emphasis on growing the business and i honestly hate being in the dark. My husband is ok being a little loosey-goosey - good thing we aren’t financially dependent on this! It’s still very much a side hustle but it’s our brand and we take pride in the quality and integrity of our product and love our customers. So, on to the win… Today, I did it! I set up my folders, write my .md files. Tested, iterated and eventually nailed it. All I have to do is export my revenue, my expenses and fill in a few other details regarding events we do and presto. 4 steps, pausing along the way to reconcile any flags and finally landing at a clear picture of all the numbers of our business! Plus more regarding events we do, fees and other things we want to have to make future decisions. I’m excited to run all my stages for May. This made so much click for me. This might be basic but a huge win for me!

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.