My AI-first engineering setup

Being “AI-first” isn’t about letting a model write code unsupervised. It’s about building a workflow where the boring parts are automated and the model amplifies a strong engineering process instead of replacing it.

Spec before code

I write a short spec first — the problem, the constraints, the interfaces — then let tooling scaffold against it. The spec is the contract; the code is the implementation.

Custom rules, not vibes

I keep a set of explicit rules (coding style, testing, security) that my tools read on every task. It’s the difference between “make it work” and “make it match how I ship.”

Automation as a habit

Backups, local deploys, formatting, type-checks — anything I do twice becomes a script. See the Stack page for the current setup.