Built a content pipeline with Claude Code - the CLAUDE.md file is underrated

I have a small Substack about infrastructure postmortems. The writing is fun but the research (scanning blogs, searching HN, building timelines) was taking forever, so I built a system to automate it. Four parts: * Discovery: Python scripts scan RSS feeds + HN for postmortem articles * Ranking: Scores incidents based on criteria I defined (emergence, irony, lessons, etc) * Research: Fetches postmortems, extracts HN comments, builds timelines * Writing: Generates draft angles based on my existing articles as voice samples The thing that surprised me: the [`CLAUDE.md`](http://CLAUDE.md) file matters way more than I expected. Claude Code reads it as project-specific instructions, and once I put my article structure, voice guidelines, and quality checks in there, the whole system started behaving like I wanted. It's basically a config file for AI behavior. Anyone else using these extensively? Code is here: [https://github.com/rajjagirdar007/content-engine](https://github.com/rajjagirdar007/content-engine) Also wrote a deeper blog post abt this: [https://rjagirdar.substack.com/p/i-automated-my-substack-research](https://rjagirdar.substack.com/p/i-automated-my-substack-research)