Putting multiple topics into a single article makes it hard for readers to find what they need. This article explains why I introduced the one page, one topic policy on this site and what criteria I use to determine what counts as one topic.
A firsthand account of using Claude Code Dynamic Workflows to run security, performance, and code style reviews in parallel, including how results were merged.
How I use structured handoff files and shared rules to transfer working context from Claude Code to Codex.
While asking AI to add a blog article, I discovered that the navigation layout had also been changed without instruction. This article describes why that happened and how I addressed it with a rule in CLAUDE.md.
A record of four consecutive Git conflicts on a feature branch, the attempt to resolve them with AI assistance, the decision to abandon the branch, and the lessons I took from it.
AI-generated Japanese text is often not suitable for business documents as-is. This article categorizes four common problem patterns and provides concrete rewriting examples for each.
When AI writes articles, they can feel like they were written by someone else. To address this, I defined author perspective, writing style, prohibited expressions, and an E-E-A-T checklist in my-blog-writing SKILL. This article covers how article quality changed before and after defining the skill.
A record of setting up automatic deployment on Vercel with AI assistance, starting from manual publishing after every code change. Covers the configuration steps, errors encountered, and how they were resolved.
Writing a specification before asking AI to implement reduces mismatches and repeated revisions. This article explains the Spec First principle and what to include in a simple specification.
Three terms — References, Reference Materials, and Related Links — were mixed inconsistently across the site. This article records how I clarified the distinction and standardized usage.
A record of the new problems that emerged once the Vibe Coding build phase ended and maintenance began, and the harness, tests, and validation I introduced to address them.
Is the time spent building CLAUDE.md and rule files really necessary? This article explains concretely what changed before and after setting up a harness, based on my own experience.
When using AI to write blog posts, I use a twelve-step workflow to verify numbers, facts, and reference links before publication. This article describes each step in a way that is accessible without technical background.
A record of three specific problems encountered when starting Vibe Coding — vague instructions, unintended design output, and lost context — with explanations of why each occurs and how to address it.
I built a system with AI to translate Japanese articles into English and keep them in sync on the site. This article covers the translation flow and three patterns that caused problems: over-interpretation, structural changes, and inconsistent terminology.
A file exists in the repository but the link is broken — this happened on this site. Here is why verifying internal links by file path alone is insufficient, and how I addressed it.
What should humans do when AI handles implementation? A concrete breakdown of tasks that can be delegated to AI versus tasks that humans must verify themselves.
Drift — where configuration files and actual code gradually diverge over time — is a common problem in AI-assisted projects. This article explains the causes and prevention strategies.
AI gives different answers to the same question, and it does not remember previous sessions. This article explains Harness Engineering, a design approach developed to address these challenges when using AI in ongoing projects.
An explanation of the Vibe Coding concept. What does it mean to build sites and features by giving instructions to AI rather than writing code yourself, what can it do, and what are its limits?