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 checklist.
An explanation of AWS's AI-Driven Development Life Cycle through its current five phases, official examples, enterprise case, and adoption checklist.
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.
A practical guide to what Codex Memories are for, how they differ from AGENTS.md, and when to avoid, review, or reset memory behavior.
How I decide when to use Claude Code versus Codex in the same repository, and how I design handoff documents to transfer context across sessions.
How I reduced recurring Astro build failures by moving automatic normalization into prebuild instead of treating each failure as a one-off fix.
How AI Learning Playground positions Playwright alongside structural checks, URL verification, and human review.
A look back at three months of building and running AI Learning Playground with Vibe Coding, organized around insights from the technical, design, and operational phases.
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.
I updated the learning_time workflow so docs articles normalize reading time during authoring, while dev:check and prebuild keep the same normalization as a safety net.
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.
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.