Writing your first post
Once setup is done, now you write. In blog-studio, writing is natural language, not a slash command. Say “write a post about this topic” and blog-orchestrator carries it from research through drafting.
1) Call it in natural language
Section titled “1) Call it in natural language”Type your topic at the Claude Code prompt in natural language.
write a post from my experience building a Chrome extension with Claude CodeOr narrow the scope.
- “write a post about X” → one full pass through research, drafting, review, publishing
- “just a draft of X” → up to before review
- “just review it” → up to right before publishing
Whatever the utterance, blog-orchestrator takes it and decides the Phase range needed.
2) Phase 1 — strategy first
Section titled “2) Phase 1 — strategy first”The orchestrator makes the brief first. Title candidates, slug, category, target reader, keywords, search intent, outline, and differentiation angle land in _workspace/briefs/{slug}-brief.md.
Normal screen: a line like “Phase 1 strategy complete” runs, and the brief file path shows. The post’s direction is set at this step, so if the brief differs from what you intended, it’s better to ask for a fix right here. Going all the way to drafting with the direction off costs a lot to undo.
3) The spot that asks about real experience
Section titled “3) The spot that asks about real experience”Before drafting, the orchestrator has a spot where it stops and asks. If the concrete error or data, failure or friction that should go into the post is empty, the AI asks the user for the real details rather than inventing experience.
This is a deliberately planted spot. A post without first-person experience and a concrete failure reads AI-flavored and has weak E-E-A-T signals. When it asks “what error message did you see,” “where did you get stuck,” write down what you remember. That detail builds the post’s trust.
4) Phase 2 — drafting
Section titled “4) Phase 2 — drafting”The orchestrator runs research, drafting, and editing in turn. The post piles up as staging at _workspace/posts/new/ko/{category}/{slug}.md.
Length follows the brief’s mode. The default, long, is 10000–12000 Korean characters, and short is 5000–7000. For a quick tip or a single-problem fix, you can set the mode ahead of time with “write it short.”
Normal screen: a “Phase 2 production complete” line along with the staging file path. At this point the post isn’t published yet. It’s only inside _workspace/ on your computer.
5) Category
Section titled “5) Category”When the category isn’t obvious, tool or platform analysis goes under ai, and opinion or workflow essays under thoughts. If your blog runs its own categories, just say the name.
6) The spot to read the post yourself
Section titled “6) The spot to read the post yourself”Once the staging file is made, read it through once. Open _workspace/posts/new/ko/... in VS Code, or tell Claude Code “show me the post I just wrote.” The two gates (AI-smell, AdSense) screen it once more before publishing, but it’s safer for a human to check your intent and the facts. In particular, check that the experience you gave in step 3 actually made it in.
Once the Korean draft is out, go to bilingual, the spot for making the post’s English version. If you don’t run an English blog, skip this step and go to publish.