Everyone gets something wrong the first time. Vote below, then drop your mistake in the comments so others can learn from it.

Hi all. Quick background - The organisation I work for recently signed an agreement with Anthropic and last week we got access to their most recent models (Haiku, Sonnet and Opus). We’re predominantly a Microsoft house so have been using OpenAI this whole time and I have a Copilot licence. With everything I’ve learnt in this community, it’s been the biggest frustration not having access to tools that I can leverage to build ICM structure. I was trying to build my own if I’m honest. This week that changed as getting the Anthropic models also gives me access to the Copilot Cowork ‘Agent’ (frontier, and not just an agent 🤦). I now have something that can interact with my folder structure and today I completed testing of a workflow for creating proposals off the back of receiving an RFP - a process that usually takes 2-4 people a working week (5 days) of collaboration, research, meetings, etc, but took me just over 1 hour to have a fully branded working draft, off of the prompt “A new RFP has just come in - see attached”!!! (Screenshot for proof) We have a pretty rigorous process when we receive RFPs, so to be clear exactly what’s going on: 1. Validate the RFP against a number of criteria first to establish its something worth our time responding and bidding for. 2. Go through a research stage to gather information about the client, the industry, competitors (known or potential), case studies etc. 3. Analyse all research with additional context of our relationships and previous opportunities or projects if they exist. This additional data is all store in a CRM that has limited access to only senior people. Artefacts are created here with matrices of competitor comparison analysis, value wedges and our approach based on the case studies. 4. Map out our value proposition comparatively to potential competitors and develop the story we want to tell. (All this before we start building out the proposal and embed this information into it) 5. Build out the proposal. There is a template but it’s extensive and requires shaving down quite often. This is also done by junior members more often who are just pulling information in without understanding what it all means. 6. Check that branding guidelines are in place throughout and consistent. 7. First draft is now ready for senior review and changes

You just saw how the folder structure adapts to different use cases. Vote below, then drop your customized setup in the comments. What did you name your workspaces and why?

If you want to drop this in the Skool community and actually get the attention of the high-level engineers, you need to lead with a pattern interrupt. These guys see "How to prompt" posts all day—you need to tell them why their current workflow is about to hit a ceiling. Here is the exact post I would write for you: Headline: Vibe Coding is the new "Technical Debt." It’s time to talk about SDD. We’ve all seen the magic. You vibe with Claude or Cursor, you prompt your way into a working MVP in three hours, and it feels like we’ve conquered the world. But there’s a wall coming for all of us. Once your project hits 5,000+ lines of code or requires complex state management, "vibing" starts to fail. The AI begins to loop, it hallucinations your file structure, and you spend more time "fixing the fix" than building features. The elite 1% of AI Engineers are moving toward Spec-Driven Development (SDD). The SDD Framework (How the Pros are building now): Instead of jumping straight to the prompt, you insert a "Contract Phase" using two specific files in your root directory: 1. spec.md: The "Source of Truth." This isn't just a prompt; it’s a rigorous definition of every user journey and data model. 2. plan.md: The "Execution Guardrails." This tells the AI exactly how to implement the spec, defining the file structure and API contracts before it writes a single const. Why this is your new "Moat": In a world where everyone can "vibe code," the code itself is a commodity. Your value as an AI Engineer in 2026 isn't your ability to prompt—it’s your ability to Architect. • Determinism: SDD stops the AI from guessing. • Context Management: By referencing a central spec, you keep the "God Object" in the AI's head consistent. • Scale: This is how you move from "cool demo" to "enterprise-grade SaaS." Stop prompting. Start Architecting. Check out this InfoWorld breakdown on why this shift is happening: https://www.infoworld.com/article/4166817/vibe-coding-or-spec-driven-development-how-to-choose.html

I've always known computers, i have always felt more than comfortable inside my files and folders. When i saw what Jake was teaching, it was too good to be true. It almost felt like a matrix moment. Why did i think all of this was so complicated? How can one video completely explain the entire AI hallucination bubble that I have been stuck in since my life changed to a vibe coding addict? Either way, holy f*^&* s^*(!!!! This is a big deal for me, i have been so unorganized my whole life, now with the codex and claude apps, i just structured them to mirror whats in my folders, made the necessary md files in each, and i have not stopped being productive since. I used to be so scatter brained, but with this system, and the new codex and claude desktop apps allowing you to organize folder structures on the left panel, this was a match made in heaven with Jakes system. No dashboard, don't want one, i have been more productive in the morning by simply opening my app and looking at my folders, every conversation thats ongoing with full understanding of the project and what is needed every step of the way. I set up a system where i use the code word "pickup" or "handoff" Anytime i say handoff at the end of the night, the MD files already know that it triggers a process of writing to the memory files, doing a verification pass to make sure it was written succesfully, and if i am in an active app building project, it will commit and push to the github branch automatically. I can fully close the chat window with no worries of losing any progress, then in the morning, from any other app i want, any terminal window, any IDE, i just go back to that folder with my AI and say "pickup" it will wake up, not only get up to speed itself, but give me a summary of where we were and what we should do next. This solved the problem i had my whole life of forgetting my progress and leaving things undone. I haven't participated much in this community because I can't find time, but im finally finding time because I have done more work in 2 weeks than i have done all year.