This repo is my personal engineering handbook — the philosophies, workflows, and tooling that shape how I design, build, and ship software. It is written for myself first and shared publicly as a reference for anyone curious about how an engineer-first, AI-amplified practice actually works day to day.
It is a living document. Expect it to grow and change as my thinking evolves.
The why — principles that explain the decisions behind how I work. These change slowly.
- Branching Strategy — why every repo runs on
develop/mainwith CLI-merged releases and conventional commits. - Release Cadence & Semver Discipline — why releases are a deliberate ceremony, why the monthly patch cycle, and how conventional commits drive the version number.
- Security Posture — why every repo ships with the same SAST, Scorecard, CODEOWNERS, and SLA baseline from day one.
- Testing — why I write the tests I write, and why I don't write the ones I don't.
The how — concrete steps, commands, and tooling that implement the philosophies. These change as tools evolve.
- Branching & Releases — branch model, day-to-day flow, and the release ceremony.
- CI Automation Surface — the GitHub Actions workflows that ship with every repo, what each does, and when it fires.
- Development Tooling Stack — the AI-assisted development stack I use, and the end-to-end workflows that run on top of it.
Brainstorm-level design docs capturing how I'm thinking about specific engineering problems. Not polished specs — working documents that evolve as decisions get made.
- Claude Bot Account for AI-Authored PRs — separating authorship from review so AI-written code has a clean audit trail.
More chapters are in progress.
developis the default branch. All changes land via pull request.maintracks released versions of the handbook.- The handbook is versioned with semver tags so I can reference a specific snapshot of my thinking over time.