Write something
Pinned
Mar 15 •
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
4160 members have voted
Pinned
3d •
🏆 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 🚀
16d •
From messy to branded profile grid
With very little experience a week ago, I created a project outline to brand out the cover images on Instagram profile grid. In less than 30 min, after going through the foundations i had it completed. Claude code executes with just two words and can make as many cover on demand as i wish and output them neatly as PNG files in a folder. Jake - super thanks! I learned so much in less than a week 🙏🙏🙏🙏 See before and after :)
1h •
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 ***
11h •
In Production: Are Agents Driving Workflows or Are Scripts Orchestrating Them?
Trying to sanity check how multi-step workflows are actually handled in production. The way I’m currently thinking about it: When building, it feels very agentic (using markdown like claude.md, rooms, skills, etc. to structure everything and have the AI help design the system). But in production, I’m trying to understand how control actually flows across multiple steps. Is it more like this: Option A (AI-led flow): - Trigger fires - Script collects data + relevant markdown - AI is called - AI responds and decides the next step - AI continues task-to-task from there OR Option B (Script-orchestrated flow): - Trigger fires - Script collects data + relevant markdown - AI is called for a specific task - AI returns output - Script takes that output, decides next step - Script loads new context/markdown - Script calls AI again (and this repeats for each step) So basically: 👉 Is the AI “driving” the workflow once triggered 👉 Or are scripts orchestrating each step and calling AI as needed Feels like it might be more B or somewhere in the middle, but not sure what’s actually best practice. Would love to know how others are structuring this in real systems.
1-30 of 883
skool.com/quantum-quill-lyceum-1116
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
1
+764
2
+638
3
+468
4
+391
5
+387
Powered by