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

The setup Yesterday I posted about rebuilding my workspace to be agent-agnostic. Plain markdown, plain YAML, env-var paths, no Claude-specific lock-in. The thesis: when the tooling layer churns, the workspace outlasts it. I did not expect to test that thesis the next day. What happened Claude went down mid-task. I opened Codex CLI in the same workspace. Same skills loaded. Same memory. Same briefs. Same manifests. Codex read the workspace exactly the way Claude reads it, because the workspace is just files. The task done. Faster, actually. Zero downtime. Zero re-plumbing. Zero "let me port my setup." Why it worked Three properties carried the swap. The orchestration layer is plain text. Briefs, manifests, memory, voice rules. All markdown and YAML. Any agent that reads files reads my workspace. The agent-specific bits are isolated. Hooks, slash commands, settings live behind one entry point. Codex doesn't need them. The rest of the system functions without them. The skills are portable. My skill definitions aren't Claude-shaped, they're task-shaped. Codex picked them up and ran. The lesson When you build your stack around one tool, an outage is a stop. When you build your stack around your workspace, an outage is a tool swap. The agent is a worker. The workspace is the contract. Workers are interchangeable. This is the whole point of decoupling. What I'd do differently Nothing. Yesterday's migration was the work. Today's outage was the dividend. If you're still running everything inside one agent's surface, that's a single point of failure dressed up as convenience. Pull your config, briefs, and memory into plain files. Put the agent-specific layer in a sidecar. Test the swap before you need it. You will need it. // A<3

So as some of you know, I posted yesterday about having an agent agnostic workspace. Here's a few learnings for those building out their workspace now, so that you don't have to spend a couple million Claude tokens porting your entire workflow like one gurl did. 😅 The trigger I spent a day rebuilding the foundation under every project I run. The orchestration layer behind everything I do, every product, every brand, every active client, sits in one root. Last week I moved that root. The move cost roughly two million tokens of Opus output, sixty-seven logged migration steps, and a purpose-built migration toolset. Worth it. Here's why I did it, what changed, and the structure I wish I'd started with. Why I did it The old setup grew. Months of layered decisions, each defensible in the moment, ended up nested three folders deep with the same name repeated in each. Not a typo. Three of them. The path was a symptom. The real problems were structural. Code, content, and config were braided together. Every workspace held source files, render outputs, plan documents, briefs, screenshots, and configuration in one tree. Backing up orchestration meant backing up renders. Reading briefs required mounting the encrypted code drive. Hardcoded paths were everywhere. Tools, hooks, plugins, and native apps all assumed one specific absolute path. One move would have shattered the system. The configuration was Claude Code specific. Hooks, settings, slash commands all baked into one agent's surface. If I wanted to run the same workspace through Codex or Gemini, the layer of plumbing I'd need to build was its own project. Session state and canonical config lived in the same directory. Ten gigabytes of accumulated runtime state in .claude/ made the workspace feel heavy. Most of it was regenerable. None of it was sorted. What changed The migration introduced three roots, each with one job. Workspace root holds orchestration only. Markdown briefs, YAML manifests, plans, decisions, content drafts, memory bank.

Long story short don't forget to remove your API key from your ENV variable in VS Code after running out of credits. I switched mid stream to another account and it continued working, but somehow it was still running on the API. The system looked at all the activity and decided I was a threat. Evidently they are really busy so it's going to take a while. Account Ban Appeal Form If you believe your account was wrongly disabled by our systems, please answer the following questions. Please Note: We are currently receiving higher than normal email volumes due to our recent launches; therefore, our response times will be slower than normal. We will be in touch as soon as we process your appeal.

What brought you to this course? Vote below, then tell us in the comments