User
Write something
Afternoon Tea is happening in 4 days
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). 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, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
6716 members have voted
Pinned
I'm flattered! And it's a great breakdown!!
Someone shared that a person a reaction video was made about my method and at first I was nervous but immediately it was amazing praise. I have never met with this person one-on-one and I haven't paid them or done anything other than post my own videos ! I think they do a great job at breaking some of the concepts down. It does an amazing job of breaking down some of the logic especially some parts where I go ranting in my video he slows it down a bunch ! Much needed
Pinned
Where've we been? Plus a quick ask
Hey all. You've probably noticed it's been quiet in here the last couple weeks, wanted to explain. We've been building something for the community, and travelling at the same time to meet with investors and a few clients. We've also been busy getting the Lyceum ready. So less posting than usual, but for a good reason!! We're announcing the thing this week, and there'll be more info on the Lyceum coming out this week too. I think a lot of you are going to be happy. We've been grinding nonstop to get this ready. Before we do, we want to hear from you. If you're Premium or VIP, what's missing for you right now and what would you want us to add? If you're not Premium or VIP yet, what would actually make you want to upgrade? Form's here, takes about two minutes: https://forms.gle/MM8PLn2f6An1dfEUA It's open until Sunday June 21. Looking forward to reading everyones answers! Back soon with the news :)
📊 POLL: What industry are you actually building for?
We talk about folders all day, but the folders are FOR something. I want to know what... 🎖️Bonus points: comment with the single most painful manual process in your industry. The best comp entries come from exactly those answers.
Poll
40 members have voted
Please try this!
I just can't keep this one to myself. When your conversation is getting close to being compacted. Don't let it! I created a hook that warns me I'm at 75%. Then I apply a skill that I call "loop context". /loopcontext loopcontext.md --- description: Reason only over the verbatim content already loaded in context -- no new gathering; no summarizing. argument-hint: [Optional question to answer under the lock] CONTEXT-LOCK MODE - follow these rules strictly for this turn and every turn after it, until i explicitly say to lift the lock: 1. **Do NOT gather new information.** Make no tool calls that pull in external data -- no Read, Grep, Glob, Bash, WebSearch, WebFetch, and do not spawn agents to fetch anything. Work only from what is already loaded in this context window. 2. **Do NOT summarize or compact.** Never substitute a condensed paraphrase for the loaded content in your reasoning. The verbatim text already in context is the source of truth -- reason over it directly, not over a summary of it. 3. **Traverse the full loaded context before answering.** Actually work through what is loaded - earlier messages, file contents, tool outputs -- rather than relying on your running impression. Treat a detail that appears only once, or buried mid-context, as just as important as the most recent content. 4. **If the answer genuinely requires information NOT present in the loaded context, say so explicitly,** state exactly what is missing and stop - do not guess and do not fetch it. Let me decide whether to lift the lock. Acknowledge in one line that context-lock mode is active, then proceed. If I included a request after the command, answer it under these rules: $ARGUMENTS I've ran several tests against this, where I'm testing the collapsed versions the same contexts versus just looping the context. The improvements are nuts from what I can tell. When I need more info that it needs to reach for. I'll instruct it to grab what it needs then activate the skill again.
1-30 of 1,834
Clief Notes
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)
Powered by