💰 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 🚀

I wanted proof that my prompts improved from four months ago. The results turned into this post. Around early January I added these instructions to my Claude.ai user preferences: If required information is missing, ask clarifying questions before answering. Before giving the final answer: list assumptions, identify missing data, state confidence level. If appropriate, advise on how to write a prompt more efficiently in the future. Then I had Claude pull my chat history from before and after, and look for patterns. I figured I'd see changes in what I was asking. The actual change was in how I structured conversations around the asking, in three phases. Phase 1: one-line prompts (early January) Real prompt from January 8: "How do I set up a eSIM on a Windows laptop?" I was asking the way you'd ask a search engine. Claude wrote a generic eSIM tutorial. I bounced because it didn't match my situation, and never came back. That was my default. One sentence prompts. No context, no constraint, no goal. Phase 2: Claude starts showing its work (mid-January) This is where the instructions started doing actual work. The "list assumptions" line forced Claude to write down what it was filling in for me. When a response opened with "Assuming this is a Windows endpoint with standard user permissions and no recent OS reimage," I could correct the wrong guesses before they corrupted the rest of the answer. About half the time, at least one was wrong. "Identify missing data" produced a list of the questions Claude wanted to ask but was about to silently guess at. Reading that list every response taught me what to include upfront. Every "missing data" bullet was a future prompt fix. "State confidence" forced Claude to mark which parts of the answer were solid and which to stress-test. "High confidence that one of the first three checks will identify the cause" is useful in a way that a confident-sounding wall of text just isn't. The prompt-efficiency line pulled the other three together into a habit. After enough rounds of "next time include the OS version and whether the machine is domain-managed," I stopped needing to be told.

Locked in for the next 5 days only. Ends May 5th at 10:00 AM EST. No exceptions. 🎉 Premium: $27 → $14/mo 🎉 VIP: $97 → $67/mo The closest you'll get to our original launch pricing. We're doing this because the community has shown up for us, and we want to show up back. 🤝 🔥 Already a member? Read this carefully. To lock in the new rate, you need to: 1. Cancel your current plan 2. Resign under the new price That's the only way the system can apply the new rate. We have way too many members for manual refunds, so we can't refund anyone who just signed up at current pricing. But the savings stack month over month, so if you plan to stick around (and you should 😁), the math works out fast. 🚫 A few ground rules: Please do not DM myself or Jake about pricing, exceptions, or extensions. We love you, but we're a small team and we need to stay focused on building. Everyone gets the same window. Everyone gets the same deal. If you miss it, you miss it. We'll do more things for the community down the road. ⏰ The clock: 🟢 LIVE NOW 🔴 Locks May 5th, 10:00 AM EST - Premium gets you The Vault and Afternoon Tea calls. - VIP gets you The Drawing Room, High Tea, and bespoke folder builds from Jake himself. If you've been on the fence, this is the moment. 🚀 Tag a friend who needs to be in here. Let's make Cinco a movement. 🎊 🌶️🌶️🌶️

So I signed up for a year of premium. I really don’t know what the difference is in benefits per level. Most of the info is free to all? I think I’m missing something?

A few people asked about my .md based task management system so sharing it here: https://github.com/rocleemusic/TaskSystem I should also mention I have my main workspace as a github repo because I work between 2 different computers at work and home, so I have a hook command, when i type /sync on a computer it pulls from github and then runs the task system. the manual call is : What's my focus for today? I'm also still tweaking the retrospective section since it's only come up once since starting to use it. There's a full breakdown and examples in the repo, feel free to ask questions or if you find something that's broken, it might be missing some context from my main Claude.md I've also included a build-instructions.md so you can give that to claude and have it built anywhere. it's large cuz it includes the schemas for the child folder files and i wanted to make it easy to use as a single file. But it was built thinking about how I would like to interact with Claude (like Jarvis). The main entry points for me are an ideas.md at root where I can throw any idea I suddenly have, and the main chat at start of session to get the 1-3 things most important to do today. It's grown a bit to include recurring tasks and flag high-priority things. The other goal was to offload the burden of remember what's important or to figure out what I have energy to do after work. I also wanted it as pure markdown incase an online service went down, I can still view the full list or just my focus, it's just a text file on my system. The thinking behind this was largely due to some realizations after watching Jake's videos. If we think of AI as a programming language, then what is it's infrastructure? What do I need to actually build a full app for something that I can describe with plain language and have AI serve as the interpretation layer to the computer below? Any workflow is really just a program codified into a step by step task list.