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.

https://www.koachkev.io/ Semi-done, but yeah — this is the place to learn, build, and prosper. I’ve had this plan and idea for a long time. Honestly, it’s been about 8 years. I always wanted a personal website — a real digital home base where I could share my work, update ideas quickly, make changes whenever I needed, and keep building over time. In one of the photos, you’ll see a GitHub project I started 8 years ago. Thanks to AI, and the ICM training from Jake in this Skool, this became much more possible — faster, cleaner, and more efficient. Before this, my biggest issue was that I could build parts of a site, but I couldn’t create it the way I actually envisioned it. Long story short, it never came out how I wanted. JavaScript was difficult for me to learn at the time, and I had other priorities, so it never became the main thing I focused on. But I’ve always had ideas, plans, systems, programs, and brands I wanted to build. Now, those things feel closer than ever. This personal site is still in progress. I’ll show you Version 1, which was created by using my X account and my YouTube channel — youtube.com/@koachkev — as the foundation for my brand, style, and content direction. Then I’ll show you V2, images attached For V1, I took my accounts into Gemini and asked it to scan everything and create a review of my brand and style. Then I took that file into Claude and used it to create a claude.md file and a context file. From there, I went into Claude Code, told it what I wanted, and out came V1. You’ll see that in the attached images. V2 came from me adding, changing, and refining things. I knew I was still missing a lot — the details, the flow, the wording, and the overall feel needed work. I changed the colors, cleaned things up, and let it sit for a bit. That’s also when I took it live using GitHub, Vercel, and Resend for the email newsletter system — all free. For V3, I went back through old notes: ideas, programs, systems I knew I wanted to build someday, and YouTube video concepts I wanted to eventually put behind a paywall.

There have been some good questions in my previous posts about my agents, so I want to clear up a few things. I call them agents because it helps me think and stay organized. But strip the jargon and here's what's actually happening: a folder with the right files in it tells an AI who it is, what it does, and what good looks like. Unix figured this out a long time ago. I remember working on mainframes in my early 20s. Files in folders. It wasn't powerful because it was complex. It was powerful because it wasn't. Unix came out in 1969; I was using it from 1998 to 2002. The "writing room" is a folder. Cash lives in it. His instructions, his guardrails, his examples, his voice reference — all files. The AI reads the folder and knows how to behave. The room gives it context. The files give it structure. I have 15 of these rooms. Duke orchestrates between them. The naming isn't the point. The structure is. Here's the part most people miss: almost every agent in my system has a human counterpart. A real expert whose domain knowledge shaped the instructions — and who can tell me when the agent gets it wrong. Cash's counterpart knows copywriting. Trace's counterpart knows data. That feedback loop is how the system actually improves. You're not building AI. You're building infrastructure. Build the foundation. Build the structure. The agents are just what you call it when the rooms start working together. My lesson: don't copy me, don't copy Jake, we all learn from each other, and then you make it your own. Stick to the fundamentals. Watch Jake's videos; it will rewire your brain and change how you think about AI. There are no shortcuts. You have to build a foundation first. Links to referenced posts: https://www.skool.com/quantum-quill-lyceum-1116/visualized-my-agent-team https://www.skool.com/quantum-quill-lyceum-1116/the-folder-system-became-my-agency

Inspired by @Curtis Hays, I finished an experiment that I had started a few weeks ago. I started my company as a local web design agency in 2014. I've pivoted a few times since, where our core offer is that of Fractional CMO services, but we still do some agency type work for existing clients, friends, and family. I was ready to throw in the towel on web builds just because they take so much time and I hadn't cracked the code on building sites with ongoing content. I finally got it this evening! We've gotten good at building unique sites using Claude with next.js, files live in github, website runs on vercel. This evening I was able to get a headless WordPress environment where I can add/edit/delete content, but the design still lives in Vercel! I realize this might seem like a small thing for some, but it's a ginormous win for the 8 SIGNAL team :D It's gonna save us sooooooo much time rebuilding from next.js to Elementor. Huge shoutout to Curtis. By sharing his win, he inspired me to dig further into this and figure it out! Here's the site that was previously just a "static" site on vercel, now all the content is coming from a wordpress install: https://century-rentals.vercel.app/ P.S. If you have a better way of managing websites that require a CMS and SEO/AEO, don't hold back. I won't be deflated. I'm always looking for ways to improve and do things better. P.P.S. Website's for a buddy, and still not finalized yet, so I'm taking some liberty to mess around with him about baseball because he knows less than I do, and I don't know much LOL!

There are two skills in Claude that I use over everything else that have been really successful for me. I love the folder system here and I use something similar just to keep things organized. As I'm sure most people have heard of Superpowers and I think it's good to a point. Superpowers is good at brainstorming and asking me the questions I didn't consider but it's bad on execution. That's where GSD or Get Shit Done comes in. It can take the plan from Superpowers, break it down into Phases and Waves and then you verify at every checkpoint to make sure a certain feature works. This effectively allows me to "one-shot" apps and make sure it works along the way. The part of the stack that I don't have nailed down yet (leaning into my cyber security background a bit) is security and just trying to make sure we cover stuff like prompt/code injection for example. Does anyone else have a similar stack or different process?