The Folder Structure That Makes AI Build Better Software

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: The Folder Structure That Makes AI Build Better Software
- URL: https://www.youtube.com/watch?v=RQckIBzOCsA
- Topic: Creative Automation
- My current learning frame: Use Folder Structure That Makes AI Build Better Software as a transcript-backed creative automation walkthrough: at 0:37, it frames what sits where. Get it right and regular AI does brilliant work session after session.
- Why this matters: New playlist item from AI Code That Works; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:37 / Evidence 1: "what sits where. Get it right and regular AI does brilliant work session after session. Get it wrong and the smartest model on earth guesses, drifts, and quietly wrecks your project while swearing everything is fine. So, stick..."
- 2:51 / Evidence 2: "system. At the root of your project sits one file. In Claude code, it's literally called claude.md. And it is the agent's front door. The first file it reads every session. And here's the rule almost everyone gets..."
- 4:29 / Evidence 3: "code, that's a folder called .claude. This is where the conventions live. Your build rules, your design system rules, the catalog of components you reuse so the AI stops reinventing a button that already exists. These are the..."
- 6:19 / Evidence 4: "starts building toward a target you already hit and moved past. Confidently steering you wrong because you never told it the plan was over. Stale docs are worse than no docs. With no docs, the AI asks. With..."
- 8:25 / Evidence 5: "to do what a folder and a text file do for free. The most effective setup I found is also the cheapest one. That's not a coincidence. It's the point. Don't vibe code your way around this by..."
- 11:03 / Evidence 6: "works from your rules and decisions without you spoon-feeding any of it. The structure does the remembering, so you go back to deciding what to build. And go look at your own project right now. If your AI..."
- 13:06 / Evidence 7: "time. That pack plus 15 more. Everyone a real piece of production stack I run every day. It's another 10 hours of deeper courses. It's the full resource repository. Every template, prompt, and tool. And it's weekly access..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A creative workflow board with critique criteria and review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "The Folder Structure That Makes AI Build Better Software", not a generic Creative Automation essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.