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.

在做出架構決策、更改公共 API、發布功能時，或在需要記錄未來工程師和代理程式理解程式碼庫所需的上下文時使用。 來源：addyosmani/agent-skills。