All skills Get in touch
AI Content Automation
Multi-brand content pipelines with explicit states and review gates, built so scale does not become dilution.
How I use it
Drafts scattered with no pipeline
Built a content system where each piece moves through explicit states — brief, draft, review, scheduled, published — instead of living in a folder nobody can audit.
Automation that damages the site it feeds
Nothing publishes without clearing a gate. Volume is the thing that hurts a domain, so the gate is the feature and the generation is the easy part.
Prompts edited on vibes
Tested prompt variants against each other on held-out inputs rather than changing a prompt and trusting that it improved. Most "better" prompts are not.
What I use
- Claude API
- TypeScript
- PostgreSQL
Related skills
Want the detail behind any of this?
I can walk through any of it in as much depth as you want.