I stopped doing this too but two books I read recently changed my mind.
How to take Smart Notes: https://www.goodreads.com/en/book/show/34507927
Building a Second Brain: https://www.goodreads.com/book/show/59616977-building-a-second-brain
These books or their concepts are mentioned above by others.
The idea is to create one note per nugget. You can include the original nugget and also your own thoughts on how it relates to your projects and higher levels.
A key insight for me in the Building a Second Brain book is to file notes by project. The consequence of this is that if a golden nugget would be useful for a project, then file it there. Notes should be easily searchable so that they can be easily moved into new project folders in the future. I think the key principal is to put the note where you need to see it. I don't use the suggested PARA structure but instead apply the same principal to my project support and reference folders.
In a Zettelkasten, this golden nugget note would reference (and be referenced by) other related notes. You can relate it to your projects by use of a "desktop" (which I believe is Zettelkasten terminology for a project in process). The linking system between notes isn't meant to be a comprehensive web. Rather, it is intended to allow discovery of related concepts by traversing threads of linked ideas.
For me in GTD, once I have captured a nugget like this, my filing priority for these notes looks a bit like this:
1. File it in an appropriate project support folder.
2. File it in an appropriate reference folder.
3. Create a new reference folder that maximises my chance of finding the note at the right time (maybe a folder for a higher level of mine).