I have said this already but it bears repeating because it is the thing that separates a useful library from a folder of templates you wrote once and forgot about.
Every time you use a framework and edit the output, that edit is information. If the edit is something you do once because of the specific situation, it is not a framework issue. If the edit is something you do twice or more, it is a missing instruction in the framework, and it should be added.
The refinement cycle is simple. Use the framework. Review the output. Note the edits. If an edit recurs, update the framework. Save the updated version.
Over time, your most-used frameworks become remarkably precise. They produce output that requires minimal editing because every repeated correction has been built back into the structure. That is the compounding return of a prompt library: the more you use it, the less work each use requires.
I refine my library at the end of each week during the first month of building it, and monthly after that. It takes ten minutes. The return on those ten minutes is measurable in hours saved.
