What Is AI-DLC? Understanding AWS's Proposed Approach Through Examples
An explanation of AWS's AI-Driven Development Life Cycle through its current five phases, official examples, enterprise case, and adoption considerations.
An explanation of AWS's AI-Driven Development Life Cycle through its current five phases, official examples, enterprise case, and adoption considerations.
A practical guide to coding-agent self-healing loops based on 2026 research and official implementations from OpenAI, Google, and GitHub, covering layered verification, stop conditions, permission boundaries, and human approval.
How I am building a harness to reduce repeated color accessibility issues in UI components created through Vibe Coding, especially across light/dark themes, hover, selected, and focus states.
Learn which preferences and cautions belong in Codex Memories, which mandatory rules belong in AGENTS.md, and when to stop or review memory use and generation.
How to hand work between Claude Code and Codex: record current state, completed work, remaining tasks, reasoning, and verification results, then resume in the next session.
How I moved automatic normalization before validation in prebuild to address recurring Astro build failures.
How structural and URL checks differ from Playwright browser verification, where browser checks fit in the validation flow, and which decisions require human review.
A review of development and maintenance through 148 change records from March 22 to June 21, 2026, shared rules, and implemented checks, with explicit limits on unmeasured effort and effects.
A plain-language guide to using Claude Code Hooks for repeated checks, including before-versus-after timing, human approval boundaries, and an adoption process.
How to record an AI workflow problem, cause, resolution, and prevention in lessons.md as a decision history that later work can verify.
A record of how a production build command ran while I was asking AI to make a separate change, and the approval-required rule I put in place afterward.
A safe handoff process for uncommitted changes, separating what Codex Local, Worktree, and Cloud environments can see.
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.
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.
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.
This article explains the current workflow for synchronizing English articles from canonical Japanese, using three translation-drift patterns and a two-stage checklist. It separates differences that structural checks can surface from semantic differences that require human judgment.
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.
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.
How to centralize Claude Code and Codex policy in shared/, organize it by role, connect tool-specific references, and use synchronization checks to reduce missed updates.
AI gives different answers to the same question, and it does not remember previous sessions. This article explains how I use the term Harness Engineering for this site's AI operation practices.