Automating publishing tasks with Claude Code so I can focus on writing
Alfred Lua built an agentic CMS using Claude Code and Obsidian, automating research, proofreading, and backlinks across a 75-day daily publishing streak.
By Dillip Chowdary • Nov 20, 2026 • Source: alfredlua.com

At a glance
- Builder
- Alfred Lua
- Core tools
- Obsidian, Claude Code, Vercel
- Model used
- Claude 3.5 Sonnet
- Publishing streak
- 75 consecutive days
- Scheduled research
- Daily at 6:48 am
- Event date
- 18 December 2026
In this post
Solo founder Alfred Lua deployed an autonomous content management system built on Anthropic's Claude Code command-line tool, sustaining a 75-day daily publishing streak across his personal and technical websites. As detailed in alfredlua.com's report, the setup replaces commercial publishing platforms with terminal agents that handle daily background research, multi-pass proofreading, bidirectional backlinking, and calendar scheduling. By offloading editorial administration to local command-line tools, the architecture eliminates the operational friction of running an independent online publication.
This teardown analyzes how local Markdown vaults, version-controlled repositories, Claude Code skills, and Vercel hosting combine into an automated publishing pipeline. It outlines how autonomous scheduled agents collect source material, execute iterative editorial reviews, manage link taxonomies across essay archives, and sequence distribution queues. The workflow is designed for solo developers, technical writers, and software founders who want to publish regular essays without maintaining hosted content management systems.
01Markdown file repositories across local tools
The architecture replaces hosted platforms such as WordPress, Ghost, and Webflow with a local stack combining Obsidian, Next.js, and Vercel. Obsidian serves as the primary writing interface for local Markdown files, synchronized across mobile phones and laptops using an Apple iCloud+ subscription. Because the static website uses MDX files for page rendering, Claude Code interacts directly with raw text files on disk rather than through database endpoints or administrative browser dashboards.
File storage is divided across two local Git repositories. The primary website repository contains published article files, site components, and Next.js rendering routes originally built using tutorials from Lee Robinson. A secondary Getting Things Done repository houses editorial task lists, a local content calendar, and modular skill files that instruct Claude Code on specific publishing steps.
02Scheduled morning research and memory retention
To eliminate blank-page paralysis and avoid open-ended web browsing, Claude Code executes an automated research task every morning at 6:48 am. The agent uses live web search tools to identify three verified stories or historical quotations addressing writing, practical wisdom, and life choices. It analyzes source credibility rather than relying on unverified training data, moving high-quality findings into Obsidian notes while discarding weak leads.
The discovery routine runs on Anthropic's Claude 3.5 Sonnet model. The agent maintains an internal memory log that updates automatically after each run, preventing it from suggesting repetitive quotations or previously covered historical anecdotes. If morning research uncovers multiple compelling ideas, the author archives the surplus material into individual note files inside Obsidian for future articles.
03Automated proofreading and editorial revision cycles
Draft proofreading is driven by a custom skill located inside the Getting Things Done workspace folder. Once a draft is completed in Obsidian, the author submits the Markdown text to Claude Code for structural, grammatical, and factual evaluation. The tool flags spelling errors, checks logical consistency across arguments, and performs targeted web searches to confirm factual statements.
Each article passes through five to ten revision cycles with the agent before publication. Although the author previously relied on human editing from former colleagues at Buffer and Pebblely, automated reviews provide immediate turnaround across multiple drafts in a single afternoon. Examining alternative phrasings generated by the model helps resolve awkward sentences and overcome writing blocks during drafting.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
| Editorial Metric | 2022 Setup (Alfie) | 2026 Agentic CMS |
|---|---|---|
| Language Model | GPT-3 | Claude 3.5 Sonnet |
| Review Feedback Rounds | 1 daily human review | 5 to 10 automated passes |
| Automated Backlinks | 0 linked posts | 13 linked posts |
| Publishing Streak | Irregular intervals | 75 consecutive daily articles |
04Bidirectional backlinks and article metadata indexing
Operational administration centers on a global catalog index created by Claude Code after parsing all historical articles. The resulting Markdown index records titles, publication dates, category tags, structural summaries, and keyword lists for every published post. A recent newsletter titled I feel like I'm not supposed to enjoy parenting was cataloged with tags for joy, perspective, and finite time alongside summaries of its core arguments.
The agent references this index to assign three relevant tags to new drafts while preventing tag bloat through explicit constraints. It simultaneously injects forward-links from archive pages and embeds backlinks to older relevant essays, placing up to 13 previous posts as natural backlinks within a single article. Strict execution rules prevent the tool from rewriting wording inside linked archive pages, and the author maintains manual veto power over all proposed hyperlinks.
05Editorial calendar conflict resolution and distribution
Article publishing dates are managed through a local content calendar located in the Getting Things Done repository. Because the author drafts essays in batches weeks in advance, Claude Code evaluates thematic density across consecutive dates instead of simply assigning drafts to the next open calendar day. This sequencing prevents thematically similar essays from appearing on back-to-back days.
During one scheduling pass, Claude Code assigned an article to Monday, 30 November 2026, at 8:00 am after verifying that prior slots were filled. The agent positioned the essay after weekend pieces addressing Richard Feynman and F.
Scott Fitzgerald because the themes remained distinct. Completed articles are pushed to Buffer via automated scripts, while formatted rich text is generated for manual pasting into Substack, Medium, and Facebook.
npm install -g @anthropic-ai/claude-code
claude update/model sonnetclaude --model sonnetexport ANTHROPIC_MODEL=claude-3-5-sonnetNote: Alfred Lua is hosting an online Write Club session on Friday, 18 December 2026, from 10:00 am to 12:30 pm SGT for five to ten participants.
Frequently asked questions
What core software tools comprise Alfred Lua's agentic CMS?
The system uses Obsidian for draft writing and note storage, Claude Code for automated research and content operations, and Next.js hosted on Vercel for website publishing. Files are synced across devices using Apple iCloud+.
How does Claude Code automate morning article research?
Every morning at 6:48 am, Claude Code searches the web using Sonnet 5.5 to find three verified stories or quotes about writing and life. It assesses source credibility and records results in a persistent memory log to avoid duplicate topics.
How does the agent manage internal backlinks across essays?
The agent maintains a central Markdown index file cataloging past post titles, dates, tags, summaries, and keywords. It references this file to insert relevant backlinks and forward-links without altering existing prose in published archives.
How does Claude Code schedule upcoming drafts on the calendar?
The agent inspects a local calendar in the author's Getting Things Done repository and assesses thematic similarities between drafts. It reschedules articles when consecutive days share similar themes, ensuring topic variety across daily slots.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement