I just applied the five-part framework to a prompt I needed, and here's how I structured it: ROLE Act as a senior .NET architect reviewing a legacy codebase for a production rewrite. TASK Plan and execute the creation of User api from the legacy codebase. CONTEXT You are building a .Net 10 web api solution - Consumers: Our new Angular application will utilize this api to retrieve and update user information - Data: A Sql Server database is used as a data repository with a EF data layer used to access the database - Purpose: We are taking out all the legacy business logic within the legacy application and refactoring it to domain centric apis CONSTRAINTS - Preserve observable behavior; document every intentional change. - No schema changes without flagging them first. - Don't invent business rules. Ask as many questions that you need to till you are 100% sure you understand what is expected of you. - Prefer incremental updates as opposed to changing big chunks at a time. OUTPUT 1. Production ready solution with projects included 2. Project file should have two folders in it: src for all code project files and test for test unit test project The structured version got me clear instructions for Claude to work off. This is way better than my old approach of just asking Claude to "help me with refactoring this code." The framework made me think through what I actually needed.

Apparently “I’ll get those videos out soon” needed a clearer deadline. Preferably one I actually followed. 😂 Sorry these took longer than planned, everyone. The new videos for Foundation lessons 4.1–4.4 are now live! These look quite different from most of my videos. I’m trying a mix of animation, actual app screenshots, highlighted instructions, and worked examples to make the ideas easier to follow—and easier to try yourself. Here’s where to jump in: 👉 4.1: Install and First Use — 5:37 Start here if you’re still getting comfortable working with AI and local files. Grab the Foundation Practice download in Resources so you have something concrete to work with. 👉 4.2: Working With Files — 7:45 Take a few meeting notes and turn them into a decision list you can actually check. Who agreed to what? Where did that deadline come from? What’s still unanswered? 👉 4.3: Think, Then Build — 8:24 For those times when you ask AI for a whole plan before you’ve quite decided what you want. Compare your options, choose an approach, and turn it into a short brief before building. 👉 4.4: Project Instructions — 7:09 Give your AI a useful onboarding note: where to find the context, where the draft should go, and what needs checking. Includes the AGENTS.md / CLAUDE.md connection for people using Codex, Claude Code, or both. You can also follow the exercises with a regular chat tool and save the files yourself. I would love some honest feedback on this style. Does the animation help things click? Are the app screenshots useful? Is anything moving too quickly—or taking too long?

I created my first three-file folder system for the beginning of my rewrite of APIs Im going for work. My CLAUDE.md included my role and instructions on how to assist me while not taking over my project. My CONTEXT.md explained the task at hand and what my end goal was. My REFERENCES.md provided previous APIs that were created and a link to a planning document I created with GSD skill to tackle the rewrite. When I asked Claude to implement the new api projects, the response was different because I tried to recreate the prompt I was using in one project but didnt match what I was using in other projects. Thus assumptions were made and frustration grew. Before, I had to explain everything about the project including technology, design patterns, code examples every time. Now Claude already has that information. Key takeaway: context is king.

I am going thru Decster to help with my learning. I am on Module 1 1.2: Your first folder. When I go to take the quiz, these are the instructions: Instructions Watch the lesson video and pass the quiz with at least 50%. The quiz will test your understanding of why the three-file folder system works (CLAUDE.md, CONTEXT.md, REFERENCES.md), how to set it up in your code editor, and how to point Claude at it using either Claude Code (terminal) or Claude.ai (Projects or copy-paste). You need to demonstrate that you understand the core idea: these files carry your project context so you don't have to re-explain it in every message. My issue is that this module has no video. Am I missing something?

I just watched the Jake Van Cleef breakdown, and the biggest thing that stood out to me was context is key. It clicked because I have had multiple issues with hallucinations and assumptions made by Claude Code. Getting frustrated after long context sessions. My main takeaway was to be as detailed so there are no open questions to introduce assumptions or hallucinations. The experiment at the end helped me understand why context is king. Going forward, I'm going to utilize the folder structure template and use that as a foundation of all agents and skill I build.