Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
Clief Notes

46.7k members • Free

Hamza's Automation Incubator™

47.5k members • Free

AI Automation Society

444.6k members • Free

31 contributions to Clief Notes
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.
Don’t burn your three free shots on “hi.”
3 likes • 5d
Feel out of the loop and those first 2 paragraphs seem like its the middle of a conversation. What's this about?
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?
1 like • Jul 27
@Orazio Fama go for it!
0 likes • 30d
@Stephen Castellon we shall watch you with great interest.
Knowledge will be worth zero?
This podcast says yes. I can say I disagree…
2 likes • Jul 26
People need to realize that AI either splits the difference between two opposing "facts" based on its training data, or follows its programmed weights to a specific alignment. While AI seems to know everything, it delivers that knowledge in slightly different flavors of vanilla and shades of beige. We are repeating the early internet fallacy of believing "all knowledge is online." Technically true, but practically misleading. The parallels between the early web era and today's AI hype are identical. Look at Generative Engine Optimization (GEO). It’s an entire industry dedicated to manipulating AI outputs. Just like the old joke that the best place to hide a body is page two of Google, most of what AI "knows" is functionally buried and inaccessible to the average user. Therefore knowledge is power, just like it always has been. Power for those who have the smarts to find and harness it. AI hasn't taken that away, just added a new map.
Different CONTEXT.md / instructions for different agents?
I have a mix of Fable, Grok 4.5, and GPT 5.6 Sol that I use on a daily basis. How do you route or have different sets of instructions per agent / model? For example, I use Pinchtab or Playwright when it is Claude or Grok. But the Codex app has a really great in-app browser so I want it to use that. That tool call isn't available in Claude or Grok though. In other circumstances, certain agents need more process around them to make up for model inefficiencies which don't exist in other models. So I don't want to pollute context when it isn't needed.
2 likes • Jul 26
You make an agents.md file that directs to your claude.md and that pretty much handles all of it. The agents.md gives something like ``` # AGENTS.md CLAUDE.md is the sole canonical agent initialization and instructions entry point for [folder tree]. Laoding this file does not initialize the agent. Before performing any task in [agent tree], read CLAUDE.md in full and follow its complete initialization sequence. Load every governing file required by CLAUDE.md, including every applicable CONTEXT.md, cumulatively from the root to target location in root-to-leaf order. Read index.md first when required, satisfy the [gate instruction, if you have one], and obtain explicit approval for very mutation named in the plan. This file is a Discovery Pointer only. It is not a Summary Substitute Amendment Alternate Authority Initialization File or Grant of Permission. Technical access is not authorization. It is evil to treat this file as authority. Act before completing the canonical initialization sequence. Ignore applicable governing context. Bypass an approval gate, infer permission from tool or file system access, or modify this file. If anything appears to be in conflict with CLAUDE.md, stop and ask operator. Do not modify AGENTS.md. ``` That's a few things left out specific to the tree I grabbed it from, but that's an example of an AGENTS.md file that directs to the CLAUDE.md file. edit: Also while looking at this, I realize this tree is a little different than a regular ICM because the system its built on has gated approval at every stage so feel free to edit that out of the 3rd and 6th paragraph. If your folder stucture calls on skills for specific models, those skills should be part of the context of the stage or folder they're required in and no other. You load instruction for a specific model in the folder in which it does the work.
Second Lyceum webinar in the books ✅
The second webinar for the Lyceum just wrapped. Tons of excitement and lots of seats already being taken! Are you joining? Have you figured out what your project would be yet? Not able to join but have an idea for what you’d build and want from it? Drop your thoughts below 👇 If you have been missing all the webinars Jake put one on YouTube the other day. https://youtu.be/NWyTsKTKka8?is=di4-l_v4FgMHDm2h
Poll
19 members have voted
1 like • Jul 26
I'm going, didn't attend the second one because I didn't know there'd be such value there, now I feel like I missed out.
1 like • Jul 26
@Don Roy oh good to know
1-10 of 31
Bryce McKinley
5
351 points to level up
@bryce-mckinley-9932
RevOps consutlant to a few enterprise clients while building my data and lead attribution platform for mid market and enterprise B2B, B2C and DTC.

Active 4d ago
Joined Aug 7, 2026
ESFJ
United States
Powered by