User
Write something
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
4169 members have voted
Pinned
Jake didn't do me any favors! Please Help🙏
Quick note about Skool’s bot protection: If your comment is just a few short words, you’re better off hitting the like button instead. What you probably don’t know is that the admins are getting absolutely blasted with anti-bot warnings — and Jake didn’t do me any favors by blowing up my notifications. We’re growing extremely fast (25,855+ and climbing), so we’ve got a massive target on our backs. Short, low-effort comments are triggering the system hard right now.Help us keep this community high-quality: Only comment when you have real value to add — sharp insights, innovative ideas, or meaningful experiences. Likes 👍 are there for quick appreciation. Save the comments for stuff that actually moves the conversation forward. Do your part. Let’s protect the space we’re building together. Thanks, legends. *** @Jake Van Clief has not approved this message, he's swamped ***
Pinned
🏆 Weekly Comp #2: The Artifact Sprint 🏆
💰 Week 1 winner @Ian Barriopedro took home $200 cash. 🎟️ This week the prize gets bigger. ✨ Winner gets a FREE seat in The Lyceum. ✨ https://www.skool.com/quantum-quill-lyceum-1116/12-weeks-real-projects-250k-in-prizes-lets-talk?p=e850567b 🎯 Pick your cohort: Technical, Business, or Creator. Your call. 📋 THE CHALLENGE: "The Returning Client" You just got hired again. Different client this time. Meet Marcus. 👋 📎 Download the full client brief attached to this post. 🛠️ YOUR DELIVERABLE An interactive artifact built in Claude that does what Marcus asked for. ✍️ Plus a 100 word writeup covering: - 👤 Who it's for - ⚙️ What it does - 🎨 One design choice you made and why 📐 THE RULES ✅ It has to work ✅ It has to sound like Marcus, not a bank ✅ The writeup matters ⚖️ Judging: Myself, Jake, and the mods. 🎟️ Who can enter: Premium and VIP members only. Free members, this is your sign. Upgrade and you're in the running for a Lyceum seat. 🚀 📨 How to submit: Drop a screen recording or screenshot of your artifact, the link if you've got one, and your writeup in the comments below. 📅 Deadline: Saturday, May 2nd at 12:00 PM EST 🎉 Winner announced: Monday, May 4th at 12:00 PM EST 💡 A note before you start. This isn't a finance challenge. It's a design and voice challenge. You don't need to be a CFP to win this. Read the brief. Marcus tells you exactly what he wants and how he thinks. Your job is to build something that solves his problem and sounds like him. 🆕 If you've never built an artifact in Claude before, this is a great first one. The brief is clear, the scope is reasonable, and the bar is "would Marcus actually send this to a prospect?" 🔥 @Ian Barriopedro set the standard last week. Your turn. LFG 🚀
Do you use AI for your hobby?
I'm curious what everyone here likes to do for fun (of course building stuff with Claude is fun too lol), and if you've applied any AI to your hobby. For me it's been super useful for DND planning and I find I get to stay in creative flow more. Curious what other people are doing
Something I built this week that will help anyone working with Claude Code
Background first — because how this came together matters more than the file itself. --- ## The problem I kept running into Every time I started a Claude Code session, I was re-explaining everything. Who I am. What I’m building. What matters. What not to touch. Session after session. The context would bloat. The model would drift. And I’d end up managing the AI instead of working with it. I thought the fix was a better prompt. It wasn’t. --- ## What @Ari Evergreen showed me Ari introduced me to the dispatch pattern. Instead of relying on chat history, you write a brief to disk before the session starts. The brief is the contract. The worker (Claude) opens it cold, executes, and returns a result. No shared history. No “as we discussed.” No hidden context. Her work on: - structured briefs - worker isolation - and the cold-start rule completely changed how I think about AI. The cold-start rule was the shift: > If the brief cannot stand alone, it is not finished. --- ## What @JakeVanClief framework gave me Here I learned to think in systems instead of prompts. - `CLAUDE.md` → navigation hub - `CONTEXT.md` → live project state - `REFERENCE.md` → stable lookups Three files. That’s enough for any new session to orient itself quickly, without scanning everything. That’s the foundation. --- ## The realization These aren’t different ideas. They’re the same idea at different scales. - A worker sandbox is a dispatch worker - A context file is a routing layer - A system architecture is just structured dispatch Once that clicked, the gap became obvious. --- ## So I built the missing layer A bootstrap file. One markdown file that sits at the top of a project and does what neither system does on its own: It aligns: - the worker model - the architecture - and the rules **before any work begins** --- ## What it actually does Drop it into a project, and Claude:
1-30 of 884
Clief Notes
skool.com/quantum-quill-lyceum-1116
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by