Architectural Decisions FAQs

Question 1

Can I control the level of detail in the decision logs?

Accepted Answer

Yes. The skill is designed to adapt its output based on complexity. It can generate brief one-sentence summaries for simple library choices or detailed multi-section reports for complex architectural trade-offs.

Question 2

When should I use this Claude Code skill?

Accepted Answer

Use it when making high-impact project choices, such as selecting a database, switching frameworks, or defining core design patterns. Claude will also proactively suggest documenting a decision when it detects significant architectural shifts.

Question 3

How does this skill improve my development workflow?

Accepted Answer

It automates the tedious task of maintaining ADRs. By capturing the context, alternatives, and trade-offs directly from your active conversation, it ensures high-quality documentation without interrupting your coding flow.

Question 4

What does the Architectural Decisions skill do?

Accepted Answer

This skill maintains a chronological log of major design and architectural choices in a dedicated docs/decisions.md file. It ensures that the 'why' behind your project's core structure is documented and preserved for future developers.

Question 5

Does it document every small code change?

Accepted Answer

No. The skill is intentionally conservative. It filters out minor implementation details and routine refactors, focusing exclusively on significant decisions that shape the project's long-term trajectory.

Architectural Decisions

Architectural Decisions

주요 기능

사용 사례

주요 기능

사용 사례