User
Write something
Lyceum Webinar is happening in 2 hours
Pinned
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
🏆 WEEKLY COMP #9: THE EDITOR 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 💻 Code review editor for a specific language and level (junior TypeScript, senior Python) - 📊 Pitch deck editor for pre-seed founders - 🎨 Grant application editor for arts nonprofits - 📄 Resume editor for career switchers into tech - 📰 Op-ed editor for policy publications - 🎙️ Podcast script editor for interview shows - ⚖️ Legal brief editor for civil litigation - 📋 Product spec editor for early-stage PMs - 🎓 Academic paper editor for one specific field The more specific, the better. "Writing editor" is too broad. "Op-ed editor for tech policy publications targeting a policy audience" is right. 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your editor is a folder with five things: - 📄 identity.md (who the editor is, what work they review) - 📐 rules.md (how they critique) - 💬 examples.md (what good critique looks like) - 📚 reference/ (style guides, checklists, frameworks the editor uses) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the editor. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK An editor is NOT a rewriter. An editor doesn't do the work for you. An editor surfaces what's weak and pushes you to fix it. That distinction is the whole assignment this week. When someone hands the editor a draft, the editor shouldn't produce a "fixed" version. The editor should point at the three lines that don't work, explain why, and hand it back to the writer to solve. ✍️ Generic feedback like "consider strengthening your intro" is a fail. Specific feedback like "your intro assumes the reader already knows what a Series A is, but this pub is read by generalists, so lead with the stakes instead of the jargon" is what a real editor does.
Pinned
❗The Lyceum opens this Thursday: live webinar at 7 PM ET❗
Thursday, July 16 at 7:00 PM ET. Quick version for anyone who hasn't been following: The Lyceum is Eduba's 12-week AI certification program and the first credential we've ever issued. Over 3,000 people are on the waitlist and seats per cohort are limited. What we'll cover in the hour: 01 / The structure. 12 weeks, three sprints, nine live sessions, 18 hours of instruction, 12 instructors per cohort. 02 / The cohorts. Technical, Business, and Creator. Same core curriculum, weighted differently. We'll walk through how to pick yours. 03 / The competition. $250,000+ in prizes across the tiers and how your capstone feeds into it. 04 / The certification. What you have to do to earn it and what it actually certifies. 05 / The investment. What it costs, how payment works, and who should not enroll. Then live Q&A until the questions run out. One more thing. At the end of the session we're doing something for the people actually in the room. It's capped at a small number, it goes in the order people claim it, and we're not putting it in writing. Be there and stay to the end. The session is live only. No recording going out. Thursday · July 16 · 7:00 PM ET skool.com/live/XM7969jTG7L Come with the hard questions. Bring the skeptical ones too. That's what the hour is for.
Kimi K3 is out and damn it looks good
So the official launch video released about 2 hours ago, here's the link: https://youtu.be/bn0atstgavo?si=6SIAUKYAQBVIQ4N0 Also, the link to the article: https://www.kimi.com/blog/kimi-k3 First off, this has genuinely surprised me, a 3 Trillion parameter model that isn't open source, but it is open weight (Coming July 27th). The bench marks are insane, beating models like Fable and 5.6 Sol. A quick side note, do not trust bench marks blindly, start using personalized bench marks which relate to your field. If you're a web designer, get the models to go through your process and analyze the output of each model, different models have different advantages. The article has some insane use cases, mainly the 3d Open World, I don't know how many prompts or what framework they ran it with but it still looks quite good. Another interesting point, Kimi K3's article points out it's editing and visual effects capability, including motion graphics. Quite some potential there. The API pricing with a few comparisons of what I feel like are the top models are below: (Name: Input/Output per million tokens) Kimi K3: $3.00/$15.00 Fable: $10/$50 GPT 5.6 Sol: $5.00/$30.00 Caveats to each: Kimi K3: - Relatively more expensive for a Chinese model. - It doesn't always stay on task when there's a lot of context. - If you're switching to Kimi K3 mid session with a lot of context, it may get lost. - Quite slow by the only provider up right now, 28 tokens/second (About half the speed of fable and sol) Fable: - Usage limits finish faster than the tokens it generates. GPT: - Multiple cases of important files or entire code bases being deleted, back to 2025 we go!
0
0
🏆 COMP #8 RESULTS: THE WILDCARD 🏆
📦 AND SOMETHING NEW: EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 WHAT WE DID DIFFERENTLY THIS TIME Every submission was cloned at the exact commit that was public when we read it, and read file by file. The brief. The identity. The rules. The reference layer. The code. Where a repo made a claim we could check, we checked it. Arithmetic recomputed by hand. Sample photos opened and compared against the outputs that cited them. Files diffed. Self-tests traced. Thirty-two repos, read at the code/word level. And one lens over everything, because it's the lens this whole community is built on: does the build keep the human's judgment where it pays and put the deterministic work in code, where it can't hallucinate? 📦 THE FEEDBACK PACKAGE This is the new thing, and it's for everyone not just the podium. 📦 COMP #8: THE WILDCARD - The Vault Every entrant gets a markdown file. Three parts: 1️⃣ The read. What your build actually is, and the strongest thing in it cited to your own files. Rule numbers. Function names. Your own examples. 2️⃣ One push. The single change that most improves your build. Not a list. One. 3️⃣ An idea worth naming something original in YOUR build, credited to you, that the rest of the community is told to take from. Plus links to the builds your feedback points at. Nobody walks out of this comp empty-handed. Thirty-two builds, thirty-two named ideas. The roster alone is worth the download. 📍 The package + the full write-up (what held up, what was missed) live in the new Feedback module: 📦 COMP #8: THE WILDCARD - The Vault 📚 WHAT THE FIELD TAUGHT Three lines split thirty-two repos: ✅ Enforcement. A must in a markdown file is a request. A must in code is a constraint. (That line is from one of your repos. It's in the package. Go find whose.) ✅ Evidence. The builds that shipped receipts of a REAL run transcripts, dated logs, before-and-after fixes read differently every single time.
1-30 of 2,532
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