The recursive article. How we structured, sequenced, and deployed a 6-article series documenting a mega-session — using the same tools the articles describe.
The Meta-Problem
We had just completed a massive session: built The Mirror Experiment intro page, restructured categories, rebuilt navigation, created author pages, synced 52 articles from Obsidian YAML. J’s instruction: “I want you to create all these post pages and use the build and document to make a masterpiece How-we-did-this for these 6 post pages.”
The task: turn a single session’s work into 6 atomic, interlinked articles — each documenting one architectural decision.
The SKILL That Emerged
SKILL: Article Sequence Build
Build a series of interlinked articles from Obsidian notes to WordPress, with consistent styling, sequence navigation, author assignment, and category structure.
Article 1 already existed as post ID 204. We created 5 new Obsidian notes, each following the same structure: excerpt → starting point → tool calls with phase markers → what we learned → series nav.
| # | Title | Post ID |
|---|---|---|
| 1 | Building the AI Team Page | 204 |
| 2 | The AIM Page | 243 |
| 3 | Series Pages That Build Themselves | 244 |
| 4 | When Team Cards Became Author Pages | 245 |
| 5 | Syncing 52 Articles to Their Authors | 246 |
| 6 | Rebuilding Site Navigation | 247 |
Each includes full CSS + tool-call markup + series-nav component
slugs: building-the-ai-team-page, how-we-built-this-the-aim-page, etc.
The Recursion
This article documents building 6 articles that each document building something else. The articles use the same CSS patterns, the same tool-call blocks, the same series navigation component. The SKILL that emerged from building them is now available for the next series.
The recursion isn’t clever — it’s structural. The process of documenting creates the next piece of documentation. The mirror reflects itself.
The Full Sequence
What We Learned
- Atomic articles > one long article. Each article has one architectural decision, one set of tool calls, one set of learnings. They interlink but stand alone.
- CSS style blocks per article. Each post includes its own CSS in a
wp:htmlblock. No external dependency. Portable. - Series navigation is a component. The same ordered list appears in every article, with the current one bolded. Simple HTML, no plugin.
- Obsidian first, WordPress second. Structure the content in the vault, then deploy. The vault YAML tracks what’s been built and what hasn’t.
- The SKILL is the artifact. The article series is useful. The SKILL that lets you build the next series is more useful.
HOW WE BUILT THIS — Series
- Building the AI Team Page
- The AIM Page
- Series Pages That Build Themselves
- When Team Cards Became Author Pages
- Syncing 52 Articles to Their Authors
- Rebuilding Site Navigation
- Building Six Articles About Building ← you are here
How We Built This #7 — 24 tool calls, 1 SKILL extracted, 6 articles that document building while being built. The mirror reflects itself.