Growing a Zenn Writing Environment from Scratch with Claude Code

I write Zenn articles with Claude Code. My role is to set the direction, read the finished article end-to-end, and provide fact-checks and feedback. Claude Code handles the actual edits. After two weeks of this workflow, I noticed a natural cycle forming: every time a problem comes up, it gets turned into a reusable mechanism so it never happens again. Verbal instructions become skills, manual tasks become scripts, and pitfalls become learned skills. Everything stays in the environment in a reusable form. This article documents the problems I encountered and what each one was turned into. First: Turning Tone into a Skill Before writing the first article, I defined the writing tone. "Technical but not too casual," "no AI slop," "be honest about failures" — I gave Claude Code detailed style instructions and saved them as a zenn-writer skill. Before creating the skill, I had to repeat "use polite Japanese" and "no AI slop" every time I started a new session. With the skill in place, the s