We've been hoarding links like digital pack rats -- and it's time to crack the vault open. Jake and I put together a running list of the tools, resources, and random goldmines we keep coming back to. The stuff that actually stuck after the hype wore off. If it survived our workflows, it earned a spot here. https://www.skool.com/quantum-quill-lyceum-1116/classroom/c7f102c7?md=59285d6b92ed425cae7f439761e26acf ------------------------------------------------------------------- WHAT THIS IS Think of it as a curated toolbox -- not a "Top 100 AI Tools" listicle from some SEO farm. These are things we've actually used, broken, duct-taped back together, and kept reaching for. Some are well-known, some are buried gems we stumbled on at 2am while chasing a rabbit hole. WHAT WE NEED FROM YOU This page is alive. It's not a monument -- it's a workbench. - Drop a comment if something on here saved you hours (or cost you hours -- we want to know that too) - Suggest additions -- what's in YOUR toolchest that we're sleeping on? - Call us out -- if something's outdated, broken, or just not as good as the alternative you found, tell us - Share your use case -- same tool hits different in different hands. How are you actually using these? We'll keep updating this as the collective stack evolves. Your feedback shapes what stays, what goes, and what gets added next. ------------------------------------------------------------- Disclaimer: You know the drill -- this is garage tinkering, not production gospel. Your mileage may vary. Duct-tape what works and break what doesn't. Let's keep building brains that can't be taken away from us.

I've been in this community for about a month now and wanted to share where things stand with one of my builds. This isn't polished by any stretch. I do have a few other workflows like content-creator, document-creator, but I needed something to help me navigate my day-to-day as I begin a couple side quests outside my normal 9-5. The goal was simple: I didn't want another chat window I have to remember to open. I wanted something that knows my priorities, reads my calendar, checks my email, and texts me when I need a nudge. Not a chatbot, more like a Chief of Staff. And the goal is to operate within the bounds of the subscription with no extra costs, while also maximizing token efficiency. The other thing I didn't want to do is implement an orchestrating harness yet (OpenClaw, Hermes, etc). The challenge for myself was to keep this as simple as possible without inflating scope. Someone in this community said once: 'constraints are just as, if not more, important than your requirements. What do you NOT want your build to do?' I've definitely taken this to heart in my workflows. ## Planning I've made a few posts about this in comments, but I cannot stress the importance of planning before you build. My method was simple: - First I brain dumped context via voice dictation and transcribed this. Simple tools: VoiceMemos, copy, paste. - Next, I worked through the planning phase with the chat function of Claude in Opus 4.6. I wanted pushback, challenge, and for the model to force me to think deeper and keep me honest. This produced the product requirement document, or PRD. This was a multi-day process (a week?) in my free-time. - For the architecture build, I used Cowork. Handed it the PRD, answered a few basic questions, and then it went on it's way. Got it uploaded to a private git repo. - Currently, I'm working thru further debugging and walking thru the checklist within the PRD in a phased approach. As you'll see below, I have setup a remote screenshare so I can also let Cowork see what I'm doing. This was the most essential because we work TOGETHER to make things happen. it's like working side-by-side with my developer and engineer.

I am working on 4 different projects using mainly Claude Code and CoWork. Two projects are personal and two are for clients. I understood that I need to be in the loop to make important decisions (strategic, operational, aesthetical). So, I tell my agents to show me their work stept by step, present pros, cons, unkowns, and ask for my decision. So, I spent my day answering questions from my agents as the present me their work, just like a CEO would spend their day answering questions from its direct reports. Sometimes they are high level questions, sometimes they are detailed quesitons. I might be able to automate some of those decisions in the future, but now I understand where do I need to spend my time and how important is our capacity to make decisions about complex issues.

Has anybody else experienced Claude prompting them to switch to Sonnet 4 due to some sort of safety filters being activated? Does anybody have any suggestions on what to do so that it'll stop blocking my chats? All I've done is talked about building this folder architecture and worked through the process with it.

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.