Claude Code for content

• CLAUDE.md: the orchestratorOne file, read at the start of every session. Its job is to route, not to contain everything.9 min1
• Skills are just foldersHow to move a long procedure out of CLAUDE.md so it loads only when it is actually needed.8 min1
• Subagents, and the one rule that keeps them safeSend four researchers out at once. Just never let two of them write to the same file.7 min1
• Plugging in real dataAPIs make research better, not possible. Build every one with a fallback so a dead key never stops the work.7 min
• Which part, when?A decision table for the four moving parts, and the slash menu that ties them together.4 min1

RewardYour CLAUDE.mdat 100% of this module

• Read the SERP before you write a wordThe research pass that decides whether an article can rank, and how to make Claude actually run it.8 min
• Verify once, reuse foreverThe knowledge base that turns research from a cost into an asset, and the stamp that keeps it honest.6 min1
• Blame your tooling firstThe most expensive lesson in the whole system. When a check returns something strange, the check is the suspect.10 min1
• Four ways to reach a page that looks deadA blocked request is not a dead page. Work through the ladder before you drop a source.6 min
• Mining Reddit without embarrassing yourselfReal quotes from real people beat another paraphrased vendor claim. Here is how to get them, and how many to use.6 min

RewardThe source escalation ladderat 100% of this module

• Never let it invent a linkClaude will happily write a plausible internal URL that does not exist. Here is the check that stops it.6 min
• The link set is a claim about the businessHow many internal links an article needs depends entirely on how the site makes money. Get it wrong and the page contradicts itself.8 min1
• Placing keywords you can actually countA placement rule that fits on one line, and why counting them in your source file gives the wrong answer.7 min1
• Meta, slugs, and the five-word anchorThe last mile. Four small rules that get skipped and then cost you clicks for the life of the page.6 min

RewardThe internal-link cheat sheetat 100% of this module

• The kill listAI writing has a vocabulary. Once you can see it, you cannot unsee it, and neither can your reader.9 min1
• Give every section a shapeSix structural rules that stop an article turning into a wall of bullets. These are what make Claude's output look edited.7 min1
• Never let it describe your product from memoryThe knowledge base is not documentation. It is the vocabulary file that stops Claude inventing features you do not sell.7 min
• Write in phases, not in one shotAsk for an article and you get an article. Ask for an outline first and you get a better article, for less total work.6 min

RewardThe anti-slop kill listat 100% of this module

• Why three passes was not enoughThree passes check that rules were followed. They cannot see that the argument is wrong, and twice in a row they did not.7 min
• What each pass is looking forFive passes, five different jobs. Learn to route a defect to the right one and you never run the wrong check twice.9 min1
• Let a script do the boring halfAbout a third of proofreading is mechanical. Write it once, run it forever, and never get bored at article thirty.7 min
• A scripted edit is not a safe editBulk edits pass every count and quietly break meaning at the joins. Here is the check that catches it.6 min
• The completion gateThe rule that stops a draft calling itself an article: name every pass, or call it a draft.5 min1

RewardThe five-pass SOPat 100% of this module