Most people still use AI like a chatbot. Write a prompt. Get an answer. Rewrite the prompt. Repeat. Loop engineering changes that. Instead of manually reviewing every response, you create a workflow where AI evaluates its own output, follows predefined rules and continuously improves until it meets your standards. This approach isn't about replacing human judgment—it's about reducing repetitive work and building more reliable AI systems. In this guide, you'll learn how to: - Build your first review loop with Codex - Structure projects using AGENTS.md - Create repeatable AI review workflows - Automate quality checks for code and content - Develop systems that improve through iteration The most effective AI systems are not built from a single perfect prompt. They are built from simple, reliable loops that consistently solve one problem at a time. How do you see loop engineering changing the way we build with AI over the next few years? I'd love to hear your thoughts.

Many of today's fastest-growing AI roles focus on skills like communication, marketing, customer success, content creation, product strategy and technical support—not advanced coding. As AI adoption grows, companies are looking for people who can bridge the gap between technology and business. Which AI role interests you the most? Follow for more AI insights and practical resources.

It has been 10 days since I joined Clief Notes community and started Jake's coursework. It has been a massive step change in how I understand - and now use AI more effectively. A few days ago I joined into a paid subscription and the resources have proved to be very helpful in setting up my own folder structure. Before joining this community my use of AI was prompting the web user interface and copying the artefacts / outputs for my work. I had projects setup with various context files and instructions. I recently created my first website (in-progress) using Claude Code in VS Code and Jake's 'workflow-starter-code-project.md' template to create the folder structure. Most of the time has been spent in learning ICM, configuring the folder and file structure to route AI, and planning the geological database schema. Building the website was the easy bit! What has changed / unlocked in my use of AI: - spending more time planning and less time managing prompts and outputs - output has significantly increased with less prompts required to get the same job done I feel more "human" now and less like a "machine" in my use with AI since moving to the ICM method. The time being creative and planning is often away from the computer, where I'm spending time with family or doing the things I enjoy outdoors. I appreciate how Claude just "gets me" now without typing out an essay or giving me vague responses or hallucinations. If you are new here my advice is: - take your time to work through the foundation content - no rush, it takes time to learn and understand how to implement this knowledge into your work - start small and build for something specific - don't spend time creating a folder structure on what you think you will use - build for what you will use today, in 30 minutes. - play around and fail fast it won't be perfect to start with and that is OK :) Thank you to Jake - and everyone who has contributed to this community and built the resources that exist.

1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

Hi everyone, I'm posting this because I'm curious to hear your perspective on harness engineering within the ICM method. If you have any experience or opinions, please share :)