came back after a week offline and spent an hour just reading posts. people are shipping. full agent teams, named specialists, live clients. and i'm still on the foundation. but here's the honest version of what's actually happening. i build something. it works. then i look at it and realise it's not what i actually wanted. so i break it and start again. then halfway through the rebuild, a new idea comes in and now i don't know if i should finish what i started or pivot to the thing that's clearly better. i've rebuilt the same system three times in a month. and the worst part.. each version was better than the last. so was the rebuilding wrong? or is that just what building actually looks like before it locks in? genuinely asking because i can't tell if this is a me problem or if everyone here is quietly doing the same thing and just posting the final version.

This was such a challenge. I had a idea for a hero landing page design but it was not coming together as I hoped. It got to the point where i was using GEMINI, CLAUDE and CODEX to "just get something close it". Alot of back and forth prompting, folder structure fell apart the first time. I just had to keep engineering it. Tried it forward and reverse engineering it. I was patient but very persistent. I COULD HAVE BEEEN BETTER ORGANIZING AND STRUCTURING MY FOLDERS. It seemed like there was no hope. It seemed no matter how good i got them, the design was just odd, not as direct and very confusing. WHAT DID THIS DO....? ACTUALLY, it inspired me to create my own tools and workflow systems so my designs can manifest exactly how i please and i can have more control of the details. Something ill be speaking and following @Ari Evergreen and @David Vogel about. And of course more videos from @Jake Van Clief. I went into gemini and created parts of the design and had it add controls for it so i can get it looking how i wanted, then took the code and added them to my files or my prompt. This seemed to really advance the design forward. i need to find a better way to update the files. This design was not easy! I want to thank @Shirsho Guha @Marcos Accioly and all others for the feedback on the my other post for my first website. You can see the old version and 1st post about it here: https://www.skool.com/quantum-quill-lyceum-1116/project-2-personal-website-sheesh?p=8319ce31 Definitely learned alot and look forward to adjusting for better workflow and designs. V5 with HERO DESIGN https://www.koachkev.io/

💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.

I've been running cold email campaigns for clients for 3 years and the biggest shift I've seen isn't the tools. It's what actually gets a reply. Personalization used to mean scraping a name and company from LinkedIn, dropping it in the first line, and hitting send. "Hey {FirstName}, I noticed {Company} and thought..." That worked in 2022. It's dead now. Everyone's doing it and prospects can spot a mail merge from the subject line. What changed for me was treating personalization like actual research instead of a data field. Here's what I started doing: → I scrape the prospect's entire website. Not just the homepage. Blog posts, service pages, case studies, about page, even their contact form if it's there. → Then I feed all of that into OpenAI and have it analyze what they actually do, who they serve, and what problems they're likely dealing with. The AI doesn't just summarize. It finds the specific details nobody mentions in generic outreach. So instead of "I saw you work in logistics," the email opens with "Noticed you handle cross border freight into Mexico. Your blog mentioned customs delays eating 15% of delivery windows." That's the kind of line that gets opened because it doesn't sound like 500 other emails they got that week. The reply rates went from 2-3% with generic personalization to 8-10% with actual research. One prospect replied last week: "Your email won because you actually read our site. Everyone else sent the same template." The system I built does this automatically. Scrapes the website. Analyzes every page. Generates icebreakers that reference non-obvious details. It writes openers like a human who spent 20 minutes studying their business, except it does it for 1,000 prospects in an hour. Here's what I learned building this: Small prompt details make a massive difference. Having OpenAI shorten company names naturally (say "Stripe" not "Stripe Inc.") and reference specific pages beyond the homepage makes it feel real. The difference between "I saw your website" and "I saw your freight tracking dashboard lets customers get ETAs without calling" is everything.

Am I trying to reinvent the wheel for my first ICM project? I'm working on building job search tools/workflows to support my own job search. I've jumped in head first and: - I'm burning through my CLAUDE PRO tokens - why? My sense is I've setup my root CLAUDE.md file poorly. I switched from Sonnet to Haiku and never used Opus. (I know there are other ways to access LLMs, but I want to spend some time mastering the Claude Code extension interface before jumping into openrouter, Claude API, etc.) - I'm iterating the folder/workflow/skill design but still getting really poor draft outputs (I got better outputs just prompting in the free version of Claude) - I'm still learning the Classroom content and am hoping to get some insights as to any red flags for being newer to this (i.e. I'm just biting off too much for my first project) ## Workspace Structure ``` jobbot/ ├── CLAUDE.md ← You are here (always loaded) ├── CONTEXT.md ← Task router ├── _config/ │ └── story-bank.md ← Master STAR narrative library (shared across workspaces) │ ├── linkedin-optimizer/ ← Build and maintain LinkedIn presence + content │ ├── CLAUDE.md │ ├── CONTEXT.md │ ├── profile/ ← Profile optimization pipeline │ ├── content/ ← Content creation pipeline │ ├── growth/ ← Analytics and growth tracking │ └── _config/ ← Stable reference: profile, voice, keywords, pillars │ ├── resume-optimizer/ ← Master CV + JD-tailored resumes │ ├── CLAUDE.md │ ├── CONTEXT.md │ ├── master-cv/ ← Full CV maintenance pipeline │ ├── tailored/ ← Per-application tailored resume pipeline │ └── _skills/ ← 6 skills: audit, rewrite, jd-decoder, match, tailor, ats-check │ ├── cover-letter-optimizer/ ← Per-application cover letters │ ├── CLAUDE.md │ ├── CONTEXT.md │ ├── pipeline/ ← intel → narrative → draft → review │ ├── final/ ← Approved cover letters │ └── _skills/ ← 4 skills: company-intel, narrative-select, draft, review │ ├── application-engine/ ← Application prep, ATS forms, tracking, analytics