... date math. Before you know it the codebase is bloated with small single purpose packages that nobody wants to maintain. We already have solid built in helpers in our main codebase but the model completely ignores them unless I spell it out every single time. How are you nudging your AI tools to look at what's already in the repo before pulling in extra dependencies ...

... just using vanilla JS. It seems like these tools always jump to installing third party packages for tiny tasks that only take a few lines of code. How are you stopping them from cluttering package.json without having to spell it out in every single prompt ...

... looking, is it usually by topic, or more "what was I thinking around that time", more like a date or a project? That changes a lot about how the retrieval should work. Comment from Hadi Farnoud(@hadifarnoud): The calendar-vs-notification distinction feels especially true for meeting notes. A reminder is fine for a tiny chore, but anything that came out of a meeting usually needs protected time, context, and a clear definition of done. The thing I'd want ... ... while a thing on your calendar doesn't ask anything, it's already a commitment you made. That difference in mental weight is exactly right. Going to sit with this. Thanks for taking the time to spell