63
architecture decision record
also ADR
A short note: the decision, the context, the options you rejected. So next month’s chat does not relitigate it.
What is architecture decision record?
An ADR is a dated page in the repo. Context, decision, consequences. It is not a design novel. It is why the code looks like this.
Why does architecture decision record matter when vibe coding?
A new thread will “improve” the architecture you already chose, because the reason lived in chat. Pin it in `docs/adr`. Tell the model to read it before proposing a second approach.
How do you do architecture decision record?
When a choice has a real alternative — library, storage, auth — write a one-page ADR before generating the second option. Status: accepted. Link it from the prompt.
How do you ask a model for architecture decision record?
Read docs/adr before proposing a new architecture. If this decision is new, write an ADR: context, decision, rejected options. Do not implement two approaches.
What goes wrong with architecture decision record?
An ADR after the rewrite, describing what you wish you had decided. Write it when the choice is made, not as fan fiction.