Come chat about your goals for the week! If you are new here, this is a chat room for general talk about the past week and the week ahead. Share what you’re working on and network with others! If you‘ve been here before, you know the drill. Leave a comment below: - What you’re working on - Something you hope to ship - Blockers you’re running into at the moment - Where you’re looking for help currently - Anything else you’d like to share Have fun and enjoy your week everyone! This weeks poll: lately I’ve been feeling like I’ve moved more from building and learning to a good portion of my time utilizing the systems I’ve finally shipped. This has been a big and welcome shift for me and I feel like I actually am grasping this stuff. Where are you on your journey?

## 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.

There's a rule in teaching called backward design. You don't start with the lesson. You start with the assessment. Decide exactly how you'll know they learned it, then build backward to the activities that get them there. Sounds obvious. Almost nobody does it, because writing the test first is harder than diving straight into the fun part. Same trap with AI builds. We open a chat and start barking the build before we can say what "done" actually looks like. Then we act surprised when done keeps moving. The habit i borrowed from the classroom: if you can't write the check for "done," you're not ready to build. Not the feature, the check. One sentence you could prove true or false. "A new user gets from signup to first export without asking me a single question." Now every step has a target to aim at, and you'll know the moment you've hit it. Writing that sentence first feels like bureaucracy. It's the opposite. It's the thing that stops you building three polished versions of the wrong feature. And there's a bonus. If you can't write the sentence, you just found out the project isn't scoped yet. Better to learn that now, for free, than four hours in. What's your one-sentence "done" for the thing you're building right now?

Most people drive AI like a slot machine. Type a vague wish, pull the lever, hope. Wrong output, pull again. Three hours later: forty messages, half right code, no idea which version was good. That is not building. That is gambling with extra steps. The fix is not a cleverer prompt. It is a plan. Here is the exact habit, start to finish. The one idea Stop prompting. Start defining outcomes. A prompt is a wish. An outcome is a result you can check. AI accelerates, it does not generate. Point it at a clear target and it closes the gap fast. Point it at a vague one and it just gets lost faster. ———————————————————————— The chain (this is the whole method) 1. Brainstorm first. Do not open a chat and start barking instructions. Open a conversation whose only job is to decide what you are building. What does done look like. What must be true. What is out of scope. I use `/brainstorm` and answer one question at a time until the fog clears. 2. Freeze it in a spec. A spec is the brainstorm written down and made hard to argue with. Three parts: - Objective, in one sentence you could prove true or false. - Constraints, the rules that bound the solution. - Definition of done, where every item can be checked with a single action. If you cannot write the objective sentence, you are not ready to build. Better to learn that now, for free. 3. Break it into a phased plan. Turn the spec into ordered, bite sized phases. The rule that matters most: each phase must be small enough to finish in one sitting, with room to spare. 4. Hand each phase over as a typed brief. This is the part that does the heavy lifting. Read the next section. ———————————————————————— Think in PRDs A typed brief is a product requirements document, scaled to whatever you are making. It is the difference between "build me a settings page" and a short doc with a goal, constraints, acceptance criteria, and phases. It feels like bureaucracy. It is the opposite. The brief is a forcing function: - You cannot write acceptance criteria for a feature you do not understand.

Just wanted to do this post as I'm genuinely curious what other people are using to communicate with their Claude chats, Claude Code, etc. For me everything is done by talking into different Claude chats, which are essentially workers. Those Claude chats generate the prompts for me to put into Claude Code. I spend all day orchestrating different Claude chats and making sure that everything runs smoothly, basically just orchestrating a workflow. I'd be really interested to know what other people are doing: - Are people using Wispr Flow? - Are people typing? - Is there another alternative?