Pinned
👑
Jul 1 •
Welcome to Clief Notes. Here's where to start.
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?
Pinned
👑
6d •
🏆 WEEKLY COMP #11: THE CARTOGRAPHER 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ ($4,750 Seat) Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE This is a weird one, and you may feel lost at first. But it's up to you to make a map for those who come after and if there is no map, you must get lost to make one. Build a folder-based cartographer that can walk a body of work and leave a map a later reader can wander and show what that map is. The later reader is often an AI. Sometimes it is a new person. Same map. Same job. Not why it failed. Not how to fix it. Not a tour of how the week goes. What the nouns are. How they move. What else moves if you touch one. What is live, what is leftover, and what is a ghost with a name and no wiring. This week's deliverable is one cartographer folder someone can drop into a Claude project, point at a real body of work, and get back a map a cold reader can enter without reading the whole thing. 🎯 PICK YOUR TERRITORY Pick a body of work you have actually been inside. Something a new person or a cold model would get lost in. Something someone will change, not something you will only describe. A few sparks: 💻 A repo you own. Even a small one. The map is for the next developer, or the next session, that has never seen it. 📂 A client delivery folder a VA or a contractor has to inherit next month. 🧩 A Make, GHL, or n8n pack someone else will edit without you on the call. 📒 An Obsidian or Notion vault a collaborator has to add to without breaking the spine. 🧾 The live records behind how a job gets quoted, approved, and invoiced in your shop. The files. The objects. Not the story of a bad month. 🎓 A course or L&D library someone will update after you. 🏭 The asset and work-order objects in a plant system you actually touch. The more specific, the better. Maps how our business works is too broad. Maps the five objects a new hire has to understand before they touch the invoicing folder is right. 🧠 WHAT YOU ARE ACTUALLY LEARNING ICM has six forms. You have been living in the first ones. Pipeline. Coach. Editor. Diagnostician.
Pinned
8h •
Don’t burn your three free shots on “hi.”
The feed is a terrible index. Clief Notes AI is the librarian for it — not a second Claude, not a folder-builder, not a replacement for a Check-In. Free is three prompts. Total. DMs and the sidebar both count. After that you’re back in the classroom, which is still where the work lives. I wrote the map so you don’t spend shot one on “what can you do?” What’s in it - What this agent is (and what it will never do) - Chromium install, Student portal, same email as Skool - Three Getting Started shots and three Foundation shots you can paste - How to talk to it with the five-part prompt so a sloppy ask isn’t 33% of your budget Do this now 1. Classroom → Getting Started → watch Navigating The Course (2:51) 2. Open How to Access your Clief Notes Agent & Roadmap and install 3. Read the guide: Comprehensive Guide to Clief Notes AI https://www.skool.com/cliefnotes/classroom/c7f102c7?md=144082eaf875446eba04fa1db90fcc90 4. One DM. Then open Foundation 1.1. Check the box. The agent is a map. Your folder is the architecture. If the agent writes the system, you didn’t learn the system. Paste this if you only have one shot left: I just joined as [beginner / daily AI user / developer]. Give me the three-step start, the first Foundation lesson title, and what “done” looks like. Do not invent a custom curriculum. If three shots already feel tight, that’s the product working. Foundation stays free. Paid keeps the librarian on.
2m •
About Me
Hey Clief Notes fam! 👋 I'm Alejandro and I'm happy to be here. 🙋 A little about me: I´m an Industrial Engineer, worked in Engineering and Automation sales, O&G Industry, now e-Commerce in the last 5 years. 🎯 My current goal: To understand better the basics, know the most important functions and build better apps with AI as a tool, not as an all-doer. 💪 What I'm currently building/working on: I´m vibe-coding a bunch of web applications for personal use, and tried a couple of tools, now I´m mainly focusing on building with structures, and using Visual Studio Code + Codex I´m making Personal-Use projects for my One-Guy-Company, like: - Sales OS System - Personalized Marketing System - A website for our Gaming-Gang, including weekly updated unique stats (Check it out and feedback here please https://dota-noob-pro.vercel.app/) 🤔 My biggest struggle or question right now: My biggest struggle is the lack of patience. I´m taking it one step at a time, and the "Clief Notes" Roadmap helps me a lot! Let's get it! 🚀
0
0
3d •
What do you do when waiting for prompts to come back?
A pad of scrap paper beside the keyboard has done more for my throughput than most of the tooling I changed this year. The minutes a model spends building are the minutes to spend deciding what happens after it lands. - The next sequence - the two or three work orders after this one, written while this one runs. - Notes on the output - what to keep and what to challenge, marked as you read rather than after. - Designs - page layouts, folder trees, flows. Faster to draw than to describe. The dead time in an agentic session is real. A job runs for a few minutes and there are three things you can do with that window: watch it, interrupt it, or think. Watching teaches you nothing and interrupting usually costs a rerun. Writing by hand does something a second chat window does not. The keyboard pulls you back into the work; paper keeps you above it, which is the seat you are supposed to be in while an agent is running. The reading half matters more than the planning half. Marking what to challenge as an output comes in, rather than reaching the end and reconstructing it, is the difference between a next instruction that corrects course and one that just says carry on. The bit I have not solved is getting any of it back into the system. Everything on that pad is orientation the workspace never sees. One of the synced writing tablets pointed at a folder would close that - handwriting arriving as context on the next prompt, and the notes logged as part of the record of how a build actually went. If anyone here has wired one up, I want to hear how. Genuinely think that is one of the more interesting unbuilt pieces sitting in plain sight...
1-30 of 3,261
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+760
2
+662
3
+536
4
+507
5
+430
Powered by