AGENTS.md vs CLAUDE.md: How to Give Claude and Codex Separate Rules in the Same Repository
What CLAUDE.md and AGENTS.md each do, why separate files are necessary, and how I use shared/ to avoid duplicating common rules.
What CLAUDE.md and AGENTS.md each do, why separate files are necessary, and how I use shared/ to avoid duplicating common rules.
AI can generate URLs for references that do not actually exist. This article covers how the URL-checking script for this site works and how it classifies results.
A record of how reducing AI input context to lower costs led to a decline in output quality, along with criteria for deciding what can and cannot safely be removed.
Manually checking the consistency of configuration files has limits. This article covers the process of building a validation script with AI and why automated detection proved useful.
A firsthand record of configuring a site using Astro, Starlight, and Vercel alongside AI. Covers the role of each tool and a breakdown of which parts of the setup were delegated to AI versus confirmed personally.
The criteria I use to decide whether to work with Claude Code or Codex in the same project, with a specific example of handing off mid-task.
Who holds copyright over text that AI generated, and should readers be told? This article explains Japan's current legal understanding and the policy I follow on this blog.
Three axes for deciding how much to delegate to AI — reversibility, scope of impact, and ease of verification — explained with concrete scenarios.
Repeating the same instructions to an AI every time is less stable than defining procedures as a skill file. This article covers how I designed SKILL.md files for this site and what changed as a result.
Because AI memory resets between conversations, resolved issues can recur in the next session. This article explains how I designed lessons.md, a log file that AI reads to avoid repeating the same mistakes.
Based on experience running an AI reviewer alongside an AI writer, this article clarifies what automated checks reliably detect and where human review remains necessary.
When the number of rule files for AI grows, knowing what is where becomes difficult. This article explains how I organized them into three categories—rules, skills, and workflows—using the shared/ directory.
When AI generates many articles, frontmatter values can fall out of sync with the actual content. This article explains why I introduced an automatic normalization script for the learning_time field and what consistency gains come from automation.
What happened when I moved work from Claude Code to Codex with a dirty worktree, and the steps I now follow for a safe handoff.
How I designed and use an agent-handoff document to transfer work from a Claude Code session to Codex.
A record of how a production deployment command ran while I was asking AI to make a separate change, and the approval-required rule I put in place afterward.
A step-by-step record of building a website from scratch in collaboration with AI. What I delegated to AI and what I decided myself, explained through the actual stages of the project.
Real examples of setting up Claude Code hooks for pre-edit backups and post-edit automatic validation, with notes on how the workflow changed.
CLAUDE.md is the configuration file AI reads first when starting a project. This article explains what to write in it and how it changes AI behavior, with before-and-after examples.
A record of five specific patterns where AI-generated Mermaid diagrams failed to render correctly — including special characters, arrow direction, label length, Japanese text, and nested structures — along with how each was resolved.