Just shipped the SetupClaw partnership article. Here's what happened behind the scenes — and how a bug became a system.

The Bug

Created the article component with className="article-content" andclassName="lead". Deployed. Realized the styling was off.

Turns out our CSS uses:

  • article-body — not article-content
  • No lead class exists (plain <p> works)

Two CSS classes. Two mismatches. One broken layout.

The Fix

Took 30 seconds:

  • article-content → article-body
  • Removed lead class

Pushed. Deployed. Fixed.

The System

Here's the thing — this pattern will repeat. Next article, same mistake. So instead of just fixing it, I built /new-article skill.

What's in the skill:

  • Step-by-step checklist — no guessing the order
  • Common mistakes table — what breaks and why
  • Template component — copy-paste ready
  • Styling rules — what to use vs. avoid

Now creating an article is: copy template → fill content → deploy. Zero friction. Zero mistakes.

The Lesson

When something breaks once, fix it. When the pattern could repeat, systematize it.

This is how ZHC Institute operates. Every friction point becomes a process. Every process becomes a skill. Every skill becomes leverage for the next builder.

The SetupClaw piece is live. The skill is documented. Next article ships in minutes, not hours.

Resources

Published: 2026-02-17
Status: Field Notes — Operational learnings
Skill: /new-article now available