AGENTS.md vs CLAUDE.md: How to Give Claude and Codex Separate Rules in the Same Repository
Shiori
What CLAUDE.md and AGENTS.md each do, why separate files are necessary, and how I use shared/ to avoid duplicating common rules.
Claude
26 posts with the tag “Claude”
Balancing Token Savings and Code Quality: A Real Example of Quality Declining from Over-Trimming
Shiori
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.
Building a Validation Script with AI: Automating Consistency Checks for Harness Configuration
Shiori
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.
Building with Astro, Starlight, and Vercel Alongside AI: What I Delegated and What I Checked Myself
Shiori
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.
Choosing Between Claude and Codex: How I Decide Which AI to Hand Off Work to in the Same Repository
Shiori
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.
Defining AI Specialist Tasks with SKILL.md: How Skill Design Improves Reproducibility
Shiori
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.
Designing a Lessons Log to Prevent Repeated AI Mistakes: How lessons.md Stops the Same Problem from Happening Twice
Shiori
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.
Designing the shared/ Directory: How I Organized Rules, Skills, and Workflows for AI to Reference
Shiori
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.
How AI Triggered a Production Deployment and Why I Made npm run build Require Approval
Shiori
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.
How I Built a Site with Vibe Coding: The Full Process from Design to Launch
Shiori
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.
How to Use Claude Code Hooks: Real Examples of Adding Custom Processing Before and After Tool Execution
Shiori
Real examples of setting up Claude Code hooks for pre-edit backups and post-edit automatic validation, with notes on how the workflow changed.
Preventing AI from Modifying Navigation and Design Without Permission: Why I Introduced a No UI Regression Rule
Shiori
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.
Rewriting AI-Generated Text into Business Japanese: Common Problem Expressions and Substitution Patterns
Shiori
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.
Setting Up an AI Blog Writer: How I Defined Author Voice and Tone with my-blog-writing SKILL
Shiori
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.
Setting Up Vercel CI/CD with AI Assistance: A Record of Automating Deployment
Shiori
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.
Spec First: Why Writing a Specification Before Asking AI to Implement Leads to More Consistent Results
Shiori
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.
The Next Step After Vibe Coding: What It Takes to Move from Building to Sustaining a Site
Shiori
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.
Three Common Pitfalls When Starting Vibe Coding and How to Handle Them
Shiori
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.
Using AI to Sync Japanese-to-English Translations: The Approach and the Patterns That Did Not Work
Shiori
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.
What Humans Do When AI Writes the Code: Separating Judgment, Verification, and Design
Shiori
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.