What are you working on this week? Could be an app, automation, content system, AI workflow, website, client project, creative experiment… let’s hear it 👀

(all install paths will be in the comments) 𝟏. 𝐒𝐤𝐢𝐥𝐥 𝐂𝐫𝐞𝐚𝐭𝐨𝐫 this is the factory that builds everything else. describe what you want in plain english → claude builds the skill, tests it, packages it. you never have to write a skill.md by hand again. drop in an SOP and it becomes a reusable skill instantly. install: /plugin install skill-creator 𝟐. 𝐒𝐮𝐩𝐞𝐫𝐩𝐨𝐰𝐞𝐫𝐬 fixes the #1 failure in claude code: rushed, sloppy output. forces claude to plan first, work in isolation, write tests before code, then review its own work twice. gets you from 60% → 80% on the first pass. fewer debugging cycles = less time, lower token costs. 150k+ stars on GitHub btw 𝟑. 𝐆𝐒𝐃 (𝐆𝐞𝐭 𝐒𝐭𝐮𝐟𝐟 𝐃𝐨𝐧𝐞) fixes context rot. you know when claude starts forgetting requirements halfway through a session and cutting corners? GSD spawns fresh sub-agents for each task so your main session stays clean and every task gets a full context window. also has an autonomous mode if you want to hand it a spec and walk away. 𝟒. /𝐫𝐞𝐯𝐢𝐞𝐰 𝐚𝐧𝐝 /𝐮𝐥𝐭𝐫𝐚 𝐫𝐞𝐯𝐢𝐞𝐰 already built into claude code. most people aren't using it. /review = fast structured code review after you build something. free beyond normal tokens. /ultra review = uploads your branch to a cloud sandbox, spins up parallel reviewer agents, each attacking from a different angle. bugs have to be independently verified before they hit your list. no false positives. need claude code 2.1.86+. costs $5–20/run after 3 free ones on Pro/Max. 𝟓. 𝐂𝐨𝐧𝐭𝐞𝐱𝐭 𝐌𝐨𝐝𝐞 keeps garbage out of your context window. raw tool outputs get routed through a sandbox. a 56kb playwright snapshot becomes 299 bytes. 315kb of session output becomes 5kb total. also tracks every file edit, decision, and error in a local SQL database so when claude compacts the conversation, it doesn't lose anything. sessions that used to fall apart at 30 minutes now run 3 hours clean. 𝟔. 𝐂𝐥𝐚𝐮𝐝𝐞𝐌𝐞𝐦 carries knowledge across every future session. claude normally starts from scratch every time. ClaudeMem hooks into the session lifecycle, captures what happened, compresses it into semantic summaries stored in a local SQLite db with vector search, then injects the relevant parts back in when you open a new session. also auto-generates and updates your CLAUDE.md files while you work.

Every person in here is part of the founding class of something special. To kick things off, I want everyone to drop an intro below ⬇️ 👉 Comment with: 1. Who you are (your name + a short bio) 2. What you’re building or interested in (sales, content, vibecoding, startups, data/ML careers, etc.) 3. What you want to take away from this group (skills, connections, accountability, results) The more we know about each other, the faster we can connect, collaborate, and accelerate. I’ll go first in the comments. Now it’s your turn. ⚡

Quick update to clear a few things up and close some open loops! First: the official release date for a few private courses are now locked in: January 31st, 2026 🏁 That applies to: - AI Creative Director - Everything About APIs (n8n + real-world use cases) If you’ve seen other dates mentioned before, no stress, this is the final one! Between Jan 20th and Jan 31st, I’ll still be dropping exclusive automations in here. They’ll also be showing: - How to actually use APIs in real workflows - How to use new creative tools like Kling Motion Control & Higgsfield’s Cinema Studio ✨ - More advanced image + video generation systems Think of it as a behind-the-scenes ramp-up before the courses officially open. On the office hours front, I’ve been in Paris🇫🇷 since Sunday and I’m here until Saturday, so I’m pausing office hours just for this week. We’ll be back to normal next week, and once we’re live again, bring all the questions you’ve got. And a few quick shoutouts so no one feels left hanging: - @K G private courses officially open Jan 31st - @Xiggy King APIs course isn’t delayed, just aligned to the date above - @Ini Ikpe The Q&A confusion was on me traveling to France but we’re back next week 💯 Appreciate everyone’s patience!! I’ve been taking this week to work on courses and automations to take EVERYONE in this group to the next level of wealth with automation. A LOT of good stuff is about to land. Anyone who sticks in this group will quickly start to feel more powerful with their new AI abilities.

To make sure people are getting questions answered about N8N templates and to keep 'Office Hours' focused and useful, I’ve set up a shared Office Hours Queue that we’ll be using going forward. If your question is not logged in the queue, it will NOT be answered live. ✅ Here's How to Reserve a Spot for Office Hours 1. Open the Office Hours Queue spreadsheet (linked here and below) 2. Add a new row (walkthrough video below) 📸 How to Add Screenshots (IMPORTANT) If your question involves an error, node config, or unexpected output, screenshots are STRONGLY recommended. Here’s how to add them correctly: 1. Upload the screenshot to Google Drive 2. Rename the file to something you’ll recognize (example: n8n question.png) 3. In the spreadsheet, click the File option under the Screenshots column 4. Search for the file by name and attach it. 🎥 Quick Walkthrough I’ve included a short walkthrough video in the sheet showing exactly how to fill everything out step-by-step. Watch that once and you’ll be good forever. ⏰ Office Hours Today There's an Office Hours today at 1:30pm PST. If you have: - Questions about an automation template - Something breaking in n8n - Confusion about setup or logic 👉 Log your question in the queue now so I can review it before the call! ➡️ OFFICE HOURS QUEUE SPREADSHEET