The preface: Anyone near my age (60) knows what it was like to take math classes and forced to do write out every answer on paper and show their work. Calculators were barred from classrooms. "You won't have a calculator with you all the time to work out math problems" Well, that was a lie. Whatever I need to do I can do on my phone. Calculators? Everyday folks don't even use them. The problem: I read a comment a few days ago from someone who has a tech (coding) background stating that people who vibe code need to understand what the code does. I'll be the first to admit, I don't know what all goes into the things I make. Since I used to create websites (and worked for a web hosting company), I grasp the fundamentals (html, css, but I don't know a lick about Python or a host of other programming languages. But I create some really cool stuff. I built a full AR system for my sister and her husband's solar farm business. I created a "Planner Factory" which allows me to create bespoke journal pages for new products. I designed a "Guide" that gives visitors encouragement, provides scriptures and prayers and helps them find the products that match their needs on my site. I made a "Logistics Review Tool" that runs against my builds to verify 16 operability lenses + ICM. I just finished a "Prayer Video Studio" for YouTube shorts. I'm finishing a "Mockup Studio" for my Simplify to Glorify brand of products. (and more...) Do I know how they work? Nope. At least not entirely. I know the basics. Does that matter? I don't know - and that's why I am asking the question. Where my mind goes with this: I can make mayonnaise but I have no idea what the whole chemical process is that makes it happen. I can play the piano and know when something sounds good (or awful), but I don't have a background in music theory. Do I need to know what makes it work?

## UPDATE ## Hey All made some updates to the extension, full changelog below but biggest thing is it's now in the Chrome webstore as an unlisted extension! To install for firefox should be a 1 click install below, and for Chrome follow the link to the web store: Firefox: https://github.com/rocleemusic/skool-view-dist/releases/download/v0.3.2/skool-view-0.3.2.xpi Chrome: https://chromewebstore.google.com/detail/skool-view/cffkfollpgckdnelbincojldcmhihfgm?authuser=0&hl=en BONUS: Edge users can install extensions from the Chrome Web Store (just for you @Jake Van Clief ) so you should be able to install it as well, just need to enable it because of permissions (see below). Note on the Chrome extension: It may be disabled by default because of permissions issues so you might need to enable it by going into your extension settings, but after giving it permission it should be good to go. Chrome signing / validation also takes longer so it may be on version 0.3.1 but after it passes review should auto-update to 0.3.2 Also special thanks to @M. M. who forked and added some features that I wrapped in to this release. Things I'm hoping to add: Real links to the posts, currently it caches the data. Search functionality, and export post as .md. ## ORIGINAL POST ## Browsing on Skool can be a bit overwhelming with it's UI (my eyes need a dark theme) and the great volume of stuff on CliefNotes makes jumping in daunting, especially if you're away for more than a day, so I wanted something that made browsing feel effortless and easier to navigate and see things and keep posts around that I wanted to dig into a bit more. So I built a browser extension that gives me a faster, cleaner view over the same Skool feed, posts, and comments.

Carla took the top of the leaderboard this week. 🎁 What @Carla Bosteder wins: She was already a VIP member, so we're converting her account. ✨ Free VIP for life. ✨ The Drawing Room. High Tea. Bespoke folder builds with Jake. All of it. Forever. No charge. ⏰ The 7-day clock resets. Next Monday someone new takes the top spot. 🎯 How it works: - 📝 Post things worth reading - 💬 Help people in the comments - 🛠️ Share what you're building, what's working, what's breaking - ❤️ Engage with what others are putting out there The leaderboard tracks all of it. 🎁 The prize, depending on where you're at: 🆓 Free member? You get lifetime Premium, free ⭐ Already Premium? We convert your Premium so you stop paying 👑 Already VIP? We convert your VIP so you stop paying Either way, you stop paying. Carla, congratulations. Well earned. 👏

New VIP member checking in! as excited as i am for my journey, It wasn't an easy decision, but I know knowledge pays dividends.This was an investment in myself, and I'm committed to making it count. Time to bunker down, learn, grow, stay disciplined, and put in the work. Looking forward to being part of this community.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 📋 THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- 🎯 THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- 🗂️ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2️⃣ The folder system that solves it. Same structure as every week: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 📚 reference/ - 📖 README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- 🔥 THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪