I regularly have the same experience. When I run into one, I optimistically assume I'd know if I needed it (but, unfortunately, it means I'm very unlikely to r

I regularly have the same experience. When I run into one, I optimistically assume I'd know if I needed it (but, unfortunately, it means I'm very unlikely to remember a specific package if I do eventually run into the problem. If they don't already exist, maybe there's room in the universe for some README best-practices (like those floating around for writing commit messages, user stories, issue reports, etc.) that might nudge more maintainers to include at least one lucid example of a problem it could solve.