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.