Agent-Enhanced Development · the book

Code your teammates, your owner, and your agents can all read.

Nine chapters on one billing example, carried the whole way. Nothing gets rewritten. It gets read.

Start reading · Chapter 3 →
zsh · your machine
$ claude plugin marketplace add AgentC-Consulting/aed-conventions
$ claude plugin install aed@aed-conventions
aed@aed-conventions installed · 3 skills, 3 commands, 1 naming hook
$ open https://agentc.consulting/agent-enhanced-development.md
$

Copy this and hand it to your agent. It installs the conventions and opens each chapter's machine edition as you go. Optional. The book reads fine without it.

The idea

One piece of information, three readers, and the agent in between.

Billing · Apply a late fee · help page
1# Applies a late fee to an invoice that has gone past its grace period, then tells the customer.
2class Billing:::ApplyLateFee
3# -- What this needs --
4
5 # The invoice being charged. It knows its customer, its amount, and its due date.
6 property invoice : · Invoice — required
The owner's help page. It is the developer's file.

Every chapter shows one piece of information crossing from one reader to the next without a rewrite. The developer writes the file once. The owner reads it as a help page. Their assistant follows it when it writes the next one.

The chapters

Nine chapters. Start with the open one.

Contents

Chapter 3 is open. The rest open in order.

  1. 1 Why agents need conventionsMy agent stopped reading before it reached the part that mattered.
  2. 2 Vibe coding as a squadHer agent renamed what mine had just named.
  3. 3 Naming that reads like a sentenceThe line that reads without opening three other files.Read now →
  4. 4 Process managers"When an invoice goes thirty days late, then…"
  5. 5 Feature storiesMy own feature, written so an agent can build it.
  6. 6 Edit-level styleThe edit, and the check that runs on it.
  7. 7 Control flowA case statement I can read like a menu.
  8. 8 How the workflow runsRunning it with a local model.
  9. 9 Adopt it in ten minutesMy agent reports what it changed.

Your place is kept on this device.

Why a book

Vibe coding works alone. A squad needs one convention.

customer.cr · two agents
her agent
1class Customer
2 property name : String⋯
3 property email_address : String
4end
my agent
1class Customer
2 property first_name : String⋯
3 property email_address : String
4end
Two agents, one file, two names for the same thing.

Two people and two agents on one codebase rename each other's work and bury the plan inside method bodies. Call it team vibe coding or squad vibe coding: every hand on the file, human or agent, needs the same names, the same process managers, the same feature stories. This book is that convention, taught one chapter at a time.

Where the rules come from

Versioned, licensed, and signed.

zsh · aed-conventions
$ gpg --import agentc-signing-pubkey.asc
gpg: key 7C7636A83E58439F: public key "AgentC Consulting <st@agentc.consulting>" imported
$ git tag -v v1.1.0-rc.1
tag v1.1.0-rc.1
tagger AgentC Consulting <st@agentc.consulting>
gpg: Good signature from "AgentC Consulting <st@agentc.consulting>"
v1.1.0-rc.1 · CC BY 4.0 · signed tag

Keep going

Where to next.