From 55 folders to a content machine that runs itself

Spent an entire day stress-testing the batch pipeline across multiple projects — verifying provenance claims, auditing conversation transcripts, and building the skill that would let me run batch-project-pipeline on any Antigravity project folder and get draft content out the other end. The conversation hit 844 steps and 39 user turns, the longest single session in this project's history. The pipeline reads the conversation index, separates user conversations from subagent noise, deep-reads transcripts for inflection points, and drafts log entries in the site's voice. When the first dry-run produced 376 lines of speculative recommendations based on conversation counts instead of conversation content, I killed it and rewrote the skill to require evidence-backed provenance chains. Every log entry now cites specific conversation IDs and step ranges. Every thread traces back to its source entries. The skill went from 0 to 662 lines across 5 working days — a codified version of everything I learned about turning build history into portfolio content.

Three skills now compose the full pipeline: ai-studio-export-rescue (342 lines) for cleaning raw exports, batch-project-pipeline (662 lines) for autonomous content production, and publish-content for the interactive human-in-the-loop workflow. The 55 apps aren't just sorted anymore — they're feedstock for a content machine that reads its own build transcripts and writes about what happened.