A toolkit is unglamorous. It is the prompts you have refined until they are reliable, the templates you start from, the checklists that catch your known failure modes, the scripts that handle the parts you do the same way every time. None of it is impressive individually. Together it is the difference between starting from zero and starting from eighty percent.
Treat it like a product you maintain. It has a purpose, users of one, and a backlog. When something goes wrong twice, that is a bug, and the fix goes into the toolkit rather than into your memory.
The reason this compounds is that the toolkit captures judgment. Every correction you make once becomes a correction you never have to make again.
The alternative is doing the same setup work every time and calling the result experience.