How I Built an AI Pipeline to Draft My Art Blog Posts Faster

The Temptation of Automation

For years, I handcrafted every blog post about game art. Research, sketching out ideas, writing, formatting—each piece took hours. But with AI tools popping up everywhere, I wondered: could they handle the grunt work while I focused on the creative decisions?

The answer turned out to be yes, but it wasn't as simple as typing a prompt. I spent several days wrestling with APIs, style guides, and formatting quirks. The result? A pipeline that writes, styles, and pushes my articles straight to the blog's draft folder. This post is my attempt to break down what worked and what didn't.

The Two Real Problems

First, most AI-generated text reeks of artificiality. It's too polished, too generic, lacking the quirks and opinions that make writing feel human. Readers can spot it a mile away and bounce.

Second, formatting is a soul-sucking time sink. Copy-pasting from a text editor into a CMS often mangles the layout, leaving you to fiddle with styles for an hour. I wanted AI to not just write but also deliver a properly formatted draft, ready to publish.

Setting Up the Pipeline

To push formatted content directly to the blog's draft folder, I needed to use the official API. For my platform, that meant getting an AppID and AppSecret, plus whitelisting an IP address. The process had recently moved to a new developer portal, so I had to figure out the updated steps.

Once I had those credentials, I plugged them into WorkBuddy via a simple instruction. It walked me through adding its IP to the whitelist, and just like that, the technical bridge was up.

Training the AI to Sound Like Me

Now came the hard part: making the AI write like... me. I started by feeding it 3-5 of my best posts and telling it to mimic my tone. That gave me a rough imitation, but it wasn't enough.

Since WorkBuddy is from the same company as my blogging platform, it could access my entire history. I let it read all my past articles, and it picked up on my favorite phrases, my habit of starting with a hook, even how I structure chapters. The output improved dramatically.

But I didn't stop there. I turned those observations into a written style guide—a document that lists my go-to words, banned phrases like "firstly" and "lastly," paragraph length limits, and even rules for images. Then I packaged that guide into a custom Skill, so WorkBuddy loads it automatically every time I ask for a new post. No more remembering to feed it context.

Formatting for the Blog's Quirky Editor

My blog's editor is notoriously picky. Standard HTML with divs and flexbox falls apart. The only reliable approach is to use table-based layouts, with styles applied directly to table cells. I had to define strict rules: only certain CSS properties like color, background, font-size, and margins; no border-radius, no gradients, no pseudo-elements.

I baked these rules into the Skill as well. Now, when WorkBuddy pushes a draft, the formatting is already correct. I don't touch a single style tag.

The 5-Step Human Review

Even with all this automation, I never publish without a thorough review. Here's my checklist:

1. Is the Direction Right?

First, I check the overall topic and structure. Does it match what I intended? AI tends to wander off-topic while sounding perfectly confident. If something's off, I give specific feedback and ask for a rewrite.

2. Does It Sound Like Me?

I read through the entire piece looking for AI tells—overly formal transitions, clichés, that polished but empty tone. The opening paragraph is the biggest offender. If a sentence doesn't sound like something I'd say, I rewrite it and tell WorkBuddy to avoid that phrasing next time.

3. Is the Title Punchy?

A title needs numbers and a promise. My AI's first attempt was long and flat. I changed it to something like "I Automated My Blog Drafts with AI—Here's How, 10x Faster." Also, watch out for character limits; my platform rejects titles over 64 bytes (Chinese counts as 3 bytes per character).

4. Is the Formatting Clean?

AI loves to over-decorate—boxes, colored backgrounds, badges everywhere. I now instruct it to match the style of my best-performing posts, sticking to a minimal, clean look.

5. Are the Screenshots Real?

For tutorials, nothing beats actual screenshots. AI-generated illustrations are a no-go. I make sure every step has a real screenshot, or I leave a placeholder for myself to add later.

Iterating with Feedback

Each revision cycle, I focus on one aspect at a time. First draft: let it run wild. Second: tighten the tone. Third: rearrange sections. Fourth: polish details. After four or five rounds, it's close to ready.

But the key is to feed those corrections back into the style guide. For example, I once asked for an illustration to accompany a post. The AI generated a generic concept art that had nothing to do with the topic. I told it, "Only use real screenshots; if none exist, leave a placeholder." That rule is now part of my Skill, so it never happens again.

Why Bother?

This pipeline cut my per-post time from five hours to thirty minutes. But more importantly, it shifted my role from typing every word to making judgment calls. I decide what's worth saying, provide the raw material, and polish the final output. The AI handles the heavy lifting.

Sure, the AI does 95% of the work, but that last 5%—the taste, the authenticity, the human touch—is what makes a post worth reading. Tools will keep improving, but your unique perspective is irreplaceable. Set up your own pipeline today, and you'll have a tireless assistant that never complains about the grind.