Hi friends. Last week was my first submission into the weekly comp. Although I had no illusions about winning (or even placing), I was excited to build and learn. I learned a lot about the build process, but would love to learn about what I could have done better. Since there's no feedback from the judges, I was wondering if anyone would be kind enough to look at my work, and give some constructive criticism. Your wisdom would be much appreciated! here's my submission: SHIPYARD is for the person who needs to learn AI but has no idea where to start. They've tinkered, hit walls, and stalled trying to figure it out alone. That was me until a few weeks ago. Then I stumbled upon the Clief Notes community. The knowledge here has unlocked something for me. But reading lessons and then trying to build on your own can still feel like fumbling in the dark. I'm sure a lot of you, like me, would love to have Jake sitting next to you — coaching you through every step. Shipyard is my v0 attempt at that. This tool grew out of the lessons taught in this very community — the same folder-structure and first-principles thinking that makes AI finally click. Shipyard is that coach. It takes someone from "I don't know how" - to proof, in their own hands, that they can build something real. Drop the folder into a Claude or Codex project and it becomes your coach. You pick one of four practice builds: File Organizer, Brain-Dump Planner, Notes, or Decision Helper. It walks you through making the tool as real files on your own computer, one step at a time. It teaches before it asks, pushes back when you're vague, and makes you write every line yourself. In about 20–30 minutes you walk out with a working AI tool that you built yourself, and actually understand. Landing Page: https://julianargus01.github.io/shipyard Repo: https://github.com/julianargus01/shipyard

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇺🇸 Quick note first. This post is going up Today because we took Memorial Day off yesterday. To keep things fair, you've got until Sunday May 31st at 12:00 PM EST to submit. Same week of build time, just shifted. ---- 📋 THE CHALLENGE Build a folder-based AI researcher for a specific topic or industry. You pick the domain. This week's deliverable is one researcher folder that someone could drop into a Claude project and use as their personal research partner for whatever domain you've built it for. ---- 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🏦 M&A activity in one industry (fintech, healthcare, defense) - ⚖️ Court cases in one area of law (employment, IP, immigration) - 🧬 Scientific research on one health condition or treatment - 🏘️ Real estate market dynamics in one city or asset class - 🥊 Competitive intelligence for one product category - 📜 Historical research on one period, place, or movement - 📚 Academic literature in one specific subfield - 📋 Regulatory developments in one sector - 📰 Journalism research on one beat (climate tech, AI policy, biotech funding) The more specific, the better. "Research assistant" is too broad. "M&A research analyst for early-stage fintech deals in the US and Europe" 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 researcher is a folder with five things: - 📄 identity.md (who the researcher is, what domain they cover) - 📐 rules.md (how they research) - 💬 examples.md (what good looks like) - 📚 reference/ (frameworks, source lists, key concepts) - 📖 README.md (how to use it)

Yet again making this SO hard to decide, I am bringing together a rubric just to be able to really break these down its getting so close. OVER 37 ENTRIES. Spent all day today looking at YouTube Videos, testing apps, reading through markdown files. Going to spotlight six (no particular order), then a few thoughts on where this is heading as well as the winner out of everyone. 🥊 @Ariel Ortiz , The Praeceptor Honest read: if Ariel had been premium last week, he was the winner and again this week easily can take home the prize but more importantly they are premium now! He went premium and somehow raised his own bar. Idea for a Native iOS app in Swift 6 , three YouTube videos including a 4:28 behind-the-build, voice mode pipeline, 17 operator extractions (Grove, Munger, Walsh, Aurelius, Naval, more). Hero copy reads "A room. Not an app." which was really a great hook, one of those opening lines that makes you very curious right off the rip. What I'd take from Ariel beyond this comp: he treats every brief like a product launch. Even the video stack alone is a walk towards the idea that distribution matters as much as tech now. 🔗 https://praeceptor-web.vercel.app 🔗 https://github.com/orteug/the-praeceptor 📹 https://youtu.be/Cfs1KAC2Ry0 🔥 @Ruby Sparks , The Gut Mechanic Ruby's a monster. Every week crushes it without a doubt. The landing pivots from consumer pain into a B2B sales pitch in one stat (the $530B-lost-to-employee-health number) and her voice across the entire page is sharper than what most paid brand consultants ship. She also created an ENTIRE skool community for it. Which is a win in its self. Twenty years of chronic illness in the founder story. IG, Skool, a 14-minute course, B2B framing layered into the consumer hook so the consumer side does discovery and the B2B side does monetization.

Hey everyone 👋 Bas here. I wanted to share something that's been a foundational tool in my toolkit, especially when I'm working with ICM (Interpretable Context Methodology). I had someone asked me about this in the community and it helps me, hope it can help you too. Full transparency: I built this. It's called Praxis Library 📚 (praxislibrary.com/learn/index.html), a free, open knowledge platform covering 177 AI communication frameworks and techniques with a 5,324-term glossary and 254 academically sourced citations. Why I'm sharing it here: 🤔 When I'm building with ICM, structuring context files, designing coaching systems, writing identity docs, or really whenever I am planning or interactive with AI, I find that understanding the fundamental architecture behind how AI processes input and generates output makes my work sharper. The examples are the vocabulary and mental models I bring to the table when I sit down to build. 🧠 A few examples of what's in there and how I use them: 👇 🌟 CO-STAR Framework breaks prompting into Context, Objective, Style, Tone, Audience, and Response. When I'm writing an identity.md or rules.md for an ICM project, I'm thinking through these same dimensions. CO-STAR gave me the language for what I was already doing intuitively, which made me more deliberate about it. 🏎️ RACE Framework is Role, Action, Context, Expected Output. Before I write a single line in a CLAUDE.md file, I'm running RACE in my head: what role is this system playing, what actions does it take, what context does it need, what should the output look like? It's a quick sanity check that catches gaps before they become problems. 🔗 Chain-of-Thought / Few-Shot / Zero-Shot Techniques help me design better examples.md files. When I write worked dialogues for an ICM project, I'm essentially building few-shot examples. Knowing the research behind why that works makes me more intentional about which examples I include and how I structure them.

💰 $500 CASH 💰 Win this and you've covered a year of Premium with $175 left over. 📋 THE CHALLENGE Build a folder-based AI coach for a specific domain. You pick the domain. This week's deliverable is one coach folder that someone could drop into a Claude project and use as their personal coach for whatever you've built it for. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎤 Public speaking coach for new managers giving their first big presentations - 💼 Salary negotiation coach for tech workers at Series A startups - 📞 Cold call coach for first-year SDRs in B2B software - 🎯 Interview prep coach for product manager roles - ✍️ Writing coach for one specific genre (sci-fi short stories, college essays, op-eds) - 🏋️ Fitness form coach for one movement (squat, deadlift, golf swing) - 🌍 Language learning coach for one use case (medical Spanish, business Mandarin) - ♟️ Chess coach for one specific opening or endgame pattern - ⚽ Youth athletics coach for one sport and age group The more specific, the better. "Life coach" is too broad. "Salary negotiation coach for tech workers at Series A startups" 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 the foundation of interpretable context methodology. Folders as architecture. Each file does one job well. Your coach is a folder with five things: - 📄 identity.md (who the coach is) - 📐 rules.md (how they coach) - 💬 examples.md (what good looks like) - 📚 reference/ (frameworks, drills, source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the coach. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK A coach is NOT a knowledge base. A coach gives feedback. Pushes back. Asks better questions. Holds people accountable.