Three months in this community and I kept losing things. Someone would post a tool in Show Your Work. I'd think "I'll come back to that." Then it was buried under 40 more posts and I couldn't find it again. @David Vogel and others have built some great workarounds to highlight posts and info, but I wanted to put together something that helps me find those tools I'll otherwise flag and forget. So I scanned both categories and built an index. 72 tools. 7 categories. Standalone HTML file: open it in any browser, no login, no server, no account. What it does: - Real-time search by name, author, or keyword - Filter by category (Memory, ICM, Writing, Design, Media, Workflow, External) - Every card links to the original post and the GitHub or site - "Leave Review" generates a formatted reply you paste into the original post - "Submit a Tool" generates a post template for Resources & Finds What's in it: Memory: PMM, Cortex, Session Memory Layer, Codebase Memory MCP, and a non-technical PMM folder template for people without a dev background. ICM: Brofessor, ICM-Builder, Foundations Tutor, CoworkOS, IBE Workflow, Shipyard, Creator Orchestrator Template, PAFA, and more. Writing: Critical Editor, Council of 5, LinkedIn Content Wizard. Design: tastecheck, Weirdness Engine, Open Design, art-direct, Shade_. Media: to-md, TypeWhisper, YouTube Extraction Pipeline, Pushing Talk_. Workflow: ARI-OS, Astrid, SkillOpt, Nightwatch, Porter, The Maintainer, Subscription Auditor, and more. External: Miessler's PAI, Hermes Agent, Zuki, Signal Harmonics, GiTeam, and others. GitHub (open for contributions): https://github.com/FiSimply/clief-notes-index The README has instructions for adding via PR or the Submit button. Anything I missed, drop it in the comments & I'll add it. If there's a better way to accomplish this inside the Skool site, please comment. My way is not "the way" and I'm always open to alternatives.

Working with the EU on anything AI/systems is a headache in itself, so many rules to follow without even realizing that your VPS has to be hosted in the EU. Crazy stuff. Short story time, I had a project with a Medium sized company in Sweden, we were building a Facebook prospecting system. Now the thing is that they wanted a feature (quick note: I had already built the system with GDPR in mind, using Hetzner and all) that involved scraping individual profiles, which isn't really allowed. Now the question is, with AI giving you a workaround for almost anything, how far would you go before your morals stepped in. For me it's simple, if it even comes close to crossing the line legally or morally, it's a big no. Huge shoutout to @Tiffany Coyle for educating me on GDPR!

Everybody else is cranking small builds out in 30 minutes flat. Simple cartoon builders. I figured I was just being thorough, baking a few extra skills into the process while I was at it. Heads down. Grinding. Quietly wondering why every single step felt like pulling teeth. Wondering what I was doing wrong for it to be missing everything almost every time. Then it clicked. I checked my VS Code and sure as the sky is blue, I’d been running a damn Haiku level the whole time. Building my framework. Writing all my Python scripts. The works. No wonder it was riddled with holes and took me forever to track them all down. Three solid days swinging at a problem that was never the problem. The thing I was actually trying to build? Probably half a day of work once the workflow’s set to the right level. Expensive lesson. Time spent. Won’t be forgetting this one anytime soon.

The way we build has been on my mind lately. Part of it was @Ruben Aguirre ’s post about memory and drift and the system getting away from him. Part of it was a conversation with @Curtis Hays. Curtis kindly gave me permission to share the following, which is all his: The frame is the one from the thread @Geoff Thilo started. Two layers everybody can see: where the work lives (the folders), and what the model can see when it acts (the context loading). There's a third nobody builds for — discipline. What keeps the first two true after the day you set them up. People conflate organizing files with keeping them true over time. They're not the same job. I keep an index of every client and which version of their brand doctrine is current. I wrote it once. Then a few weeks later I touched it once more for an unrelated change. That was it. Two edits in two months while the actual client work churned underneath it — new versions, new clients, a half-dozen files that moved. By today the index was just wrong. It froze on the day I wrote it and the world walked past it. Here's the part worth noticing. It didn't go stale because I got lazy. It went stale because nothing in the system owned keeping it current. No rule, no gate, no step that said "when a doctrine file changes, the index re-derives." I went looking — there was nothing. It was a hand-built snapshot with no maintenance contract attached. An artifact like that was always going to freeze. The only question was how fast. So that conversation from Curtis got me thinking. I build a lot slower than some people in here - and I’ve already tagged two of them in this post. Part of that is because I spend time worrying about what Curtis calls the discipline. I stop and think about the boring stuff when I build. How is it going to get maintained? Does the skill force it or suggest it? I run a fortnightly reflection for my personal system. For my work one, I run a weekly sweep *and* a fortnightly reflection. I think the discipline is important enough that I baked a version of this into a competition entry in here - adjusted from my own practice to suit use by someone who is not a builder and stop the system from disintegrating over time.

This is the system I'm proudest of, and it's deliberately worth nothing to anyone but me. I've been building it for about two and a half months. My goal? Free up time personally, and test and learn everything I was learning here so that I could be confident in building out things that are proper products at work (or, more accurately, architecting things for my team to build). So this system flies in the face of some of what we learn - it's not meant to have a product launch, it's meant to be so damn unique and customised that it holds no value to anyone other than me. Current outcomes (and I'm going to build again so this will improve): - ~63 hours per year freed up for me - ~ 104 hours per year freed up for my husband - ~$2400 per year saved in food costs (around $50 per week approximately) and reduced food wastage - A calmer family who are not stressed out about what needs to be done when for school - we've gone from a last minute scramble or forgotten gear about once every 2-3 weeks to one item that was a day late in the last two and a half months. (With the root cause of that miss fully addressed instantly in the system). - Three weekly runs in a row where I didn't have to change anything in the heaviest and most challenging workflow (the weekly planning workflow). I just reviewed and approved it to write. Every minute of build time has already been paid back with interest before counting the time freed up for my husband, and I'm only two and a half months in. In fact, the first thing I built paid back on the first run with me being an hour better off from that first run even when you factored in the build time. Here's how it's actually doing that: - Term-start — the first thing I built, and the one I love most. It takes a 7 day timetable screenshot and a CSV file exported from the school app and turns it into an ICS file I can upload into my calendar. Rather than manually creating it, it can apply the reasoning required over the root information and give me the output. It even has a second-pass logic built in for the edge case logic where days aren't in the CSV which usually happens for 1-3 days each term. It works flawlessly. It began as a series of saved prompts and was my first ICM pipeline once I found this community.