documentation-and-adrs

Document decisions, not just code. The most valuable documentation captures the why — the context, constraints, and trade-offs that led to a decision. Code shows what was built; documentation explains why it was built this way and what alternatives were considered. This context is essential for future humans and agents working in the codebase.

When NOT to use: Don't document obvious code. Don't add comments that restate what the code already says. Don't write docs for throwaway prototypes.

ADRs capture the reasoning behind significant technical decisions. They're the highest-value documentation you can write.

Verwenden Sie es, wenn Sie Architekturentscheidungen treffen, öffentliche APIs ändern, Funktionen versenden oder wenn Sie den Kontext aufzeichnen müssen, den zukünftige Ingenieure und Agenten benötigen, um die Codebasis zu verstehen. Quelle: addyosmani/agent-skills.