Topic 06 / 08 · 03 articles

AI-Assisted Engineering

About this topic

121 words

AI coding agents are now part of how serious software gets built, but most advice about them is either hype or a list of prompts. What matters in practice is the environment around the agent: the instructions it reads, the permissions it has, the tools it can call and the review process its output goes through.

Here I document how I set up and operate AI-assisted engineering on a large multi-repository codebase — project instruction files, permission allow-lists, hooks, reusable skills, subagents, MCP servers and memory — and what I have learned about keeping quality high while moving much faster than I could alone.

These are working notes from daily use, updated as the tools change, with the configuration files included.

01Start here

Featured

A layered CLAUDE.md, tight permissions, hooks, skills and scoped MCP servers: the setup that keeps Claude Code safe and cheap across dozens of repositories.

13 min

02All articles in AI-Assisted Engineering