Distill an iterated conversation into one reusable prompt — corrections become requirements, rejections become an avoid-list.
What a converged conversation contains: a rejected voice, an accepted framing, a hard constraint, a format decision, and a final-version moment — each mapped to its prompt section.
View Resource →The result you finally liked lives inside the chat. Distill the iterations into one prompt: corrections become requirements, the accepted version becomes the quality bar.
View Resource →In feedback threads the rejections carry the knowledge: the mocking empty-state enthusiasm, the passive phrasing — converted into the avoid-rules that define the style.
View Resource →A case-study chat that converged on the three-beat structure becomes a template: {{input}} changes per customer, everything the iteration earned stays fixed.
View Resource →A support-reply iteration becomes a standing instruction: status-and-date first, ticket number in sentence one, never overpromise — paste once per session, use all day.
View Resource →When the chat says "this is the final version", that's the moment to bottle: the scenario opening, the differentiators, the 170-word cap — extracted at peak convergence.
View Resource →A converged email thread becomes a standing asset: the usage-anchored subject pattern, the value-before-discount rule, the five-sentence cap — extracted, not retyped.
View Resource →Your editing preferences — short sentences, six-word headlines, em-dashes intact — declared across a chat in two languages, preserved as standing rules.
View Resource →The social-campaign sequence that finally worked — hook, data point, contrarian take, thread — preserved as a workflow prompt that runs the whole recipe in order.
View Resource →A status-report iteration that converged on "lead with the decision-relevant number" becomes a prompt that produces that report every week without the Monday rewrite.
View Resource →