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

Twenty-four days ago I posted about Jake's folder system video. This is what happened next. Same foundation — markdown files, orchestration prompts, clear roles. I just kept building. Fifteen named specialists. Each one with a soul file, guardrails, and a playbook. Duke orchestrates. Cash writes. Trace pulls the data. Hank runs the financials. Clint handles the MCP integrations. Behind each one is either a human counterpart doing the real work alongside them — or a role I can't afford to hire yet. Katie who's been with me for 18 years, now has her own orchestrator running the same system. Twenty-seven client folders. Twelve live MCP integrations. One shared repo. The folder system isn't replacing my agency. It becoming my agency. Jake gave me the unlock. This is how it's going.

You learned the framework. Now try it on something you're actually working on. Vote below, then drop your prompt structure in the comments. Not the output. The structure. Show us how you set it up.