What does everyone use to create markdown files with? I use LibreWolf as my text software and it doesn't. I know you can hand create in Notepad but I know there has to be a better option. I noticed that GPT seems to balk sometimes. I have it output the language for review, and then have it generate the md file. Last time I did, it mentioned that it doesn't exactly copy the review copy, just uses a summary of it. That didn't make much sense. Suggestions please.

I just completed my first successful real-world 3D print using an ICM-based production pipeline I built—and the part actually works. What makes this interesting is that, before starting this project, I did not even know how to create a 3D model or print file. I started by researching the process and having AI help me build a detailed brief for how a proper 3D-print development workflow should operate. Then I used that brief to create an ICM pipeline that could take an idea from initial concept through modeling, validation, testing, and final print preparation. My first run was a test case. It worked, but it exposed a major inefficiency. The pipeline was completing measurements, geometry validation, design refinement, and several other expensive steps before showing me a visual representation of the object. Once I finally saw the design, I would notice something I wanted to change and have to send the project backward through multiple stages. That meant repeating expensive work and burning a huge number of tokens. So I asked the pipeline to analyze and redesign itself. It restructured the process so that an early visual concept is now presented before the expensive engineering and validation work begins. I can review the object, suggest design changes, and approve the general direction before it spends tokens finalizing measurements, geometry, strength, and printability. That one workflow change produced a significant reduction in token usage. For the first real project, I needed a replacement pole cap for my trampoline. I took a picture of one of the remaining caps, described what I needed, and let the pipeline handle the rest. It: - Interpreted the reference image - Developed the specifications - Created the model - Presented an early visual for review - Incorporated my revisions - Ran geometry and measurement checks - Evaluated strength and printability - Prepared the final print file All I had to do was explain what I wanted, look at the visuals, request a few tweaks, and tell it to get the model ready to print.

🔍 Three things to notice. 👇 1️⃣ Numbered folders set the execution order, so 01- always runs before 02-. 2️⃣ Each stage carries its own CONTEXT.MD, references/, and output/. 3️⃣ The handoff between stages is dead simple. Stage 1's output/ is what stage 2 reads as input. ================== 📂 The folder structure workspace/ -------------------------------------------# the whole operation CLAUDE.md ------------------------------------------# L0: orientation, "where am I?" (always loaded) CONTEXT.md --------------------------------------- # L1: the map, "where do I go next?" stages/ ------------------------------------------------ # all the steps in order 01-research/ ---------------------------------------- # step 1: gather the source material CONTEXT.md ---------------------------------------# today's job description references/ ------------------------------------------# rules for this step output/ -------------------------------------------------# what this step produced 02-script/ -------------------------------------------- # step 2: turn research into a draft CONTEXT.md -------------------------------------- # today's job description references/ ----------------------------------------- # voice rules, examples output/ ----------------------------------------------- # the draft lives here 03-production/ ------------------------------------# step 3: ship the final artifact CONTEXT.md ------------------------------------- # today's job description references/ -----------------------------------------# design system, build conventions output/ ----------------------------------------------- # the finished product _config/ -----------------------------------------------# L3: brand, voice, design (configured during setup) shared/ ----------------------------------------------- # L3: assets every stage might use skills/ -------------------------------------------------- # L3: bundled skills the agent can call setup/ --------------------------------------------------# first-time configuration

@Derrick Avent left one line on my last post that stood out: “focus on security guardrails for your clients.” He was right. What I thought was a 30-minute fix turned into a full portfolio upgrade. It triggered a full audit and revisit of @Jake Van Clief article *ICM-Folder-Structure-as-Agentic-Architecture*. Five repos. Five domains. Same structural upgrade, domain-specific guardrails added to each. 8 commits. 86 files. 5,667 lines. One community comment triggered all of this. I went back and fixed it properly instead of patching the surface. Has anyone else been updating competition entries? Drop a comment or reach out directly if you want to dig into the architecture. And @Derrick Avent , genuinely appreciate the pointer. ----- *All five repos public on GitHub: github.com/orteug*

Hi Clief Notes Community! If you have not met me yet, my name is Bas and I am one of the members of our community! ⭐EDIT* Apparently there is a vote going on whether or not I should change my profile picture. https://www.skool.com/cliefnotes/petition-to-change-bas-profile-photo?p=abbdd137 Clief Notes is a very special place to me and I am always trying to bring us value so we can learn, grow and win together! 🤓💪🏆 So, I have already shared the Praxis Library a 255-page tribute to prompt engineering and AI literacy. After a recent post @Curtis Hays made about me, and after I wiped the tears from my eyes, I started to build something new, and I am building that something for us. Curtis Post You all joke that I'm a bot. 🤖 So I made one. Meet Bas 2.0, the curator of a new work in progress library at askbas.com. (Coming Soon page is up) I can't always be in the thread the second you get stuck, so I built a version of me that can be. Tell him what you're after and he'll pull it off the shelf for you, day or night. 📝NOTE: Not on the shelf yet? Bas 2.0 will open a search in the site and look up the ask with you, and he will send me a notification so we can look into what you wanted to see and add it to the pages of the library for others who could learn from the lesson. 📚 What's on the shelves: - 🌐A working library of AI Knowledge, ICM, context engineering, model tutorials, and multi-agent systems. - 🏫 Learning paths for wherever you are: a Beginner's Path, a Practitioner's Path, and an ICM Deep Dive. - 🤝 A hands-on how-to library, from Claude Code, Co-Work, and Design to ChatGPT, Goals, and Codex all the way through to Skills to building your own agents. - 📝 Lessons built to make this click, not just to fill a page.