Automating Content Briefs with Claude Code + Supabase Queue

# claudecode# supabase# automation# indiehacker
Automating Content Briefs with Claude Code + Supabase Queuemasato

Built a 3-layer content pipeline using Claude Code routines: weekly-content-planner (weekly) —...

Built a 3-layer content pipeline using Claude Code routines:

  1. weekly-content-planner (weekly) — reads GSC/GA4 CSVs, generates priority-ranked briefs, INSERTs into Supabase content_briefs
  2. content_briefs table — acts as a queue with status: planned → in_progress → published
  3. content-executor (daily 02:00 JST) — pulls 1 brief, writes MDX article, git pushes, Slack notifies

The key design constraint is in CLAUDE.md:

  • Max 1 article per day (hard rule)
  • No fabricated numbers — only use data from data_evidence field
  • If lint script not found → skip and continue (don't halt)

3 failures I hit:

  • Mixed up prod/staging Supabase project_id
  • Executor halted on missing lint script
  • Claude generated fake "200 subscribers" in ExperienceBox

Full implementation log (Japanese): https://masatoman.net/articles/claude-code-weekly-content-planner-routine-2026