User
Write something
Afternoon Tea is happening in 33 hours
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
6805 members have voted
Pinned
Calling all friends, asking for your support if you can spare it โค๏ธ
My best friendโ€™s dad is currently going through cancer treatment and there is a go fund me to support his medical costs. Iโ€™m not expecting anyone to contribute life is costly enough but if you have it in your heart and are able to help it would be appreciated more than anything. Thanks in advance to anyone who takes the time to read this! https://www.gofundme.com/f/support-mikes-cancer-journey-594gk?attribution_id=sl:15012345-d96b-4d61-8d72-478b304a6fae&lang=en_US&ts=1781827434&utm_campaign=fp_sharesheet&utm_content=amp20_t1&utm_medium=customer&utm_source=facebook&fbclid=IwRlRTSASheIRleHRuA2FlbQIxMQBzcnRjBmFwcF9pZAo2NjI4NTY4Mzc5AAEewEgvL9AJQEZZj4hn-1GjsoRFFucAjFoNIwMfSrKK0H6msk7Hga8rGkqyWWg_aem_sJu0t4KDXFlHZ4Z_eAyFbA
Pinned
WEEK 7 COMPโš™๏ธ THE OPERATOR โ€” RESULTS
(and a small change to how we run these) Hello everyone!! ๐Ÿ‘‹ First, the honest bit. This one is landing later than Monday, and on purpose. Two things got us here. One, a lot more of you are submitting now. If I am going to really sit with every entry and give it a proper look, a weekend is not enough. This round I went through all of them, watched the videos, opened the repos, the full pass. That takes time and I would rather do it right than rush it. Two, I could feel a few of you running hot. Weekly is a sprint, and burnout was starting to creep in for some. So we are moving to bi-weekly. More room to build, more room to breathe, and the time for me to actually review the work the way it deserves. ๐ŸŽฅ Quick word on the videos. They were a step up this round. Some of the animated walkthroughs and live demos were a genuine pleasure to watch, and yes, I weigh them. A clean demo that shows the thing actually working makes a real difference. However I don't want that to ALWAYS be a requirement. Also you will notice the Heavy hitters that you usually see up here are not currently, some posted late and I decided to let the new entries and first timers also have a chance as well! But certainly, check the original post as every submission has something for you to learn from : ๐Ÿ’ฐ Competition 7 โž–โž–โž– ๐Ÿ› ๏ธ A FEW THAT STOOD OUT (in no order, and if you didn't make it, it doesn't mean yours wasn't great) The Pipeline Operator โ€” @Jayden Forshee Runs a whole sales pipeline. Paste a lead and it grades it, writes the outreach, and moves the card itself. The live board where you watch cards move on their own, sat right next to a normal chatbot, was one of the clearest ways anyone has shown what an operator actually is. https://github.com/griffainai/studio-pipeline-operator Board: https://pipeline-operator.vercel.app/board
Running an an LLM wiki for a team...
Trying to work out the best way to run the Karpathy like LLM wiki for a team, not just solo, and want to see how people are actually doing it. Solo is relatively simple: raw folder in, Claude builds a linked wiki out, plus an index and a log. No vector DB, just markdown. Where it gets interesting is a team, say five people in a sales operation all feeding and querying the same brain. How are you handling the shared vault? One person owning the ingest to keep the structure clean, or everyone in at once? Git repo, Obsidian Sync, something else? Keen to hear what's actually holding up in practice. Thanks
1
0
The hidden reason AI keeps organizing your files wrong ...
Most people think AI messes up because the prompt was unclear. But sometimes the prompt is fine. The problem is that your business language is unclear. One word can easily mean FIVE different things. โ€œClientโ€ could mean a person, a company, an account, a project, a payment record, or someone in your CRM. โ€œContentโ€ could mean an idea, a draft, a final post, a campaign asset, or a deliverable. AI will follow whatever meaning is implied in the moment. That is where things get messy. Duplicate files. Wrong folders. Confusing outputs. Systems that make sense once, then fall apart later. A simple way to prevent this is to create a TERMINOLOGY file. Think of it as the shared dictionary for how AI should understand your business. Inside it, define: - The words your business uses - What each word means - What each word does not mean - Which terms are approved - Which terms create confusion - Examples of the right and wrong usage This is especially useful before building SOPs, automations, dashboards, folders, workflows, or AI agents. Because once the language is clear, AI has a much better chance of organizing, writing, and reasoning the way your business actually works. What is one word in your business that AI keeps misunderstanding?
1-30 of 1,917
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