architecture-decision-records

What it does: - Captures important choices your team makes about how to build the software, like which database to use or which framework to pick - Writes down why you chose one option over others - Keeps a searchable record so future developers understand why the code looks the way it does - Automatically detects when you are making a big decision and offers to write it down When to use it: - You are choosing between different tools, libraries, or design patterns - You want to explain to your team why you picked one approach - Someone asks why the code does something a certain way - You need to remember the tradeoffs you accepted when you made a choice