|
|
|
|
|
|
by tomasz-tomczyk
94 days ago
|
|
|
Not sure this works very well. I got 10/21 with 3 quick wins: - Start recording major architecture and workflow decisions in ADRs. I'm not sure all decisions need to be in ADRs. I think AGENTS.md can summarise a lot of this and as long as you keep it up to date, it sounds more efficient than keeping every record? Some is fair though to show how you make decisions - Add at least one linter and formatter with explicit repo-level commands. I have it with go, not detected - Group repo docs under `docs/` or add an index that links the important pages. What happened to comments in code? :) |
|
|
For the ADR vs AGENTS: CLIs usually load the AGENTS.md with a tag saying: "this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task." That's claude code for instance. So ADR is rather something agents would not question.
Go linting: That's weird, ill take a look
Docs vs comments: great point but i think they serve two purposes. one is global (specs, design docs, etc.) and one is local (how a method works, or reason for a specific workaround)