User
Write something
Afternoon Tea is happening in 5 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
5534 members have voted
Pinned
I come asking for help! (NEW ROUND! VOTE ONCE A DAY PLS)
Because of the Amazing support you all gave for the first Round Wylder (my step daughter) made it into the second round! You can vote once a day and some days are 2x votes ! I would love love love if any of you support her going to work with some of the best animal rescues in the world to just cast at least one free vote if you can! You can vote here! Not Ai related so sorry for that ! Wylder | Junior Ranger
🏁 Foundations 4.3 Check-In
You just used Claude Desktop as a thinking partner instead of a vending machine. Vote below, then tell us in the comments: what was the problem, and what was the insight you walked away with?
Poll
209 members have voted
The model is the replaceable part
If switching LLM means rebuilding your stack, the LLM was never the asset. The thing you had to rebuild was. ———————————— The mistake I kept making I was building "Claude tools". Things that only worked when Claude was on the other end. The day I wanted the same capability in Codex or Kimi, I had to rewrite. Each port drifted. The version I built second was always slightly behind the first. The model isn't the centre of your stack. The contracts you give the model are. ———————————— The pattern that fixes it Three rules. All boring on purpose. 1. Markdown is the contract. A capability is a document the model reads, not a Python wrapper around an SDK. 2. Files are the memory. Shared markdown on disk at a stable path. Every harness reads the same files. 3. CLIs are the tools. Anything deterministic (search, similarity, transforms) is a shell command. Models shell out. No vendor SDK at the surface. No model-specific prompts. No proprietary format. Just files and shell. ———————————— What it buys The model becomes a knob, not a foundation. Hard reasoning task? Reach for the biggest model. Mechanical refactor? Cheapest fast one. Hundred-thousand-line transcript? Whichever has the longest context window today. Same capabilities every time. No port. No drift. The one rule that does the most work Build the interface, not the integration. SDKs are integrations. Markdown contracts, files, and CLIs are interfaces. When in doubt, lean interface. ———————————— Takeaway The model is the replaceable part. Your contracts are the asset. If your toolkit can't survive a model swap, you don't have a toolkit. You have a vendor relationship. ———————————— Full long-read with three diagrams (lock-in vs portable, the three-layer stack, the model-as-knob): → https://www.aris-space.com/documents/tools-and-plugins/the-model-is-the-replaceable-part //A<3
Where do you find your clients? 🔎💰
For those who do client work, where do you get your customers? Where did you get your first? I’m not necessarily in the position to go start a consultancy but if the day comes, I’m curious. Drop the answer below 👇
1-30 of 1,235
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by