Coding
AI coding in production: Claude Code team rollouts, Cursor and Codex CLI workflows, repo-level instructions, GitHub Actions for AI code review, and the engineering practices that survive security review.
All Articles
design-md-drift-check Build Log
A build log for design-md-drift-check, a skill that checks DESIGN.md drift against real frontend tokens, components, and UI patterns.
CLAUDE.md File Best Practices for Production Teams
Write a CLAUDE.md that keeps Claude Code useful in production: scope memory, keep rules concise, move enforcement to hooks, and review drift.
Codex vs Claude Code vs Gemini CLI for Production Teams
A production rollout comparison of Codex CLI, Claude Code, and Gemini CLI after Google's Antigravity transition, with security and telemetry rules.
Claude Code Planning Mode for Production Teams
Use Claude Code planning mode as a production review gate: when to plan first, how to approve safely, and what teams should log before rollout.
Claude Code Security Review for Production Teams
Use Claude Code security review as early signal, not an approval gate. Here is the rollout pattern, CI split, permissions, hooks, and logs.
Gemini CLI vs Antigravity CLI: The Production Migration Rule
Google is moving Gemini CLI users to Antigravity CLI. Compare migration work, access risk, controls, and when to choose Claude Code or Codex.
Codex vs Claude Code for Production Teams
Claude Code is the better first rollout for terminal-first teams. Codex wins for delegated cloud tasks, PR review, and compliance-visible agent work.
Claude Code Pricing for Teams: The Production Rollout Cost
Claude Code pricing starts at $20, but teams need a seat mix, usage credits, API fallback controls, analytics, and rollout policy.
Claude Code Hooks for Production Teams
Use Claude Code hooks as deterministic team guardrails for tests, protected files, command logging, permissions, and safe rollout.
Claude Code vs Cursor for Production Teams
Use Cursor for daily IDE work and Claude Code for governed terminal delegation. Compare costs, controls, security, and rollout rules.
One letter, every week. Working systems — not hot takes.
Build logs, agentic engineering decisions, agent failures, evals, and what survives real users. Sent weekly, never more.