In many apps I've built, every decision is stored in Markdown files under docs/. But documentation can become obsolete, even comments inside source files can.
I assume src/ is treated as the source of truth. If we start placing Markdown documentation inside src/, outdated documentation can live alongside the actual source of truth, blurring the boundary between what the system actually does and what the documentation says it does.
maarut · · focus · HN ↗
I assume src/ is treated as the source of truth. If we start placing Markdown documentation inside src/, outdated documentation can live alongside the actual source of truth, blurring the boundary between what the system actually does and what the documentation says it does.
[deleted] · · focus · HN ↗
[deleted]
gantamk · · focus · HN ↗
Yes, proximity indeed helps. However, I feel its better to automate docs revision using skills and related instructions in claude.mf/agents.md
I am building something in related problem, which is architecture visualisation